Triple
T8876642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | White Butte |
E211301
|
entity |
| Predicate | distanceToDickinson |
P85479
|
FINISHED |
| Object | approximately 65 miles southwest |
—
|
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 65 miles southwest | Statement: [White Butte, distanceToDickinson, approximately 65 miles southwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToDickinson Context triple: [White Butte, distanceToDickinson, approximately 65 miles southwest]
-
A.
distanceToLincoln
Indicates the measured distance between a given entity and Lincoln (a specific reference location).
-
B.
distanceToTopeka
Indicates the spatial distance between a given entity’s location and the city of Topeka.
-
C.
distanceToKansasCity
Indicates the spatial distance between a given location or entity and Kansas City.
-
D.
distanceToSpringfield
Indicates the measured distance between a given location and the place named Springfield.
-
E.
distanceToOmaha
Indicates the spatial distance between a given entity’s location and the location of Omaha.
- 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_69ca838e78748190934d82db3104f855 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc61472cc081909e51b4a35a20ef43 |
completed | April 1, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2956788190a311c647b4da17a6 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5d6e54808190af4156edd4c8ffbc |
completed | March 31, 2026, 11:49 p.m. |
Created at: March 30, 2026, 6:52 p.m.