Triple
T27098187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paxton, Illinois |
E686365
|
entity |
| Predicate | distanceTo Champaign, Illinois (approximate miles) |
P111231
|
FINISHED |
| Object | 30 |
—
|
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: 30 | Statement: [Paxton, Illinois, distanceTo Champaign, Illinois (approximate miles), 30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceTo Champaign, Illinois (approximate miles) Context triple: [Paxton, Illinois, distanceTo Champaign, Illinois (approximate miles), 30]
-
A.
distanceToChampaignApproxMiles
chosen
Indicates the approximate distance, measured in miles, from a given location to Champaign.
-
B.
distanceFromChampaign
Indicates the measured distance between a given entity’s location and the location of Champaign.
-
C.
distanceFromUrbana
Indicates the measured spatial distance between a given entity or location and Urbana.
-
D.
distanceToBloomington
Indicates the spatial distance between a given entity’s location and the location of Bloomington.
-
E.
distanceFromChicagoTerminus
Indicates the measured distance of an entity from the Chicago terminus point along a specified route or network.
- 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_69ef1489f8b481908e24a1985982bd26 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69ff0b6bc4a88190bf1d38c6ea26bcdc |
completed | May 9, 2026, 10:24 a.m. |
| PD | Predicate disambiguation | batch_69ff082a22f4819095ded971dbd8ea7b |
completed | May 9, 2026, 10:10 a.m. |
Created at: April 27, 2026, 8:46 a.m.