Triple
T35415042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anhalt-Dessau line |
E1023617
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | branch of the House of Ascania |
C63802
|
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: branch of the House of Ascania Context triple: [Anhalt-Dessau line, instanceOf, branch of the House of Ascania]
-
A.
member of the House of Ascania
A member of the House of Ascania is an individual belonging to the medieval German noble dynasty that ruled various principalities and territories, including Anhalt and Brandenburg, across several centuries.
-
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.
member of the House of Wettin
A member of the House of Wettin is an individual belonging to the historic German noble and royal dynasty that ruled various central European territories, including Saxony and Poland, over many centuries.
-
D.
German princely dynasty
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.
-
E.
House of Hesse and by Rhine
The House of Hesse and by Rhine was a German grand ducal dynasty that ruled the Grand Duchy of Hesse (centered on Darmstadt) from the early 19th century until the end of the German monarchies in 1918.
- F. None of above. chosen
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_69f76df54bac8190bd0d3b0eb35cda5f |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:03 p.m.