Triple
T24300087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hardy |
E606068
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Scottish mountaineering list |
C6595
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Scottish mountaineering list Context triple: [Hardy, instanceOf, Scottish mountaineering list]
-
A.
mountain list
chosen
A mountain list is a collection of mountains, typically organized with details such as names, elevations, locations, and other relevant attributes for reference or comparison.
-
B.
mountaineering route collection
A mountaineering route collection is an organized set of documented climbing routes, typically grouped by region, mountain, or difficulty, used for planning, reference, and comparison by climbers and expedition planners.
-
C.
mountaineering feature
A mountaineering feature is any distinct natural or artificial element of mountainous terrain—such as ridges, faces, couloirs, or fixed anchors—that significantly influences route selection, difficulty, and safety in climbing and alpine travel.
-
D.
mountainGeography
mountainGeography represents the physical characteristics, spatial distribution, and environmental relationships of mountainous regions, including their formation, terrain features, and influence on climate and ecosystems.
-
E.
Scottish mountain feature
A Scottish mountain feature is a distinct natural landform found within Scotland’s upland and highland landscapes, such as peaks, ridges, corries, glens, and crags, typically shaped by glacial and erosional processes.
- F. None of above.
Provenance (1 batch)
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_69e29549335881909cbf27adcaba1cf0 |
completed | April 17, 2026, 8:17 p.m. |
Created at: April 18, 2026, 12:09 a.m.