Triple
T32979567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Даниил Александрович |
E843758
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Рюрикович |
C58016
|
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: Рюрикович Context triple: [Даниил Александрович, instanceOf, Рюрикович]
-
A.
Рюрикович
chosen
Рюрикович — это династия восточнославянских князей, ведущая своё происхождение от легендарного варяжского князя Рюрика и правившая на Руси с IX по XVI век.
-
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.
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.
-
D.
Grand Prince of Vladimir
The Grand Prince of Vladimir was the supreme ruler of the medieval principality of Vladimir-Suzdal, holding preeminent authority among the Rus’ princes and serving as a key predecessor to the centralized Russian monarchy.
-
E.
Prince of Ryazan
The "Prince of Ryazan" is a conceptual class representing a medieval Russian ruler who governs the principality of Ryazan, embodying political authority, military leadership, and dynastic lineage within the historical context of Kievan and post-Kievan Rus.
- 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_69f3494c6f9c8190a255409fce8b1d3b |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:22 a.m.