Triple
T8722090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Waldeck |
E207035
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | German noble dynasty |
C12506
|
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 dynasty Context triple: [House of Waldeck, instanceOf, German noble dynasty]
-
A.
German princely dynasty
chosen
A German princely dynasty is a hereditary ruling family from the German-speaking regions of Europe that historically held princely titles, governed territories, and played significant roles in regional and imperial politics.
-
B.
Prussian aristocratic family
A Prussian aristocratic family is a noble lineage rooted in the historical Kingdom of Prussia, characterized by hereditary titles, landed estates, military and bureaucratic service, and adherence to traditional social hierarchies and customs.
-
C.
Swedish noble family
A Swedish noble family is a lineage of individuals in Sweden historically granted hereditary noble status, often holding titles, estates, and social privileges recognized by the Swedish nobility system.
-
D.
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.
-
E.
member of German nobility
A member of German nobility is an individual belonging to a historically privileged social class in German-speaking regions, typically holding hereditary titles, land, and social status recognized under traditional aristocratic 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_69ca835811d8819081ea00fd2a2c9a1c |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:36 p.m.