Triple
T3992701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Household Ceremonial Team |
E87028
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | part of the Royal Household |
C14428
|
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: part of the Royal Household Context triple: [Royal Household Ceremonial Team, instanceOf, part of the Royal Household]
-
A.
unit of the Royal Household
chosen
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
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.
member of a royal family
A member of a royal family is an individual related by blood, marriage, or adoption to a reigning or formerly reigning monarch, typically holding a recognized title, status, or role within the monarchy.
-
D.
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.
-
E.
royal court
A royal court is the formal assembly of a monarch’s household, advisors, officials, and attendants who support, counsel, and ceremonially represent the sovereign’s authority and governance.
- 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_69aed94118148190975e6aa4e554cde9 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:33 p.m.