Triple
T27649036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mardale Ill Bell |
E696795
|
entity |
| Predicate | hasPopularAscentRouteVia |
P65032
|
FINISHED |
| Object | Nan Bield Pass |
—
|
NE NERFINISHED |
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: Nan Bield Pass | Statement: [Mardale Ill Bell, hasPopularAscentRouteVia, Nan Bield Pass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPopularAscentRouteVia Context triple: [Mardale Ill Bell, hasPopularAscentRouteVia, Nan Bield Pass]
-
A.
hasPopularAscentRouteFrom
Indicates that there exists a commonly used or well-known route for ascending to a place or peak starting from the specified origin location.
-
B.
hasClimbingRoutesOn
Indicates that one entity possesses or features climbing routes located on another entity (such as a rock face, wall, or structure).
-
C.
hasNumberOfClimbingRoutes
Indicates the quantity of climbing routes that are associated with or available at a given entity.
-
D.
typicalAscentRouteVia
chosen
Indicates the usual or most commonly used route taken to ascend or reach a particular destination, such as a summit or high point.
-
E.
durationTypicalAscent
Indicates the typical amount of time required to complete an ascent.
- 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_69ef590abd3c8190834d0193bde12007 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: April 27, 2026, 2:31 p.m.