Triple
T17388027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Hamilton, 2nd Duke of Hamilton |
E422739
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Privy Council of Scotland |
C2232
|
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: member of the Privy Council of Scotland Context triple: [James Hamilton, 2nd Duke of Hamilton, instanceOf, member of the Privy Council of Scotland]
-
A.
Privy Councillor
chosen
A Privy Councillor is a senior advisor appointed to a sovereign or head of state, serving on a formal council that provides confidential counsel on matters of governance and policy.
-
B.
Lord President of the Council (UK)
The Lord President of the Council is a senior UK Cabinet minister who presides over the Privy Council and oversees its formal advisory and regulatory functions on behalf of the monarch and government.
-
C.
High Steward of Scotland
The High Steward of Scotland was a hereditary noble office responsible for managing the royal household and estates, which evolved into the dynastic title held by the Stewart (later Stuart) family who became kings of Scotland and England.
-
D.
Scottish nobleman
A Scottish nobleman is a male member of the Scottish aristocracy who holds a hereditary or granted title, land, and social status within Scotland’s traditional feudal hierarchy.
-
E.
member of the House of Lords
A member of the House of Lords is an appointed or hereditary individual who serves in the upper chamber of the UK Parliament, participating in the review, amendment, and scrutiny of legislation and public policy.
- 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_69d889d710288190bf0f4762801fefae |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:45 a.m.