Triple
T34275035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ludwig II. von Ungarn und Böhmen |
E879428
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mitglied des Hauses Jagiellon |
C13120
|
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: Mitglied des Hauses Jagiellon Context triple: [Ludwig II. von Ungarn und Böhmen, instanceOf, Mitglied des Hauses Jagiellon]
-
A.
Jagiellonian dynasty member
chosen
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.
-
B.
member of the Sobieski family
A member of the Sobieski family is an individual belonging by birth or legal relation to the historically significant Polish noble and royal lineage associated with the Sobieski name.
-
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.
member of the House of Lobkowicz
A member of the House of Lobkowicz is an individual belonging by birth or adoption to the historic Czech noble family of Lobkowicz, associated with significant political, cultural, and economic influence in Central Europe.
-
E.
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.
- 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_69f349b5f6648190b9420d94a4cd16e0 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:56 a.m.