Triple
T25336137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salathé Wall |
E635282
|
entity |
| Predicate | aidClimbingGrade |
P48053
|
FINISHED |
| Object | around VI 5.9 A2 (historical rating) |
—
|
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: around VI 5.9 A2 (historical rating) | Statement: [Salathé Wall, aidClimbingGrade, around VI 5.9 A2 (historical rating)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aidClimbingGrade Context triple: [Salathé Wall, aidClimbingGrade, around VI 5.9 A2 (historical rating)]
-
A.
climbingGradesRange
Indicates the range of difficulty grades that apply to a climbing route, problem, or area.
-
B.
climbingClassification
chosen
Indicates the difficulty rating or grade assigned to a climbing route or problem.
-
C.
primaryClimbingDifficulty
Indicates the main level of challenge or technical difficulty associated with a climbing route or problem.
-
D.
climbingGradeContext
Indicates the grading system or contextual scale used to express the difficulty rating of a climb.
-
E.
climbingClass
Indicates the difficulty or grade level assigned to a climbing route, problem, or activity.
- 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_69e75a99bd6481909476115b35b9a8e4 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f497ca0f18819090168e3221c2aa32 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
Created at: April 21, 2026, 1:32 p.m.