Triple
T20097115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poncha Pass |
E496428
|
entity |
| Predicate | distanceToPonchaSprings |
P138693
|
FINISHED |
| Object | about 6 miles south |
—
|
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 6 miles south | Statement: [Poncha Pass, distanceToPonchaSprings, about 6 miles south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToPonchaSprings Context triple: [Poncha Pass, distanceToPonchaSprings, about 6 miles south]
-
A.
distanceToPueblo
Indicates the measured spatial distance between a given entity and the location identified as Pueblo.
-
B.
distanceToPalmSprings
Indicates the spatial distance between a given location or entity and Palm Springs.
-
C.
distanceFromSocorro
Indicates the spatial distance between an entity and the reference location Socorro.
-
D.
distanceFromDenver
Indicates the measured distance between a given location and Denver.
-
E.
distanceFromSaltLakeCity
Indicates the measured distance between a given location and Salt Lake City.
- 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_69da626eee3881909f3454986d4a6511 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6666d83448190b3ade3f5b855e820 |
completed | April 20, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69e54cf788188190a46cc49c9ce7617f |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc2bc3c819088c33cd263303433 |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 11:25 p.m.