Triple
T3889586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tucson, Arizona, United States |
E88025
|
entity |
| Predicate | distanceToMexicoBorder |
P51672
|
FINISHED |
| Object | approximately 60 miles |
—
|
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: approximately 60 miles | Statement: [Tucson, Arizona, United States, distanceToMexicoBorder, approximately 60 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToMexicoBorder Context triple: [Tucson, Arizona, United States, distanceToMexicoBorder, approximately 60 miles]
-
A.
distanceFromMexicoCity
Indicates the measured distance between an entity’s location and Mexico City.
-
B.
distanceFromTijuana
Indicates the measured spatial distance between a given place or entity and the city of Tijuana.
-
C.
borderCityOnMexicanSide
Indicates that a city is located on the Mexican side of an international border shared with another country.
-
D.
distanceToPennsylvaniaBorder
Indicates the measured distance between a given location and the border of Pennsylvania.
-
E.
borderCityOnUSSide
Indicates that a city is located on the U.S. side of an international border shared with another country.
- 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_69aed9466d548190939f5217a23ed4ac |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeecaee7148190ada451ccfc6582ee |
completed | March 9, 2026, 3:52 p.m. |
| PD | Predicate disambiguation | batch_69aee759609c8190985e96ec6d96dedd |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aee80858a481909961a33fb50ff8d1 |
completed | March 9, 2026, 3:32 p.m. |
Created at: March 9, 2026, 3:21 p.m.