Triple
T27365917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santa Cruz County, Arizona |
E690160
|
entity |
| Predicate | borderLengthWithMexico |
P19447
|
FINISHED |
| Object | approximately 50 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 50 miles | Statement: [Santa Cruz County, Arizona, borderLengthWithMexico, approximately 50 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderLengthWithMexico Context triple: [Santa Cruz County, Arizona, borderLengthWithMexico, approximately 50 miles]
-
A.
borderTypeWithMexico
Indicates the type or nature of the border that an entity shares with Mexico.
-
B.
hasBorderLengthWithUSA
chosen
Indicates that the length of the land or maritime border shared between a given country or region and the USA has a specified measurement.
-
C.
borderCityOnMexicanSide
Indicates that a city is located on the Mexican side of an international border shared with another country.
-
D.
distanceToMexicoBorder
Indicates the measured or estimated distance between a given location or entity and the border of Mexico.
-
E.
distanceToSpanishBorder
Indicates the measured distance between a given location and the border of Spain.
- 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_69ef51ff826081909e42c8e2bfb97941 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: April 27, 2026, 12:17 p.m.