Triple
T36206131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prefects of the Palace |
E1047401
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | position in the imperial household |
C4989
|
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: position in the imperial household Context triple: [Prefects of the Palace, instanceOf, position in the imperial household]
-
A.
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.
-
B.
member of the Royal Household
A member of the Royal Household is an individual who serves the reigning monarch or royal family in an official capacity, performing administrative, ceremonial, personal, or domestic duties within the royal establishment.
-
C.
imperial court office
chosen
An imperial court office is an administrative position or bureau within an empire’s central government responsible for managing specific functions of state, such as finance, justice, ceremony, or military affairs, under the authority of the sovereign.
-
D.
component of the Russian imperial household
A component of the Russian imperial household is an organizational unit, role, or institution that formed part of the administrative, ceremonial, or domestic structure serving the Russian emperor and his family.
-
E.
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.
- 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_69f76e4214748190a76c986d2a1838c2 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:09 p.m.