Triple
T21365309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eads, Colorado |
E526893
|
entity |
| Predicate | distanceToKansasBorder |
P143997
|
FINISHED |
| Object | approximately 60 miles west |
—
|
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 60 miles west | Statement: [Eads, Colorado, distanceToKansasBorder, approximately 60 miles west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToKansasBorder Context triple: [Eads, Colorado, distanceToKansasBorder, approximately 60 miles west]
-
A.
distanceToOklahomaBorderInMiles
Indicates the numerical distance, measured in miles, from a given location to the nearest point on the Oklahoma state border.
-
B.
distanceToKansasCity
Indicates the spatial distance between a given location or entity and Kansas City.
-
C.
distanceToWichita
Indicates the measured distance between a given entity’s location and the city of Wichita.
-
D.
distanceToHaysKansas
Indicates the measured distance between a given location and Hays, Kansas.
-
E.
distanceToTopeka
Indicates the spatial distance between a given entity’s location and the city of Topeka.
- 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_69e0b51d8a308190b09113b3b3f9bc15 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8b06e1ba081908a96928a65da5fa2 |
completed | April 22, 2026, 11:26 a.m. |
| PD | Predicate disambiguation | batch_69e6162bbfc88190a3e75859941b2638 |
completed | April 20, 2026, 12:03 p.m. |
| PDg | Predicate description generation | batch_69e61b3e47f881908fb2aac9bd2bfb58 |
completed | April 20, 2026, 12:25 p.m. |
Created at: April 16, 2026, 5:09 p.m.