Triple
T13703542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ogden, Illinois |
E328577
|
entity |
| Predicate | distanceToChampaignApproxMiles |
P111231
|
FINISHED |
| Object | 15 |
—
|
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: 15 | Statement: [Ogden, Illinois, distanceToChampaignApproxMiles, 15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToChampaignApproxMiles Context triple: [Ogden, Illinois, distanceToChampaignApproxMiles, 15]
-
A.
distanceFromChampaign
Indicates the measured distance between a given entity’s location and the location of Champaign.
-
B.
distanceFromUrbana
Indicates the measured spatial distance between a given entity or location and Urbana.
-
C.
distanceToBloomington
Indicates the spatial distance between a given entity’s location and the location of Bloomington.
-
D.
distanceToColumbus
Indicates the spatial distance between a given entity and the location of Columbus.
-
E.
distanceFromChicagoUnionStation
Indicates the measured distance between a given location and Chicago Union Station.
- F. None of above. chosen
Provenance (4 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dcad162158819089280ee1e6b5c2cf |
completed | April 13, 2026, 8:45 a.m. |
| PD | Predicate disambiguation | batch_69dbbe9059488190a8113177c83e1481 |
completed | April 12, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69dbc59ca1a88190a6abd3bd00554c93 |
completed | April 12, 2026, 4:17 p.m. |
Created at: April 9, 2026, 9:54 p.m.