Triple
T12742917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wrocław Piasts |
E304531
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Piast dynasty branch |
C11122
|
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: Piast dynasty branch Context triple: [Wrocław Piasts, instanceOf, Piast dynasty branch]
-
A.
Piast dynasty member
A Piast dynasty member is an individual belonging to the first historical ruling dynasty of Poland, which governed various Polish and regional territories from the 10th to the 14th century (and in some branches beyond).
-
B.
Polish dynasty
chosen
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.
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.
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.
-
E.
Jagiellonian dynasty member
A Jagiellonian dynasty member is an individual belonging to the royal house that ruled parts of Central and Eastern Europe, including Poland, Lithuania, Bohemia, and Hungary, from the late 14th to the 16th century.
- 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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:26 p.m.