Triple
T14144203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Écuyer de France |
E350501
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ancien Régime 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: Ancien Régime office Context triple: [Grand Écuyer de France, instanceOf, Ancien Régime office]
-
A.
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.
-
B.
colonial office
A colonial office is a governmental department or administrative body responsible for managing and overseeing the affairs, policies, and governance of a colony or group of colonies on behalf of a colonial power.
-
C.
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.
-
D.
medieval public office
A medieval public office is an institutional role within the governance structures of the Middle Ages, endowed with specific legal authority, duties, and privileges to administer justice, manage resources, or represent sovereign power on behalf of a ruler or community.
-
E.
imperial institution
An imperial institution is a formal organization or structure established by an empire to administer, control, and legitimize its authority over territories and populations.
- 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_69d827865f608190b311820428ae027b |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 12:53 a.m.