Triple
T10342826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marina Mniszech |
E243667
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | tsaritsa consort of Russia |
C1535
|
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: tsaritsa consort of Russia Context triple: [Marina Mniszech, instanceOf, tsaritsa consort of Russia]
-
A.
Empress consort of Russia
chosen
The Empress consort of Russia was the wife of the reigning Russian emperor (tsar), holding a high ceremonial and social status at court, often influencing politics, culture, and dynastic affairs without ruling in her own right.
-
B.
Empress of Russia
The Empress of Russia is the female sovereign ruler or consort at the apex of the Russian imperial hierarchy, embodying supreme political authority, dynastic continuity, and ceremonial leadership within the Russian Empire.
-
C.
Russian grand duchess
A Russian grand duchess is a female member of the Russian imperial family, typically the daughter or granddaughter of a tsar, holding high noble rank and associated with significant social and political status in the Russian Empire.
-
D.
Grand Duchess of Russia
A Grand Duchess of Russia is a female member of the Russian imperial family, typically the daughter or granddaughter of a reigning emperor (tsar) or sometimes the wife of a grand duke, holding high dynastic rank and social status within the empire.
-
E.
Despotess consort
A despotess consort is the spouse or partner of an absolute female ruler, wielding influence and status derived from her intimate association with the despotess’s autocratic power.
- 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_69d381b22b8c8190aaed476be5f872a9 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:55 a.m.