Triple
T14144250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Aumônier de France |
E350502
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | office of the French royal court |
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: office of the French royal court Context triple: [Grand Aumônier de France, instanceOf, office of the French royal court]
-
A.
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.
-
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.
royal courtier
A royal courtier is a member of a monarch’s household who attends the ruler, manages or influences court affairs, and advances political, social, or personal interests within the royal court.
-
D.
chamber of Parliament of France
A chamber of Parliament of France is one of the two legislative assemblies—the National Assembly or the Senate—that together exercise the country’s lawmaking, oversight, and representative functions at the national level.
-
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_69d827865f608190b311820428ae027b |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 12:53 a.m.