Triple
T20395637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry the Proud |
E500195
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Welf dynasty member |
C6391
|
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: Welf dynasty member Context triple: [Henry the Proud, instanceOf, Welf dynasty member]
-
A.
member of the House of Welf
chosen
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.
-
B.
Luxembourg dynasty member
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.
-
C.
Conradine dynasty member
A Conradine dynasty member is an individual belonging to the early medieval German noble family that held significant power in Franconia and briefly provided a king of East Francia in the 10th century.
-
D.
House of Wittelsbach member
A House of Wittelsbach member is an individual belonging by birth or legitimate adoption to the historic German noble and royal dynasty that ruled territories such as Bavaria and the Palatinate and provided various European kings and emperors.
-
E.
Ottonian dynasty member
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.
- 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_69e0b4a71ebc8190b153a36c738730f4 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:28 a.m.