Triple
T20993201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yewbarrow |
E517075
|
entity |
| Predicate | hasClimbingGradeSections |
P19708
|
FINISHED |
| Object | easy scramble on Stirrup Crag |
—
|
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: easy scramble on Stirrup Crag | Statement: [Yewbarrow, hasClimbingGradeSections, easy scramble on Stirrup Crag]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClimbingGradeSections Context triple: [Yewbarrow, hasClimbingGradeSections, easy scramble on Stirrup Crag]
-
A.
climbingGradeContext
Indicates the grading system or contextual scale used to express the difficulty rating of a climb.
-
B.
hasClimbs
Indicates that one entity performs or is associated with climbing activity on another entity (such as a route, structure, or surface).
-
C.
hasClimbsCount
Indicates that an entity is associated with a specific number of climbs it has completed or is credited with.
-
D.
hasClimbingRoutesOn
Indicates that one entity possesses or features climbing routes located on another entity (such as a rock face, wall, or structure).
-
E.
climbingClass
chosen
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_69e0b5006e2881909fc2383f841740cc |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc1d829081908de889c542734393 |
completed | April 21, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e5dbec80708190a49bccab7ff97e7b |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:50 p.m.