Triple
T16705595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office of the Marshal of the Court |
E405959
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | department of the Swedish Royal Court |
C1556
|
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: department of the Swedish Royal Court Context triple: [Office of the Marshal of the Court, instanceOf, department of the Swedish Royal Court]
-
A.
royal court
chosen
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.
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.
-
C.
Swedish court
A Swedish court is a judicial body in Sweden responsible for interpreting and applying the law, resolving disputes, and ensuring justice in accordance with Swedish legal principles.
-
D.
Swedish government cabinet
The Swedish government cabinet is the collective executive body composed of the Prime Minister and appointed ministers who lead government ministries and are responsible for implementing national policies and decisions in Sweden.
-
E.
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.
- 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_69d8838db21081909589220fd71440a4 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:19 a.m.