Triple
T34690367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guadalupe Peak |
E890874
|
entity |
| Predicate | distanceFromElPaso |
P142046
|
FINISHED |
| Object | about 110 miles east |
—
|
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 110 miles east | Statement: [Guadalupe Peak, distanceFromElPaso, about 110 miles east]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromElPaso Context triple: [Guadalupe Peak, distanceFromElPaso, about 110 miles east]
-
A.
approximateDistanceToElPaso
chosen
Indicates that one entity has an estimated or rough distance measurement relative to the location of El Paso.
-
B.
distanceToAmarillo
Indicates the spatial distance between a given entity and the location Amarillo.
-
C.
distanceFromSanAntonio
Indicates the measured or specified distance between an entity and the location of San Antonio.
-
D.
distanceFromSanAngelo
Indicates the measured distance between a given entity and the location of San Angelo.
-
E.
distanceFromTucson
Indicates the spatial distance between a given entity and the location of Tucson.
- 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_69f349db7ab8819086808e833f472871 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2:05 a.m.