Triple
T20025259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lockport, Illinois |
E494963
|
entity |
| Predicate | railLineTerminusDirection |
P26272
|
FINISHED |
| Object | connects to Chicago Union Station |
—
|
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: connects to Chicago Union Station | Statement: [Lockport, Illinois, railLineTerminusDirection, connects to Chicago Union Station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railLineTerminusDirection Context triple: [Lockport, Illinois, railLineTerminusDirection, connects to Chicago Union Station]
-
A.
terminusDirection
Indicates the directional orientation or endpoint direction associated with a route, path, or line.
-
B.
direction2Terminus
Indicates the direction in which something leads toward or ends at a particular terminus or endpoint.
-
C.
railLineTerminus
chosen
Indicates that a rail line ends or terminates at the specified location or station.
-
D.
railwayRouteDirection
Indicates the direction or orientation in which a railway route runs or is intended to be traveled.
-
E.
railwayTrafficDirection
Indicates the customary side of the track on which trains are operated or expected to run within a given railway system or segment.
- 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_69da626bfd288190aa5d65098b6433ae |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6628d5b8c8190a35f95ac4a016550 |
completed | April 20, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69e54ce752748190a0a1ffddd0372271 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:35 p.m.