Triple
T23266811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rio Grande Gorge Bridge |
E588171
|
entity |
| Predicate | approxDistanceFromTaos |
P124539
|
FINISHED |
| Object | about 10 miles northwest of Taos |
—
|
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 10 miles northwest of Taos | Statement: [Rio Grande Gorge Bridge, approxDistanceFromTaos, about 10 miles northwest of Taos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approxDistanceFromTaos Context triple: [Rio Grande Gorge Bridge, approxDistanceFromTaos, about 10 miles northwest of Taos]
-
A.
distanceFromTaos
chosen
Indicates the spatial distance separating something from the location of Taos.
-
B.
distanceFromSocorro
Indicates the spatial distance between an entity and the reference location Socorro.
-
C.
approximateDistanceToLasCruces
Indicates that an entity has an estimated or rough distance measurement to the location Las Cruces.
-
D.
approximateDistanceToElPaso
Indicates that one entity has an estimated or rough distance measurement relative to the location of El Paso.
-
E.
approxDistanceFromEnsenada
Indicates that one entity is located at an approximate distance from the reference location Ensenada.
- 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_69e25d148adc819088efbf42672604e9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f194cd13b48190a9c282545a34f348 |
completed | April 29, 2026, 5:19 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:37 p.m.