Triple
T37908384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drachenwand |
E945617
|
entity |
| Predicate | viaFerrataDifficulty |
P44457
|
FINISHED |
| Object | intermediate |
—
|
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: intermediate | Statement: [Drachenwand, viaFerrataDifficulty, intermediate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viaFerrataDifficulty Context triple: [Drachenwand, viaFerrataDifficulty, intermediate]
-
A.
primaryClimbingDifficulty
chosen
Indicates the main level of challenge or technical difficulty associated with a climbing route or problem.
-
B.
относитсяККатегорииСложностиВосхождений
Indicates that something is associated with a specific category of climbing difficulty.
-
C.
typeOfClimb
Indicates the specific style or category of climbing activity associated with a climb (e.g., bouldering, sport, trad).
-
D.
climbingDifficultyContext
Indicates the contextual conditions or factors (such as environment, route type, or situation) under which a climbing difficulty assessment applies.
-
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_69f76ef20bb0819088b5b6ceecb0b8fc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.