Triple
T37370744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottish Ministers for Scottish Parliament boundaries |
E927835
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Scottish Government function |
C12783
|
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 Government function Context triple: [Scottish Ministers for Scottish Parliament boundaries, instanceOf, Scottish Government function]
-
A.
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.
-
B.
Scottish Government policy document
A Scottish Government policy document is an official publication that sets out the government’s objectives, principles, and planned actions on a specific public issue within Scotland.
-
C.
Scottish ministerial office
chosen
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 public office
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.
-
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_69f76eb820248190a5c395ca50ad002a |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:16 p.m.