Triple
T12805963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuyavian Piasts |
E306144
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Polish noble house |
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: medieval Polish noble house Context triple: [Kuyavian Piasts, instanceOf, medieval Polish noble 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.
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.
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.
-
D.
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.
-
E.
Polish–Lithuanian nobleman
A Polish–Lithuanian nobleman was a member of the szlachta elite of the Polish–Lithuanian Commonwealth, holding hereditary privileges, political rights, and often landed estates within its multiethnic realm.
- 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_69d7bdf366888190a8cccb982606889c |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:31 p.m.