Triple
T15483037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vladimir-Suzdal Yurievichi |
E376969
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Rus' ruling house |
C13641
|
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 Rus' ruling house Context triple: [Vladimir-Suzdal Yurievichi, instanceOf, medieval Rus' ruling house]
-
A.
medieval ruling family
A medieval ruling family is a hereditary dynasty that holds political power, land, and social authority over a realm, often legitimized by lineage, religion, and military strength.
-
B.
Rurikid princely branch
A Rurikid princely branch is a dynastic line descending from the medieval Rurikid ruling family, typically associated with governance over a specific principality or territory in Kievan Rus’ and its successor states.
-
C.
medieval Rus’ title
A medieval Rus’ title is a formal designation of rank, office, or nobility used in the political and social hierarchy of the East Slavic principalities from roughly the 9th to the 15th centuries.
-
D.
medieval Bulgarian dynasty
A medieval Bulgarian dynasty is a ruling family that governed the Bulgarian state during the Middle Ages, shaping its political structure, territorial expansion, cultural development, and relations with neighboring powers.
-
E.
Rurikid dynasty branch
chosen
A Rurikid dynasty branch is a lineage subgroup descending from the medieval Rurikid ruling family, typically associated with a specific territory, princely title, and period of political influence in Eastern Europe.
- 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_69d85cd21dcc81908646251b1c26ea00 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 3:40 a.m.