Triple
T37766094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saser Kangri III |
E941417
|
entity |
| Predicate | climbingDifficultyGrade |
P44457
|
FINISHED |
| Object | high-technical |
—
|
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: high-technical | Statement: [Saser Kangri III, climbingDifficultyGrade, high-technical]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: climbingDifficultyGrade Context triple: [Saser Kangri III, climbingDifficultyGrade, high-technical]
-
A.
primaryClimbingDifficulty
chosen
Indicates the main level of challenge or technical difficulty associated with a climbing route or problem.
-
B.
climbingDifficultyContext
Indicates the contextual conditions or factors (such as environment, route type, or situation) under which a climbing difficulty assessment applies.
-
C.
climbingGradeContext
Indicates the grading system or contextual scale used to express the difficulty rating of a climb.
-
D.
typeOfClimb
Indicates the specific style or category of climbing activity associated with a climb (e.g., bouldering, sport, trad).
-
E.
climbingGradesRange
Indicates the range of difficulty grades that apply to a climbing route, problem, or area.
- 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_69f76ee3251881909bb4451aad50752b |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.