Triple
T1904295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Hesse-Darmstadt |
E37764
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | German princely house |
C8279
|
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 princely house Context triple: [House of Hesse-Darmstadt, instanceOf, German princely house]
-
A.
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.
-
B.
member of the House of Hesse-Darmstadt
chosen
A member of the House of Hesse-Darmstadt is an individual belonging by birth or marriage to the German princely dynasty that historically ruled the Landgraviate and later Grand Duchy of Hesse-Darmstadt.
-
C.
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.
-
D.
Bavarian prince
A Bavarian prince is a male member of the royal or formerly ruling house of Bavaria, traditionally holding hereditary titles, privileges, and social status within the region’s historical monarchy.
-
E.
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.
- 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_69a8861be7148190a680937ec451a304 |
completed | March 4, 2026, 7:21 p.m. |
Created at: March 4, 2026, 7:35 p.m.