Triple
T34952014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jan Lucemburský |
E1008025
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | příslušník lucemburské dynastie |
C33923
|
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: příslušník lucemburské dynastie Context triple: [Jan Lucemburský, instanceOf, příslušník lucemburské dynastie]
-
A.
Luxembourg dynasty member
chosen
A Luxembourg dynasty member is an individual belonging to the medieval European royal House of Luxembourg, which produced several Holy Roman Emperors, kings, and high-ranking nobles.
-
B.
member of the Ludovingian dynasty
A member of the Ludovingian dynasty is an individual belonging to the medieval German noble house that ruled Thuringia and held significant influence in the Holy Roman Empire from the 11th to 13th centuries.
-
C.
member of the Přemyslid dynasty
A member of the Přemyslid dynasty is an individual belonging to the medieval Czech royal house that ruled Bohemia and parts of Central Europe from the 9th to the early 14th century.
-
D.
member of the Babenberg dynasty
A member of the Babenberg dynasty is an individual belonging to the medieval noble family that ruled Austria and parts of Central Europe from the 10th to the mid-13th century.
-
E.
member of the Brunonen dynasty
A member of the Brunonen dynasty is an individual belonging to a medieval German noble family that held significant territorial and political influence in Saxony and surrounding regions during the 10th and 11th centuries.
- 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_69f76dc5d4308190b77553ee07b1ede6 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4 p.m.