Triple
T21421845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conseil privé |
E528455
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | institution de l’Ancien Régime français |
C34472
|
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: institution de l’Ancien Régime français Context triple: [Conseil privé, instanceOf, institution de l’Ancien Régime français]
-
A.
institution of the Ancien Régime
chosen
An institution of the Ancien Régime is a formal political, social, legal, or economic structure that organized and upheld the hierarchical, monarchic order of pre-revolutionary France and comparable early modern European societies.
-
B.
office de la monarchie française
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.
constable of France
The constable of France was the kingdom’s highest military officer, responsible for commanding the royal armies and overseeing martial affairs directly under the king.
-
D.
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.
-
E.
government of France
The government of France is the political and administrative system through which the French Republic is governed, comprising the executive, legislative, and judicial branches that create, implement, and interpret laws and policies.
- 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_69e0c455f3688190810bc96365791b0f |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 5:48 p.m.