Triple
T18678691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prisojnik |
E456669
|
entity |
| Predicate | isClimbingGradeRange |
P48053
|
FINISHED |
| Object | varied, from moderate to very difficult 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: varied, from moderate to very difficult routes | Statement: [Prisojnik, isClimbingGradeRange, varied, from moderate to very difficult routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isClimbingGradeRange Context triple: [Prisojnik, isClimbingGradeRange, varied, from moderate to very difficult routes]
-
A.
climbingGradeContext
Indicates the grading system or contextual scale used to express the difficulty rating of a climb.
-
B.
climbedInRange
Indicates that an entity’s climbing activity occurred within a specified range of values, such as time, distance, or elevation.
-
C.
climbingClass
Indicates the difficulty or grade level assigned to a climbing route, problem, or activity.
-
D.
typeOfClimb
Indicates the specific style or category of climbing activity associated with a climb (e.g., bouldering, sport, trad).
-
E.
climbingClassification
chosen
Indicates the difficulty rating or grade assigned to 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_69d8d391eb488190ac2e9abf5bf255e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e55b26cb408190a4e209c0d4ff31ba |
completed | April 19, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_69e478db7a248190a8c6584673773923 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:48 a.m.