Triple
T13710256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piasts of Oleśnica |
E328751
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Silesian Piast dynasty branch |
C32403
|
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: Silesian Piast dynasty branch Context triple: [Piasts of Oleśnica, instanceOf, Silesian Piast dynasty branch]
-
A.
Silesian Piast
chosen
Silesian Piast refers to a member of the Silesian branch of the medieval Polish Piast dynasty, which ruled various duchies in the historical region of Silesia.
-
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.
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).
-
D.
Silesian duchy
A Silesian duchy is a medieval or early modern territorial principality in the historical region of Silesia, ruled by a duke and often formed through the partition of larger Polish or Bohemian realms.
-
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_69d80770b9bc81909f70c8c317d53cff |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:54 p.m.