Triple
T3317321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yurievichi |
E69711
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Rurikid dynasty branch |
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: Rurikid dynasty branch Context triple: [Yurievichi, instanceOf, Rurikid dynasty branch]
-
A.
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.
-
B.
Polish dynasty
A Polish dynasty is a hereditary ruling family originating from Poland that holds political power and influence over the country or its territories across successive generations.
-
C.
Capetian dynasty member
A Capetian dynasty member is an individual belonging by blood or legitimate descent to the royal house founded by Hugh Capet, which ruled France and various European realms from the late 10th century onward.
-
D.
Carolingian dynasty member
A Carolingian dynasty member is an individual belonging to the Frankish royal family that ruled large parts of Western and Central Europe from the 8th to 10th centuries, originating with Charles Martel and reaching its height under Charlemagne.
-
E.
Russian principality
A Russian principality is a semi-autonomous medieval or early modern territorial state ruled by a prince within the broader political and cultural sphere of Rus', often owing allegiance to a grand prince or tsar.
- 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_69ad85a0bb048190a5458d2738012d61 |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:11 p.m.