Triple
T23841839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Presidio, Texas |
E591007
|
entity |
| Predicate | distanceToElPasoApprox |
P142046
|
FINISHED |
| Object | about 250 miles southeast |
—
|
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 250 miles southeast | Statement: [Presidio, Texas, distanceToElPasoApprox, about 250 miles southeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToElPasoApprox Context triple: [Presidio, Texas, distanceToElPasoApprox, about 250 miles southeast]
-
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.
approximateDistanceToLasCruces
Indicates that an entity has an estimated or rough distance measurement to the location Las Cruces.
-
D.
distanceFromSanAntonio
Indicates the measured or specified distance between an entity and the location of San Antonio.
-
E.
distanceToPueblo
Indicates the measured spatial distance between a given entity and the location identified as Pueblo.
- 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_69e25d1de32c8190a907afe9c3d6cd6d |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c888c13c8190b85d2cd425ee84dc |
completed | April 29, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f1614612b481908c45d99e588882f9 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:09 p.m.