Triple
T10039271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archchancellor of the Empire |
E205252
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | great office of state |
C4786
|
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: great office of state Context triple: [Archchancellor of the Empire, instanceOf, great office of state]
-
A.
great officer of state
chosen
A great officer of state is a high-ranking official who holds one of the most senior ceremonial or executive positions within a government or royal household, often with historic and constitutional significance.
-
B.
officer of state
An officer of state is a high-ranking public official who holds a formal position within a government or monarchy, responsible for executing specific constitutional, administrative, or ceremonial duties of the state.
-
C.
head of state office
The head of state office is an organizational unit responsible for supporting, advising, and coordinating the official duties, ceremonial functions, and administrative activities of a nation's head of state.
-
D.
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.
-
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_69ca834f70e88190b2d74828b7767ec1 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 8:55 p.m.