Triple
T26624380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Master of the Royal Household |
E668296
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | French royal court office |
C18657
|
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: French royal court office Context triple: [Grand Master of the Royal Household, instanceOf, French royal court office]
-
A.
French royal household
The French royal household was the complex administrative and domestic organization that managed the daily life, ceremonial functions, and personal service of the king and royal family in the French monarchy.
-
B.
office de la monarchie française
chosen
An "office de la monarchie française" is a formal, often venal, administrative or judicial position within the institutional framework of the French monarchy, conferring specific duties, privileges, and social status on its holder.
-
C.
French royal order
A French royal order is an honorific institution or chivalric order established by the French monarchy to recognize and reward loyalty, military merit, or distinguished service to the crown.
-
D.
French royal
A French royal is a member of the monarchy of France, historically belonging to the ruling dynasties that held sovereign or dynastic authority over the French realm.
-
E.
imperial court office
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.
- 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_69ee9cff507c819092b95bf7219a702e |
completed | April 26, 2026, 11:17 p.m. |
Created at: April 27, 2026, 2:22 a.m.