Triple
T1201885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christian Henry of Brunswick-Lüneburg |
E25799
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the House of Welf |
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: member of the House of Welf Context triple: [Christian Henry of Brunswick-Lüneburg, instanceOf, member of the House of Welf]
-
A.
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.
-
B.
member of the House of Holstein-Gottorp
A member of the House of Holstein-Gottorp is an individual belonging to a cadet branch of the Oldenburg dynasty that ruled or influenced territories in northern Germany, Scandinavia, and Russia through dynastic unions and successions.
-
C.
member of the House of Savoy
A member of the House of Savoy is an individual belonging by birth or marriage to the historic European royal dynasty that ruled territories including Savoy, Sardinia, and eventually unified Italy.
-
D.
House of Wessex member
A House of Wessex member is an individual belonging to the early medieval royal dynasty that ruled the Anglo-Saxon kingdom of Wessex and later much of England.
-
E.
member of the House of Bourbon
A member of the House of Bourbon is an individual belonging by birth or legitimate descent to the historic European royal dynasty that ruled or influenced several kingdoms, including France, Spain, and Naples.
- F. None of above. chosen
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_69a4942b30f08190a91c60573e16b5ef |
completed | March 1, 2026, 7:31 p.m. |
Created at: March 1, 2026, 7:46 p.m.