Triple
T33811845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maria Feodorovna Nagaya |
E866556
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | consort of Ivan IV of Russia |
C64683
|
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: consort of Ivan IV of Russia Context triple: [Maria Feodorovna Nagaya, instanceOf, consort of Ivan IV of Russia]
-
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.
Grand Prince of Moscow
The Grand Prince of Moscow was the medieval ruler of the Grand Duchy of Moscow, who gradually consolidated Russian lands, led resistance against foreign domination, and laid the foundations for a centralized Russian state.
-
C.
ruler of Tver
The ruler of Tver is the sovereign authority governing the Principality of Tver, responsible for its political leadership, military command, and administration of justice within its territories.
-
D.
member of the House of Moscow
A member of the House of Moscow is an individual belonging to a noble or ruling dynasty historically associated with governing and influencing the political, social, and cultural life of Moscow.
-
E.
Muscovite boyar
A Muscovite boyar was a high-ranking noble in medieval and early modern Muscovy who held extensive land, political influence, and advisory roles at the tsar’s court.
- 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_69f349911a8c81908478662194b23d8c |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:46 a.m.