Triple
T6159358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stanage Edge |
E137401
|
entity |
| Predicate | hasClimbingRouteType |
P44664
|
FINISHED |
| Object | single-pitch 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: single-pitch routes | Statement: [Stanage Edge, hasClimbingRouteType, single-pitch routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClimbingRouteType Context triple: [Stanage Edge, hasClimbingRouteType, single-pitch routes]
-
A.
isClimbingRouteFeatureOn
Indicates that a specific climbing route feature is located on or part of a particular climbing route.
-
B.
climbingRoute
Indicates a relationship where a path or sequence of holds is designated for ascending a surface, typically in rock climbing or similar activities.
-
C.
climbingCategory
Indicates the classification level or difficulty grade assigned to a climbing route, problem, or activity.
-
D.
standardClimbingRouteType
chosen
Indicates the classification of a climbing route according to a recognized grading or style system.
-
E.
climbingActivity
Indicates an activity where an entity ascends or scales a surface, structure, or natural formation, typically using physical effort and coordination.
- 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_69c008a54fc88190b6ce4416490ca79d |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05d3445dc8190822954cee90f0dd7 |
completed | March 22, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69c055f5b81481908819515cdc334ae6 |
completed | March 22, 2026, 8:49 p.m. |
Created at: March 22, 2026, 4:17 p.m.