Triple
T26263426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hohbalmgletscher |
E656913
|
entity |
| Predicate | climbingRouteOf |
P134321
|
FINISHED |
| Object | Nadelhorn normal routes vicinity |
—
|
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: Nadelhorn normal routes vicinity | Statement: [Hohbalmgletscher, climbingRouteOf, Nadelhorn normal routes vicinity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: climbingRouteOf Context triple: [Hohbalmgletscher, climbingRouteOf, Nadelhorn normal routes vicinity]
-
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.
hasClimbingRoutesOn
chosen
Indicates that one entity possesses or features climbing routes located on another entity (such as a rock face, wall, or structure).
-
C.
climbingRouteName
Indicates that a climbing route is associated with a specific name by which it is identified.
-
D.
primaryClimbingRouteFor
Indicates that one climbing route is the main or most commonly used route for ascending a particular climbing objective or feature.
-
E.
hasNumberOfClimbingRoutes
Indicates the quantity of climbing routes that are associated with or available at a given entity.
- 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_69ee5b4e21bc819082be98bc9ab09796 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f6430a93a48190854ce71df680b2fa |
completed | May 2, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69f641da05b881909f6283c988639c53 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 26, 2026, 9:10 p.m.