Triple
T38630080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coastal Classic Train |
E937427
|
entity |
| Predicate | routeFeatures |
P10970
|
FINISHED |
| Object | Turnagain Arm coastline |
—
|
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: Turnagain Arm coastline | Statement: [Coastal Classic Train, routeFeatures, Turnagain Arm coastline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeFeatures Context triple: [Coastal Classic Train, routeFeatures, Turnagain Arm coastline]
-
A.
roadFeature
Indicates that an entity is a specific physical or functional characteristic associated with a road, such as its structure, markings, or related infrastructure.
-
B.
notableRouteFeature
chosen
Indicates that a route is associated with a distinctive or significant feature, such as a landmark, characteristic terrain, or other notable aspect along its path.
-
C.
routesFrom
Indicates that something (such as a path, connection, or communication) originates at one entity and is directed or carried from that source entity toward another.
-
D.
routePlan
Indicates a planned path or sequence of steps for traveling from a starting point to a destination.
-
E.
routeDetail
Indicates the specific characteristics or parameters of a route, such as its path, segments, or configuration details, within a routing relationship.
- 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_69f76ed5ca3c81909288f61fbf37b359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.