Triple
T35898783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hermannsdalstinden |
E1038296
|
entity |
| Predicate | hikingRouteDifficulty |
P24163
|
FINISHED |
| Object | demanding |
—
|
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: demanding | Statement: [Hermannsdalstinden, hikingRouteDifficulty, demanding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hikingRouteDifficulty Context triple: [Hermannsdalstinden, hikingRouteDifficulty, demanding]
-
A.
hasTrailDifficulty
chosen
Indicates the level of challenge or effort required to traverse a particular trail or route.
-
B.
difficultyRelativeToOtherRoutes
Indicates how the difficulty level of one route compares relative to other routes.
-
C.
относитсяККатегорииСложностиВосхождений
Indicates that something is associated with a specific category of climbing difficulty.
-
D.
summitDifficulty
Indicates the level of challenge or effort required to reach the summit of something (typically a mountain or peak).
-
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_69f76e2190f88190beb2eed798a4ef01 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa3fa14481908bec1d91189891fb |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:07 p.m.