Triple
T9416434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panaca, Nevada |
E227031
|
entity |
| Predicate | distanceToCalienteInMiles |
P83440
|
FINISHED |
| Object | 14 |
—
|
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: 14 | Statement: [Panaca, Nevada, distanceToCalienteInMiles, 14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToCalienteInMiles Context triple: [Panaca, Nevada, distanceToCalienteInMiles, 14]
-
A.
distanceToCaliente
chosen
Indicates the measured spatial distance between a given entity and the location or object referred to as "Caliente."
-
B.
distanceFromTucson
Indicates the spatial distance between a given entity and the location of Tucson.
-
C.
distanceFromTijuana
Indicates the measured spatial distance between a given place or entity and the city of Tijuana.
-
D.
distanceFromSocorro
Indicates the spatial distance between an entity and the reference location Socorro.
-
E.
distanceToMexicoBorder
Indicates the measured or estimated distance between a given location or entity and the border of Mexico.
- 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_69ca84359e7c819091148ba4b670e436 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd68c9917481909f793a2a9efb2a75 |
completed | April 1, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69cca54c37f88190bddccf28e5fe5c84 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:48 p.m.