Triple
T24123750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicago Ridge station |
E597733
|
entity |
| Predicate | distanceToChicagoUnionStation |
P75017
|
FINISHED |
| Object | approximately 14 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 14 miles | Statement: [Chicago Ridge station, distanceToChicagoUnionStation, approximately 14 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToChicagoUnionStation Context triple: [Chicago Ridge station, distanceToChicagoUnionStation, approximately 14 miles]
-
A.
distanceFromChicagoUnionStation
chosen
Indicates the measured distance between a given location and Chicago Union Station.
-
B.
distanceFromChicagoTerminus
Indicates the measured distance of an entity from the Chicago terminus point along a specified route or network.
-
C.
distanceToChicagoLoop
Indicates the spatial distance between a given location and Chicago’s central business district (the Loop).
-
D.
distanceFromChicagoLaSalleStreetStation
Indicates the measured distance between a given entity and Chicago’s LaSalle Street Station.
-
E.
distanceFromChicagoLoop
Indicates the spatial distance between an entity’s location and the Chicago Loop area.
- 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_69e288c808b881909fed7d18f04bcbbe |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dee718f88190860d40c6f09a77c8 |
completed | April 29, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:06 p.m.