Triple
T34924055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maria Dobroniega of Kiev |
E1007227
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Kievan Rusʼ princess |
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: Kievan Rusʼ princess Context triple: [Maria Dobroniega of Kiev, instanceOf, Kievan Rusʼ princess]
-
A.
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.
-
B.
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.
-
C.
Tatar princess
A Tatar princess is a noblewoman of Tatar heritage, traditionally embodying the political influence, cultural refinement, and lineage of Tatar royal or aristocratic families.
-
D.
Lithuanian princess
A Lithuanian princess is a noblewoman of royal or high-ranking lineage from Lithuania, often associated with the country’s medieval Grand Duchy, its cultural heritage, and dynastic alliances.
-
E.
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.
- 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_69f76dc3d83881909d5c3c14455cfa2c |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4 p.m.