Triple
T20768129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eudoxia of Moscow |
E511153
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Grand Princess consort of Moscow |
C44061
|
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: [Eudoxia of Moscow, instanceOf, Grand Princess consort of Moscow]
-
A.
princess of Kievan Rus'
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.
-
B.
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.
-
C.
Grand Duchess
A Grand Duchess is a noblewoman who holds the rank of grand duke in her own right or as the wife or widow of a grand duke, typically positioned just below a queen in a monarchical hierarchy.
-
D.
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.
-
E.
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.
- F. None of above. chosen
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_69e0b4ca01148190ac018e57e0cab46f |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:36 p.m.