Triple
T12205033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gallup |
E290813
|
entity |
| Predicate | distanceFromArizonaBorder |
P104312
|
FINISHED |
| Object | about 20 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 20 miles east | Statement: [Gallup, distanceFromArizonaBorder, about 20 miles east]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromArizonaBorder Context triple: [Gallup, distanceFromArizonaBorder, about 20 miles east]
-
A.
distanceToMexicoBorder
Indicates the measured or estimated distance between a given location or entity and the border of Mexico.
-
B.
distanceFromTucson
Indicates the spatial distance between a given entity and the location of Tucson.
-
C.
distanceToCaliforniaBorder
Indicates the measured or specified distance between a given location and the border of the state of California.
-
D.
distanceToSpanishBorder
Indicates the measured distance between a given location and the border of Spain.
-
E.
distanceToUSBorderByRoad_km
Indicates the distance in kilometers from a given location to the nearest point on the United States border when traveling by road.
- 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_69d6ab65923081909acfc61b7a612233 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d938cd2edc8190b1971349dbc0dee0 |
completed | April 10, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69d91c38321c819080d500d0d64a04f6 |
completed | April 10, 2026, 3:50 p.m. |
| PDg | Predicate description generation | batch_69d938ca32908190bd56f563efcbe8a0 |
completed | April 10, 2026, 5:52 p.m. |
Created at: April 8, 2026, 9:51 p.m.