Triple
T5408297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great End |
E120946
|
entity |
| Predicate | commonAscentRoute |
P2405
|
FINISHED |
| Object | from Seathwaite via Sty Head |
—
|
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: from Seathwaite via Sty Head | Statement: [Great End, commonAscentRoute, from Seathwaite via Sty Head]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonAscentRoute Context triple: [Great End, commonAscentRoute, from Seathwaite via Sty Head]
-
A.
climbingRoute
chosen
Indicates a relationship where a path or sequence of holds is designated for ascending a surface, typically in rock climbing or similar activities.
-
B.
durationTypicalAscent
Indicates the typical amount of time required to complete an ascent.
-
C.
totalAscent
Indicates the total cumulative elevation gained over the course of a movement, route, or activity.
-
D.
notableAscent
Indicates that an entity is recognized for a significant rise, climb, or upward journey, such as an important ascent of a mountain or similar elevation.
-
E.
secondAscentRoute
Indicates that the related route was used for the second recorded ascent of a particular peak or climbing objective.
- 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_69bd46391c0c81909fa484446732b6a3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8794e0c4819082bebf2da5e41201 |
completed | March 20, 2026, 5:44 p.m. |
| PD | Predicate disambiguation | batch_69bd8467e6b48190b9eaa9de67072e06 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:05 p.m.