Triple
T25850253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicago and Eastern Illinois Railroad |
E651180
|
entity |
| Predicate | hadRouteTo |
P91689
|
FINISHED |
| Object | St. Louis, Missouri |
—
|
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: St. Louis, Missouri | Statement: [Chicago and Eastern Illinois Railroad, hadRouteTo, St. Louis, Missouri]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadRouteTo Context triple: [Chicago and Eastern Illinois Railroad, hadRouteTo, St. Louis, Missouri]
-
A.
hadRoute
chosen
Indicates that an entity (such as a service, vehicle, or system) followed, operated on, or was associated with a specific route.
-
B.
wentTo
Indicates that one entity traveled or moved from its original location to another specified place.
-
C.
routeOf
Indicates that one entity is the path, course, or trajectory taken or followed by another entity (such as a vehicle, shipment, or signal).
-
D.
mayRouteTo
Indicates that one entity is permitted or able to direct, forward, or transfer something (such as data, traffic, or requests) to another entity.
-
E.
hadBranchIn
Indicates that an organization or entity maintained a branch, office, or subsidiary located in another specified place or entity.
- 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_69e7ab39035c8190be15c8aaee1bb858 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6023ac9e48190b60639f667445ace |
completed | May 2, 2026, 1:55 p.m. |
| PD | Predicate disambiguation | batch_69f4a0fed15881909b789251fe5d8d45 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 22, 2026, 7:58 a.m.