Triple
T3840762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ernestine branch of the House of Wettin |
E93443
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | German princely line |
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 princely line Context triple: [Ernestine branch of the House of Wettin, instanceOf, German princely line]
-
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.
House of Wettin
The House of Wettin is a historic European noble dynasty originating in Saxony that produced numerous princes, electors, kings, and other rulers across central and northern Europe from the Middle Ages onward.
-
C.
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.
-
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.
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.
- 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_69aed96ce578819084ab16e3439976c9 |
completed | March 9, 2026, 2:30 p.m. |
Created at: March 9, 2026, 3:18 p.m.