Triple
T26009034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yutan, Nebraska |
E646842
|
entity |
| Predicate | distanceToOmahaApproxMiles |
P76348
|
FINISHED |
| Object | 20 |
—
|
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: 20 | Statement: [Yutan, Nebraska, distanceToOmahaApproxMiles, 20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToOmahaApproxMiles Context triple: [Yutan, Nebraska, distanceToOmahaApproxMiles, 20]
-
A.
distanceToOmaha
chosen
Indicates the spatial distance between a given entity’s location and the location of Omaha.
-
B.
distanceToOklahomaCity
Indicates the spatial distance between a given entity’s location and the location of Oklahoma City.
-
C.
distanceToWichita
Indicates the measured distance between a given entity’s location and the city of Wichita.
-
D.
distanceToKansasCity
Indicates the spatial distance between a given location or entity and Kansas City.
-
E.
distanceToDodgeCityInMiles
Indicates the numerical distance, measured in miles, between a given entity’s location and Dodge City.
- 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_69e77e89d5848190b54352cdb74f6029 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
Created at: April 22, 2026, 9:01 a.m.