Triple
T34978789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commander of the Imperial Guard (Russia) |
E1008756
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | imperial court position |
C4989
|
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: imperial court position Context triple: [Commander of the Imperial Guard (Russia), instanceOf, imperial court position]
-
A.
imperial court title
An imperial court title is a formal designation granted within an empire’s ruling hierarchy that defines an individual’s rank, duties, and privileges in relation to the sovereign and the central administration.
-
B.
imperial court office
chosen
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.
imperial official
An imperial official is a government functionary appointed by a sovereign empire to administer its laws, collect revenues, and enforce imperial authority within a designated jurisdiction.
-
D.
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.
-
E.
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.
- 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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.