Triple
T21799888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sheriffdom of Grampian, Highland and Islands |
E538209
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Scottish judicial area |
C45317
|
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 judicial area Context triple: [Sheriffdom of Grampian, Highland and Islands, instanceOf, Scottish judicial area]
-
A.
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.
-
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.
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.
-
D.
Scottish legal case
A Scottish legal case is a formal dispute brought before a Scottish court or tribunal to interpret and apply Scots law to specific facts and determine the rights and obligations of the parties involved.
-
E.
Scottish legal office
A Scottish legal office is an organization or department in Scotland that provides legal services, advice, and representation in accordance with Scots law, often handling matters such as litigation, conveyancing, and regulatory compliance.
- F. None of above. chosen
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_69e0c4733f4081909a86622e7e6d15d2 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:53 p.m.