Triple
T18719562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pittsburgh and Lake Erie Railroad |
E457731
|
entity |
| Predicate | primaryTrafficDirection |
P3915
|
FINISHED |
| Object | east–west |
—
|
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: east–west | Statement: [Pittsburgh and Lake Erie Railroad, primaryTrafficDirection, east–west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryTrafficDirection Context triple: [Pittsburgh and Lake Erie Railroad, primaryTrafficDirection, east–west]
-
A.
trafficDirection
chosen
Indicates the direction in which traffic is intended or allowed to move relative to a given reference point or segment.
-
B.
hasTrafficDirection
Indicates that there is a specified flow or orientation of traffic associated with an entity (such as a road, lane, or route).
-
C.
transportDirection
Indicates the directional flow or route along which something is transported from an origin toward a destination.
-
D.
majorTrafficType
Indicates the primary kind of traffic or flow that predominantly characterizes a given route, segment, or transportation context.
-
E.
secondaryTraffic
Indicates that there is an additional, indirect, or subordinate flow of traffic associated with a primary traffic stream or event.
- 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_69d8d393ba9c8190a8b03b04ddbb0a09 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e56ab90adc81909f3b4aabb6d5a707 |
completed | April 19, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69e478e0889c8190a118d67b200ce8ef |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:50 a.m.