Triple
T16468628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solomonia Saburova |
E400001
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | grand princess consort of Moscow |
C12745
|
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: grand princess consort of Moscow Context triple: [Solomonia Saburova, instanceOf, grand princess consort of Moscow]
-
A.
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.
-
B.
princess of Kievan Rus'
chosen
A princess of Kievan Rus' is a high-born woman of the ruling Rurikid dynasty who played key roles in dynastic alliances, governance, and the cultural and religious life of the medieval East Slavic state.
-
C.
Grand Duchess consort of Lithuania
The Grand Duchess consort of Lithuania is the wife of the reigning Grand Duke of Lithuania, holding a ceremonial and dynastic role within the grand ducal court and state.
-
D.
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.
-
E.
Empress consort of Russia
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.
- 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_69d87f2dac988190b74d6e185fa88ba4 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:11 a.m.