Triple
T24699352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borah Peak Trailhead |
E611686
|
entity |
| Predicate | hazardsOnRouteFromTrailhead |
P115167
|
FINISHED |
| Object | rapid weather changes |
—
|
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: rapid weather changes | Statement: [Borah Peak Trailhead, hazardsOnRouteFromTrailhead, rapid weather changes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hazardsOnRouteFromTrailhead Context triple: [Borah Peak Trailhead, hazardsOnRouteFromTrailhead, rapid weather changes]
-
A.
hasClimbingHazard
Indicates that something presents a risk or danger specifically associated with climbing activities.
-
B.
travelHazards
chosen
Indicates that there are potential dangers, risks, or obstacles associated with traveling in a particular context or along a specific route.
-
C.
hasObjectiveHazards
Indicates that an entity is associated with concrete, externally verifiable dangers or risks.
-
D.
hazardEncountered
Indicates that an entity has come into contact with or been exposed to a potentially dangerous or harmful condition, object, or situation.
-
E.
hasTrailDifficulty
Indicates the level of challenge or effort required to traverse a particular trail or route.
- 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_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442a977b08190b44eac040cb90211 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 3:22 a.m.