Triple
T1301515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Sea Canal |
E27772
|
entity |
| Predicate | supportsTraffic |
P26781
|
FINISHED |
| Object | ocean-going ships |
—
|
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: ocean-going ships | Statement: [North Sea Canal, supportsTraffic, ocean-going ships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsTraffic Context triple: [North Sea Canal, supportsTraffic, ocean-going ships]
-
A.
hasTrafficManagement
Indicates that an entity implements, uses, or is associated with systems or measures for controlling and optimizing traffic flow.
-
B.
hasTrafficFunction
Indicates that an entity performs, supports, or is assigned a specific function or role related to traffic management or control.
-
C.
hasTrafficDirection
Indicates that there is a specified flow or orientation of traffic associated with an entity (such as a road, lane, or route).
-
D.
hasTruckTraffic
Indicates that there is truck-related vehicular movement or flow occurring on or through a specified location or route.
-
E.
hasTrafficControl
Indicates that some form of traffic management or regulation mechanism is present or applied to a given route, intersection, or transportation element.
- F. None of above. chosen
Provenance (4 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_69a496d6682881909ba658f1c1e0e2b0 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c1145c2481908adf22dfd6ce349b |
completed | March 1, 2026, 10:43 p.m. |
| PD | Predicate disambiguation | batch_69a4bee8544c8190874efd9bae9bccf9 |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4bf60545c8190901ccfb2cb7c4b41 |
completed | March 1, 2026, 10:36 p.m. |
Created at: March 1, 2026, 7:51 p.m.