Triple
T3954601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Household Gardens Team |
E84947
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | department 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: department of the Royal Household Context triple: [Royal Household Gardens Team, instanceOf, department 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.
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.
-
D.
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.
-
E.
royal foundation
A royal foundation is an institution, endowment, or organization established and supported by a monarch or royal family to promote charitable, cultural, educational, or religious objectives.
- 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_69aed934fbfc8190847068e4546de963 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:30 p.m.