Triple
T20840013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hatch, New Mexico |
E513068
|
entity |
| Predicate | approximateDistanceToElPaso |
P142046
|
FINISHED |
| Object | about 80 miles northwest |
—
|
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: about 80 miles northwest | Statement: [Hatch, New Mexico, approximateDistanceToElPaso, about 80 miles northwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateDistanceToElPaso Context triple: [Hatch, New Mexico, approximateDistanceToElPaso, about 80 miles northwest]
-
A.
distanceToAmarillo
Indicates the spatial distance between a given entity and the location Amarillo.
-
B.
distanceFromSanAntonio
Indicates the measured or specified distance between an entity and the location of San Antonio.
-
C.
approxDistanceFromEnsenada
Indicates that one entity is located at an approximate distance from the reference location Ensenada.
-
D.
distanceToPueblo
Indicates the measured spatial distance between a given entity and the location identified as Pueblo.
-
E.
distanceFromSocorro
Indicates the spatial distance between an entity and the reference location Socorro.
- 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_69e0b4cf62a88190bbf92351e9e57259 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c34a60848190b33078172675f8d7 |
completed | April 21, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a1f4f48190aa9fb4ef8f8aea5a |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53c4d6881909b4d0a716fa5ed4a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:43 p.m.