Triple
T18191311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woodstock Metra station |
E435538
|
entity |
| Predicate | distanceFromChicagoOTC |
P94694
|
FINISHED |
| Object | approximately 51.6 miles |
—
|
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: approximately 51.6 miles | Statement: [Woodstock Metra station, distanceFromChicagoOTC, approximately 51.6 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromChicagoOTC Context triple: [Woodstock Metra station, distanceFromChicagoOTC, approximately 51.6 miles]
-
A.
distanceFromChicagoTerminus
chosen
Indicates the measured distance of an entity from the Chicago terminus point along a specified route or network.
-
B.
distanceFromChicagoUnionStation
Indicates the measured distance between a given location and Chicago Union Station.
-
C.
distanceToChicagoLoop
Indicates the spatial distance between a given location and Chicago’s central business district (the Loop).
-
D.
distanceFromChicagoLoop
Indicates the spatial distance between an entity’s location and the Chicago Loop area.
-
E.
distanceFromChampaign
Indicates the measured distance between a given entity’s location and the location of Champaign.
- 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_69d8b90c7ec081909b4694ccecb449c6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e0cf0d7c81908ce0386c52ef601d |
completed | April 19, 2026, 2:03 p.m. |
| PD | Predicate disambiguation | batch_69e4331e92408190ad607ba4956a3897 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:31 a.m.