Triple
T9213277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fuzhou Port |
E221176
|
entity |
| Predicate | maritimeRouteType |
P7985
|
FINISHED |
| Object | coastal shipping routes |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: coastal shipping routes | Statement: [Fuzhou Port, maritimeRouteType, coastal shipping routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maritimeRouteType Context triple: [Fuzhou Port, maritimeRouteType, coastal shipping routes]
-
A.
associatedWithSeaRoute
Indicates a relationship where something is connected or related to a particular sea route, such as by use, location, or relevance.
-
B.
hasSeaRouteConnection
Indicates that there exists a navigable maritime route linking two locations or entities.
-
C.
maritimeVariant
Indicates a version or form of something that is specifically adapted for or used in maritime (sea-related) contexts.
-
D.
sailingRoute
chosen
Indicates a path or course taken by a vessel when traveling by water from one location to another.
-
E.
maritimeGatewayFor
Indicates a relationship where one location serves as the primary seaport or ocean-access point enabling maritime connectivity and trade for another location.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ca83eae42c8190a0ea9e040710a277 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccda05406081909893bec3a092d3ce |
completed | April 1, 2026, 8:40 a.m. |
| PD | Predicate disambiguation | batch_69cc660ce23c81909c7bbe10f4a05f36 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:27 p.m.