Triple
T18926836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huntington Ravine |
E462995
|
entity |
| Predicate | elevationGainFromBase |
P94224
|
FINISHED |
| Object | approximately 2000 feet |
—
|
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 2000 feet | Statement: [Huntington Ravine, elevationGainFromBase, approximately 2000 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevationGainFromBase Context triple: [Huntington Ravine, elevationGainFromBase, approximately 2000 feet]
-
A.
elevationGainRelativeToBase
Indicates the amount of elevation increase of something compared to a defined base level.
-
B.
elevationAtBase
Indicates the height or altitude measured at the base or lowest point of an object or feature relative to a reference level.
-
C.
elevationGainFunction
Indicates a functional relationship that maps a path, route, or movement to the total amount of elevation gained along it.
-
D.
hasApproxElevationGainFt
chosen
Indicates that one entity is associated with an approximate amount of elevation gain, measured in feet, relative to another context or reference.
-
E.
trailheadElevation
Indicates the elevation at which a trail begins, typically measured at its starting point or trailhead.
- 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_69d8dcfdbbb881909964fa5a75bd0b48 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c9bc36588190ae9cc3b8abf8afd4 |
completed | April 20, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e9e6488190ba8df92c8058ed88 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:59 a.m.