Triple
T3168419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord President of the Court of Session |
E66266
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Scottish public office |
C12366
|
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 public office Context triple: [Lord President of the Court of Session, instanceOf, Scottish public office]
-
A.
Scottish minister
A Scottish minister is a clergy member, typically of the Church of Scotland or another Scottish denomination, responsible for leading worship, preaching, administering sacraments, and providing spiritual and pastoral care within a Scottish congregation or parish.
-
B.
member of the Scottish Parliament
A member of the Scottish Parliament is an elected representative who serves in the Scottish Parliament, participating in law-making, scrutiny of the Scottish Government, and representation of a specific constituency or region in Scotland.
-
C.
government agency of Scotland
A government agency of Scotland is an official public body established by the Scottish Government to implement policies, deliver public services, and regulate specific sectors within Scotland.
-
D.
Scottish Parliament constituency
A Scottish Parliament constituency is a geographically defined electoral area in Scotland that elects one Member of the Scottish Parliament (MSP) to represent its residents in the devolved national legislature.
-
E.
position in the Church of Scotland
A position in the Church of Scotland represents an official role or office within its Presbyterian governance and ministry structure, such as minister, elder, or deacon.
- 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_69ad8585d7988190af37365331093ccd |
completed | March 8, 2026, 2:19 p.m. |
Created at: March 8, 2026, 3:06 p.m.