Triple
T3463098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vladimir the Great |
E73073
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Rurik dynasty |
C12793
|
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: member of the Rurik dynasty Context triple: [Vladimir the Great, instanceOf, member of the Rurik dynasty]
-
A.
member of the House of Romanov
A member of the House of Romanov is an individual belonging by birth or marriage to the former imperial dynasty that ruled Russia from 1613 until the abdication of Tsar Nicholas II in 1917.
-
B.
member of the House of Holstein-Gottorp-Romanov
A member of the House of Holstein-Gottorp-Romanov is an individual belonging to the German-Russian dynastic branch that ruled the Russian Empire from Peter III through the last tsars, combining Holstein-Gottorp and Romanov lineage.
-
C.
member of the Přemyslid dynasty
A member of the Přemyslid dynasty is an individual belonging to the medieval Czech royal house that ruled Bohemia and parts of Central Europe from the 9th to the early 14th century.
-
D.
Romanov family member
A Romanov family member is an individual belonging by birth or marriage to the Russian imperial dynasty that ruled Russia from 1613 until the abdication of Tsar Nicholas II in 1917.
-
E.
member of the House of Holstein-Gottorp
A member of the House of Holstein-Gottorp is an individual belonging to a cadet branch of the Oldenburg dynasty that ruled or influenced territories in northern Germany, Scandinavia, and Russia through dynastic unions and successions.
- 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_69ad85b224d481908ff8be51338d24ff |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:17 p.m.