Triple
T38524341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coyanosa |
E922584
|
entity |
| Predicate | distanceToPecosCity |
P204707
|
FINISHED |
| Object | about 30 miles south |
—
|
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 30 miles south | Statement: [Coyanosa, distanceToPecosCity, about 30 miles south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToPecosCity Context triple: [Coyanosa, distanceToPecosCity, about 30 miles south]
-
A.
distanceToPueblo
Indicates the measured spatial distance between a given entity and the location identified as Pueblo.
-
B.
approximateDistanceToElPaso
Indicates that one entity has an estimated or rough distance measurement relative to the location of El Paso.
-
C.
distanceFromSocorro
Indicates the spatial distance between an entity and the reference location Socorro.
-
D.
distanceToAmarillo
Indicates the spatial distance between a given entity and the location Amarillo.
-
E.
distanceFromTaos
Indicates the spatial distance separating something from the location of Taos.
- 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_69f76ea5f5588190bd0b28c82e975640 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c84ecbc81908232e5215355f43b |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:32 p.m.