Triple
T18581183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schreckhorn Hut |
E454116
|
entity |
| Predicate | servesClimbersOf |
P100985
|
FINISHED |
| Object | Schreckhorn normal route |
—
|
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: Schreckhorn normal route | Statement: [Schreckhorn Hut, servesClimbersOf, Schreckhorn normal route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesClimbersOf Context triple: [Schreckhorn Hut, servesClimbersOf, Schreckhorn normal route]
-
A.
coClimber
Indicates that two or more entities participate together in the same climbing activity or ascent.
-
B.
isRestingSpotForClimbers
chosen
Indicates that a location serves as a place where climbers stop to rest during their climb.
-
C.
climbingArea
Indicates that one entity is a designated location or site used for climbing activities in relation to another entity.
-
D.
climbingAccess
Indicates that one entity provides permission, routes, or means for another entity to engage in climbing activities at a particular location or structure.
-
E.
hasClimbs
Indicates that one entity performs or is associated with climbing activity on another entity (such as a route, structure, or surface).
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e543cffd34819090d636fd584f51db |
completed | April 19, 2026, 9:06 p.m. |
| PD | Predicate disambiguation | batch_69e478c98d4c81909d37a0e72c6e7bd0 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:43 a.m.