Triple
T16634371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sir Michael Stevens |
E404160
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | royal household official |
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: royal household official Context triple: [Sir Michael Stevens, instanceOf, royal household official]
-
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.
royal courtier
A royal courtier is a member of a monarch’s household who attends the ruler, manages or influences court affairs, and advances political, social, or personal interests within the royal court.
-
C.
Lord Chamberlain of the Household
The Lord Chamberlain of the Household is the senior officer of the Royal Household responsible for overseeing ceremonial events, royal protocol, and the coordination of official engagements and state occasions.
-
D.
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.
-
E.
clerk of the Privy Seal
A clerk of the Privy Seal was an official responsible for preparing, drafting, and processing documents that required authentication by the monarch’s privy seal, often serving as an intermediary between petitioners and higher offices of royal administration.
- 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_69d8838a41f08190b0c3f79c47df5078 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:17 a.m.