Triple
T4240590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lothian |
E95402
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | traditional region of Scotland |
C10892
|
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: traditional region of Scotland Context triple: [Lothian, instanceOf, traditional region of Scotland]
-
A.
region of Scotland
chosen
A region of Scotland is a geographically defined area within the country characterized by shared administrative boundaries, cultural identity, and physical landscape features.
-
B.
historic county of Scotland
A historic county of Scotland is a traditional territorial division that once served as an administrative and cultural unit, often retaining significance for identity, geography, and historical reference despite no longer having formal governmental functions.
-
C.
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.
-
D.
Scottish clan
A Scottish clan is a traditional kinship group originating in the Scottish Highlands, united by a shared surname, ancestry (real or assumed), territory, and allegiance to a hereditary chief.
-
E.
Scottish Parliament electoral region
A Scottish Parliament electoral region is a large geographic area of Scotland used to elect additional members to the Scottish Parliament under the proportional representation element of its mixed-member electoral system.
- 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_69b3453d91548190b4d4ef8fe52aa2ac |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:05 p.m.