Triple
T18175702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | YEADE |
E435150
|
entity |
| Predicate | isSeaportCode |
P70426
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [YEADE, isSeaportCode, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSeaportCode Context triple: [YEADE, isSeaportCode, true]
-
A.
isPortOf
Indicates that one location or facility serves as a port or harbor for another place, entity, or transportation route.
-
B.
hasSeaportStatus
Indicates that an entity possesses the status or designation of being a seaport or having seaport facilities.
-
C.
isInlandPort
Indicates that a port facility is located inland, away from the open sea, typically on a river, canal, or lake, while still serving maritime or shipping functions.
-
D.
isMajorSeaport
Indicates that a location functions as a primary maritime port handling significant volumes of sea-based trade, transport, or shipping activity.
-
E.
portCodeLOCODE
chosen
Indicates that a port is identified by a specific LOCODE (Location Code) value.
- 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_69d8b90c7ec081909b4694ccecb449c6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4df59bf3881909adc28cacbe9cb39 |
completed | April 19, 2026, 1:57 p.m. |
| PD | Predicate disambiguation | batch_69e4331baeb88190b21f50a98c36c78e |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:30 a.m.