Triple
T14056936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harbour Line |
E338242
|
entity |
| Predicate | isHarbourCorridor |
P85888
|
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: [Harbour Line, isHarbourCorridor, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHarbourCorridor Context triple: [Harbour Line, isHarbourCorridor, true]
-
A.
hasHarbourEntrance
Indicates that an entity serves as the entrance or access point to a harbour for another entity.
-
B.
hasHarbor
Indicates that a place possesses or contains a harbor for docking or sheltering vessels.
-
C.
isPartOfCorridorSystem
chosen
Indicates that one entity forms a component or segment within a larger interconnected corridor system.
-
D.
isMainHarbourOf
Indicates that a harbour serves as the primary or principal port facility for a specified location or region.
-
E.
isCoastalPort
Indicates that a location functions as a port situated on or directly adjacent to a sea or ocean coastline.
- 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_69d81c67ba6c819091935650dfb3b895 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de3c8e6d008190af8892f34c5cefbd |
completed | April 14, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69de05adef888190b023ab42ef5076b6 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:20 p.m.