Triple
T15483035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vladimir-Suzdal Yurievichi |
E376969
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | princely dynasty branch |
C12651
|
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: princely dynasty branch Context triple: [Vladimir-Suzdal Yurievichi, instanceOf, princely dynasty branch]
-
A.
dynastic branch
A dynastic branch is a subordinate line of a ruling or noble family that descends from a common ancestor but forms its own distinct lineage within the broader dynasty.
-
B.
Rurikid princely branch
chosen
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.
Rurikid dynasty branch
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.
-
D.
ducal line
A ducal line is a hereditary lineage descending from or associated with a duke, typically holding noble titles, privileges, and succession rights within a feudal or monarchical system.
-
E.
German princely dynasty
A German princely dynasty is a hereditary ruling family from the German-speaking regions of Europe that historically held princely titles, governed territories, and played significant roles in regional and imperial politics.
- 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.