Triple
T22590624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Peak |
E564936
|
entity |
| Predicate | usualClimbingRoute |
P92303
|
FINISHED |
| Object | glacier and snow climb |
—
|
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: glacier and snow climb | Statement: [West Peak, usualClimbingRoute, glacier and snow climb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usualClimbingRoute Context triple: [West Peak, usualClimbingRoute, glacier and snow climb]
-
A.
climbingRoute
Indicates a relationship where a path or sequence of holds is designated for ascending a surface, typically in rock climbing or similar activities.
-
B.
standardClimbingRouteType
Indicates the classification of a climbing route according to a recognized grading or style system.
-
C.
climbingDifficultyStandardRoute
Indicates the level of difficulty associated with ascending via the standard or most commonly used route.
-
D.
primaryClimbingRouteFor
chosen
Indicates that one climbing route is the main or most commonly used route for ascending a particular climbing objective or feature.
-
E.
hasClimbingRoutesOn
Indicates that one entity possesses or features climbing routes located on another entity (such as a rock face, wall, or structure).
- 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_69e245836014819091b91ed3074742a3 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f16160651081909d23735336fd7a16 |
completed | April 29, 2026, 1:39 a.m. |
| PD | Predicate disambiguation | batch_69ee627be4248190889a88764624e174 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 2:48 p.m.