Triple
T586227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Nassau-Weilburg |
E15163
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | German noble house |
C811
|
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: German noble house Context triple: [House of Nassau-Weilburg, instanceOf, German noble house]
-
A.
German noble
A German noble is a member of the historical aristocratic class in German-speaking regions, traditionally holding hereditary titles, land, and social privileges within the feudal and later monarchical systems.
-
B.
noble family
chosen
A noble family is a socially and often legally recognized kinship group that holds hereditary titles, privileges, and status within a hierarchical society, typically associated with landownership, political influence, and longstanding lineage.
-
C.
Dutch nobleman
A Dutch nobleman is a male member of the Netherlands' hereditary or titular nobility, historically holding social status, privileges, and often land or official positions within Dutch society.
-
D.
French nobleman
A French nobleman is an aristocratic male from France who holds hereditary or granted titles, privileges, and social status within the traditional hierarchical nobility system.
-
E.
royal house
A royal house is a dynastic family line that holds or has held a hereditary monarchy, encompassing its members, titles, traditions, and political influence over time.
- 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_69a4935783b8819082b77726ec10cc42 |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:33 p.m.