Triple
T27058925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roaring Springs |
E684980
|
entity |
| Predicate | approxElevationChangeFromNorthRim |
P6813
|
FINISHED |
| Object | about 3000 feet descent |
—
|
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 3000 feet descent | Statement: [Roaring Springs, approxElevationChangeFromNorthRim, about 3000 feet descent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approxElevationChangeFromNorthRim Context triple: [Roaring Springs, approxElevationChangeFromNorthRim, about 3000 feet descent]
-
A.
elevationRelativeToCanyon
Indicates the relative height or altitude of one location compared to the canyon’s reference level.
-
B.
elevationNorthPortal
Indicates the vertical height or altitude measured at the northern portal of a structure or passage.
-
C.
elevationChange
chosen
Indicates a change in vertical position or altitude between two points or states.
-
D.
elevationRelativeToCanyonFloor
Indicates the vertical height or altitude of something measured relative to the canyon floor as the reference level.
-
E.
elevationAtRim
Indicates the elevation value measured specifically at the rim or edge of a geographic or topographic feature.
- 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_69ef14829fac8190914bef9ecc3005d7 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: April 27, 2026, 8:20 a.m.