Triple
T19086217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laliderer Spitze |
E467154
|
entity |
| Predicate | difficultyOfNormalRoute |
P4582
|
FINISHED |
| Object | UIAA I–II |
—
|
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: UIAA I–II | Statement: [Laliderer Spitze, difficultyOfNormalRoute, UIAA I–II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: difficultyOfNormalRoute Context triple: [Laliderer Spitze, difficultyOfNormalRoute, UIAA I–II]
-
A.
climbingDifficultyStandardRoute
chosen
Indicates the level of difficulty associated with ascending via the standard or most commonly used route.
-
B.
difficultyRelativeToOtherRoutes
Indicates how the difficulty level of one route compares relative to other routes.
-
C.
hasTrailDifficulty
Indicates the level of challenge or effort required to traverse a particular trail or route.
-
D.
durationTypicalAscent
Indicates the typical amount of time required to complete an ascent.
-
E.
climbingDifficultyContext
Indicates the contextual conditions or factors (such as environment, route type, or situation) under which a climbing difficulty assessment applies.
- 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_69d8dd05ac4c8190b1967d8f97f3fb2f |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e347ee288190a3e935ff89ca94aa |
completed | April 20, 2026, 8:26 a.m. |
| PD | Predicate disambiguation | batch_69e4b9a604308190a3235184f9f2c056 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:04 p.m.