Triple
T17998561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Justice Clerk |
E430564
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Scottish judicial 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 judicial office Context triple: [Lord Justice Clerk, instanceOf, Scottish judicial office]
-
A.
Scottish hereditary office
A Scottish hereditary office is a formal position within Scotland’s historical or legal framework that is passed down through generations of a family, often carrying ceremonial, administrative, or feudal responsibilities.
-
B.
Scottish public office
chosen
A Scottish public office is an official position within Scotland's governmental or public sector institutions, held by an individual entrusted with statutory, administrative, or representative duties on behalf of the public.
-
C.
Scottish ministerial office
A Scottish ministerial office is a governmental position within the Scottish Government held by a minister responsible for specific policy areas, administration, and decision-making in Scotland.
-
D.
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.
-
E.
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.
- 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_69d8b90364248190a37381adea932f42 |
completed | April 10, 2026, 8:46 a.m. |
Created at: April 10, 2026, 10:23 a.m.