Triple
T14695801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry of Nassau-Dillenburg |
E345153
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | House of Nassau member |
C17268
|
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: House of Nassau member Context triple: [Henry of Nassau-Dillenburg, instanceOf, House of Nassau member]
-
A.
member of the House of Nassau
chosen
A member of the House of Nassau is an individual belonging by birth or lawful adoption to the historic European noble dynasty of Nassau, associated with various principalities and modern royal families, notably in the Netherlands and Luxembourg.
-
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.
House of Habsburg member
A House of Habsburg member is an individual belonging by birth or marriage to the historic European royal dynasty that ruled vast territories including Austria, Spain, and the Holy Roman Empire.
-
D.
House of Hohenzollern member
A House of Hohenzollern member is an individual belonging by birth or legitimate adoption to the historic German noble and royal dynasty that ruled territories including Brandenburg-Prussia and the German Empire.
-
E.
House of Braganza member
A House of Braganza member is an individual belonging by birth or legitimate dynastic connection to the Portuguese royal and noble family of Braganza, historically associated with the thrones of Portugal and Brazil.
- 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_69d822e4a8c08190a155df736bb7bc13 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:28 a.m.