Triple
T3474658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cabinet Secretaries (Scottish Government) |
E73342
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | senior government ministerial position |
C6963
|
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: senior government ministerial position Context triple: [Cabinet Secretaries (Scottish Government), instanceOf, senior government ministerial position]
-
A.
cabinet-level government post
A cabinet-level government post is a senior executive position, typically heading a major department or ministry, that advises the head of government and helps formulate and implement national policy.
-
B.
Cabinet position
chosen
A cabinet position is a high-level government role, typically heading an executive department, appointed to advise and assist the chief executive in implementing public policy.
-
C.
head of government position
A head of government position is a formal political role that holds primary executive authority to lead and manage the administration and implement public policy within a sovereign state or jurisdiction.
-
D.
public administration position
A public administration position is a role within government or public sector organizations responsible for planning, implementing, and managing policies and services that serve the public interest.
-
E.
great officer of state
A great officer of state is a high-ranking official who holds one of the most senior ceremonial or executive positions within a government or royal household, often with historic and constitutional significance.
- 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_69ad85b2fed48190948c8765e453d270 |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:17 p.m.