Triple
T24300097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Highlands (Scottish mountains classification) |
E606069
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Scottish mountain region |
C8950
|
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 mountain region Context triple: [Southern Highlands (Scottish mountains classification), instanceOf, Scottish mountain region]
-
A.
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.
-
B.
region of Scotland
A region of Scotland is a geographically defined area within the country characterized by shared administrative boundaries, cultural identity, and physical landscape features.
-
C.
town in Scotland
A town in Scotland is a moderately sized, historically rooted settlement that serves as a local center for housing, commerce, services, and community life within the Scottish cultural and administrative landscape.
-
D.
mountain region
chosen
A mountain region is a large geographic area characterized by elevated terrain, significant relief, and distinct climatic and ecological conditions associated with mountainous landscapes.
-
E.
Lowland Scottish clan
A Lowland Scottish clan is a kinship-based social group from the Lowlands of Scotland, historically organized around a shared surname, territory, and leadership, but generally more feudal and less Gaelic in culture than Highland clans.
- 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.