Triple
T34281450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Gorge Region |
E879599
|
entity |
| Predicate | approxDistanceToColoradoSprings |
P199028
|
FINISHED |
| Object | about 50–60 miles southwest |
—
|
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 50–60 miles southwest | Statement: [Royal Gorge Region, approxDistanceToColoradoSprings, about 50–60 miles southwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approxDistanceToColoradoSprings Context triple: [Royal Gorge Region, approxDistanceToColoradoSprings, about 50–60 miles southwest]
-
A.
distanceFromDenver
Indicates the measured distance between a given location and Denver.
-
B.
distanceToFortCollins
Indicates the spatial distance between a given entity’s location and the city of Fort Collins.
-
C.
distanceToGreeley
Indicates the measured distance between a given entity or location and Greeley.
-
D.
distanceToPonchaSprings
Indicates the measured distance between a given entity’s location and the location of Poncha Springs.
-
E.
distanceTo Aspen, Colorado
Indicates the measured or calculated spatial distance between a given entity and the location Aspen, Colorado.
- 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_69f349b5f6648190b9420d94a4cd16e0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff1ba8694481909ceb36f26ca85612 |
completed | May 9, 2026, 11:34 a.m. |
| PD | Predicate disambiguation | batch_69ff1b27f0f08190a9e74308c5b3d1ba |
completed | May 9, 2026, 11:31 a.m. |
| PDg | Predicate description generation | batch_69ff1ba7494481908678a7a0f93dbd03 |
completed | May 9, 2026, 11:33 a.m. |
Created at: May 1, 2026, 1:57 a.m.