Triple
T27490651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rostislava Mstislavna of Smolensk |
E693874
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Grand Princess consort of Vladimir |
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 Vladimir Context triple: [Rostislava Mstislavna of Smolensk, instanceOf, Grand Princess consort of Vladimir]
-
A.
Grand Princess consort of Moscow
The Grand Princess consort of Moscow is the wife of the ruling Grand Prince of Moscow, serving as his principal consort and often playing a significant role in dynastic alliances, court politics, and the cultural life of the Muscovite state.
-
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.
Moldavian princess
A Moldavian princess is a noblewoman of royal or princely rank from the historical principality of Moldavia, often associated with dynastic alliances, courtly life, and regional political influence in Eastern Europe.
-
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.
Margravine consort of Moravia
A Margravine consort of Moravia is the wife of the ruling margrave of Moravia, holding a ceremonial and often influential position within the region’s medieval or early modern nobility.
- 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_69ef5382b9648190be0b1ef2ad5d043c |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 27, 2026, 1:05 p.m.