Triple
T14419148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romanovichi dynasty |
E357534
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ruthenian princely 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: Ruthenian princely house Context triple: [Romanovichi dynasty, instanceOf, Ruthenian princely house]
-
A.
Polish-Lithuanian noble family
A Polish-Lithuanian noble family is a lineage belonging to the historical szlachta estate of the Polish-Lithuanian Commonwealth, characterized by hereditary titles, coats of arms, landholdings, and participation in the region’s political and social life.
-
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.
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.
-
D.
Hungarian noble family
A Hungarian noble family is a historically recognized lineage within the Kingdom of Hungary’s aristocracy, holding hereditary titles, lands, and social privileges passed down through generations.
-
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_69d82793421c8190861eb0e673b085de |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:18 a.m.