Triple
T24119562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Königspitze |
E597613
|
entity |
| Predicate | isClimbingGrade |
P19708
|
FINISHED |
| Object | difficult and serious alpine routes |
—
|
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: difficult and serious alpine routes | Statement: [Königspitze, isClimbingGrade, difficult and serious alpine routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isClimbingGrade Context triple: [Königspitze, isClimbingGrade, difficult and serious alpine routes]
-
A.
climbingGradeContext
Indicates the grading system or contextual scale used to express the difficulty rating of a climb.
-
B.
climbingClass
chosen
Indicates the difficulty or grade level assigned to a climbing route, problem, or activity.
-
C.
typeOfClimb
Indicates the specific style or category of climbing activity associated with a climb (e.g., bouldering, sport, trad).
-
D.
canClimb
Indicates that one entity has the ability or permission to climb another entity or surface.
-
E.
primaryClimbingDifficulty
Indicates the main level of challenge or technical difficulty associated with a climbing route or problem.
- 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_69e288c74200819098ab875b592cb39f |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dee1a2608190870ade02495c5ebe |
completed | April 29, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:05 p.m.