Triple
T10486584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bruno, Duke of Saxony |
E247314
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Liudolfing dynasty |
C27057
|
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: member of the Liudolfing dynasty Context triple: [Bruno, Duke of Saxony, instanceOf, member of the Liudolfing dynasty]
-
A.
Ottonian dynasty member
chosen
An Ottonian dynasty member is an individual belonging to the German royal and imperial family that ruled the East Frankish (German) kingdom and Holy Roman Empire from the early 10th to early 11th centuries, beginning with Henry the Fowler and most prominently represented by Otto I, Otto II, and Otto III.
-
B.
member of the House of Welf
A member of the House of Welf is an individual belonging by birth or legitimate adoption to the historic European noble dynasty known as the Welfs, which has produced numerous dukes, princes, and monarchs.
-
C.
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.
-
D.
member of the Salian dynasty
A member of the Salian dynasty is an individual belonging to the German royal and imperial family that ruled the Holy Roman Empire from the early 11th to mid-12th century.
-
E.
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.
- 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_69d381c309b88190af78aa681cf6a4c2 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 12:23 p.m.