Triple
T12863281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Casimir I the Restorer |
E307649
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Piast dynasty monarch |
C12762
|
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 monarch Context triple: [Casimir I the Restorer, instanceOf, Piast dynasty monarch]
-
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
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.
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.
-
D.
Polish duke
A Polish duke is a high-ranking nobleman in Poland, historically holding significant territorial authority, political influence, and social prestige within the Polish–Lithuanian Commonwealth or earlier Piast and Jagiellonian realms.
-
E.
Piast duke
chosen
A Piast duke is a member of the early medieval Polish ruling dynasty who governed a duchy within the fragmented Piast-ruled territories, typically holding both military and administrative authority.
- 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_69d7bdf5e7cc8190be357278bc5ba3bb |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:37 p.m.