Triple
T24699339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borah Peak Trailhead |
E611686
|
entity |
| Predicate | accessesElevationGainToSummit |
P94224
|
FINISHED |
| Object | over 5000 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: over 5000 feet | Statement: [Borah Peak Trailhead, accessesElevationGainToSummit, over 5000 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessesElevationGainToSummit Context triple: [Borah Peak Trailhead, accessesElevationGainToSummit, over 5000 feet]
-
A.
elevationGainFunction
Indicates a functional relationship that maps a path, route, or movement to the total amount of elevation gained along it.
-
B.
totalAscent
Indicates the total cumulative elevation gained over the course of a movement, route, or activity.
-
C.
hasApproxElevationGainFt
chosen
Indicates that one entity is associated with an approximate amount of elevation gain, measured in feet, relative to another context or reference.
-
D.
distanceToSummit
Indicates the measured or estimated distance remaining from a given point to the summit of a feature or elevation.
-
E.
elevationGainRelativeToBase
Indicates the amount of elevation increase of something compared to a defined base level.
- 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_69e2c4d76d148190b58ad612467149a5 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f422aee0408190899efe7e24ef2b40 |
completed | May 1, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f420e92cc88190a803aecdae78a051 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 3:22 a.m.