Triple
T15389437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maria of Rostov |
E368000
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Russian noblewoman |
C6316
|
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: medieval Russian noblewoman Context triple: [Maria of Rostov, instanceOf, medieval Russian noblewoman]
-
A.
medieval Bulgarian noblewoman
A medieval Bulgarian noblewoman is an aristocratic female member of Bulgarian society during the Middle Ages, typically associated with landownership, political influence, and participation in courtly and religious life.
-
B.
Russian noblewoman
chosen
A Russian noblewoman is an aristocratic woman of the Russian Empire or nobility, typically distinguished by her high social rank, landowning family background, and participation in elite cultural and political life.
-
C.
medieval Georgian noblewoman
A medieval Georgian noblewoman is an aristocratic woman of the Georgian kingdoms who held social status, land-related privileges, and dynastic responsibilities within the feudal and courtly structures of the Middle Ages.
-
D.
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.
-
E.
11th-century noblewoman
An 11th-century noblewoman is a high-born female member of medieval European aristocracy whose life centers on managing estates, forging political alliances through marriage, and upholding social and religious obligations within a feudal hierarchy.
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:19 a.m.