Triple
T25411132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Docks |
E636696
|
entity |
| Predicate | seaPortOf |
P77702
|
FINISHED |
| Object | Dover |
—
|
NE NERFINISHED |
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: Dover | Statement: [Western Docks, seaPortOf, Dover]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seaPortOf Context triple: [Western Docks, seaPortOf, Dover]
-
A.
portOfLoading
Indicates the location where goods are initially loaded onto a vessel or transport vehicle for shipment.
-
B.
isPortOf
chosen
Indicates that one location or facility serves as a port or harbor for another place, entity, or transportation route.
-
C.
isMainDeepWaterPortFor
Indicates that one location serves as the primary deep-water port facility for another entity, such as a region, city, or country.
-
D.
linkedToInlandPort
Indicates a relationship where something has a direct connection or association with an inland port, such as for transport, logistics, or access purposes.
-
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_69e75db361d881908d8701c856da6413 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5b00dfbf08190b20120c052126935 |
completed | May 2, 2026, 8:04 a.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
Created at: April 21, 2026, 1:53 p.m.