Triple
T5491724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hereditary Master of the Household in Scotland |
E123717
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Scottish royal household office |
C8198
|
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 royal household office Context triple: [Hereditary Master of the Household in Scotland, instanceOf, Scottish royal household office]
-
A.
unit of the Royal Household
A unit of the Royal Household is an organizational subdivision responsible for specific administrative, ceremonial, or domestic functions that support the sovereign and the functioning of the royal court.
-
B.
position in the British Royal Household
chosen
A position in the British Royal Household is an official role, either ceremonial or administrative, that supports the functions, representation, and daily operations of the monarchy.
-
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.
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.
-
E.
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.
- 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_69bd464a2d908190869324ce176779c8 |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 2:10 p.m.