Triple
T5778099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belukha Mountain |
E127493
|
entity |
| Predicate | hasClimbingGrade |
P19708
|
FINISHED |
| Object | alpine PD–AD (varies by 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: alpine PD–AD (varies by route) | Statement: [Belukha Mountain, hasClimbingGrade, alpine PD–AD (varies by route)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClimbingGrade Context triple: [Belukha Mountain, hasClimbingGrade, alpine PD–AD (varies by route)]
-
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.
canClimb
Indicates that one entity has the ability or permission to climb another entity or surface.
-
D.
primaryClimbingDifficulty
Indicates the main level of challenge or technical difficulty associated with a climbing route or problem.
-
E.
hasClimbsCount
Indicates that an entity is associated with a specific number of climbs it has completed or is credited with.
- 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_69c008361fa88190aefa4dc41b051e7f |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02acb12c081908e4beee4a957f9f9 |
completed | March 22, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69c021d0c6088190ba670ddcdbf5ca3e |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:50 p.m.