Triple
T11227149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peotone, Illinois |
E265724
|
entity |
| Predicate | distanceToChicagoApprox |
P24381
|
FINISHED |
| Object | about 40 miles south of Chicago |
—
|
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: about 40 miles south of Chicago | Statement: [Peotone, Illinois, distanceToChicagoApprox, about 40 miles south of Chicago]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToChicagoApprox Context triple: [Peotone, Illinois, distanceToChicagoApprox, about 40 miles south of Chicago]
-
A.
distanceToChicagoLoop
Indicates the spatial distance between a given location and Chicago’s central business district (the Loop).
-
B.
distanceFromChicagoTerminus
Indicates the measured distance of an entity from the Chicago terminus point along a specified route or network.
-
C.
distanceFromChicagoUnionStation
Indicates the measured distance between a given location and Chicago Union Station.
-
D.
distanceFromChicagoLoop
chosen
Indicates the spatial distance between an entity’s location and the Chicago Loop area.
-
E.
distanceToMilwaukee
Indicates the measured or calculated spatial distance between a given entity’s location and the city of Milwaukee.
- 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_69d6aac656d48190b275efaa7d6074ee |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8ff7b40819089c835be710bc575 |
completed | April 9, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69d75cfbbb188190861efd5d94fe27da |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:30 p.m.