Triple
T12839162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karl Alexander, Grand Duke of Saxe-Weimar-Eisenach |
E307000
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Grand Duke |
C31952
|
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: Grand Duke Context triple: [Karl Alexander, Grand Duke of Saxe-Weimar-Eisenach, instanceOf, Grand Duke]
-
A.
Grand Duke of Hesse
The Grand Duke of Hesse was the hereditary sovereign ruler of the Grand Duchy of Hesse, a German state that existed from 1806 to 1918 within the Holy Roman Empire’s successor systems and later the German Empire.
-
B.
Grand Duke of Tuscany
The Grand Duke of Tuscany was the sovereign ruler of the Grand Duchy of Tuscany, a central Italian state, holding hereditary monarchical authority over its political, military, and economic affairs.
-
C.
Duke of Courland
The Duke of Courland was the hereditary ruler of the Duchy of Courland and Semigallia, a semi-autonomous Baltic state under Polish-Lithuanian suzerainty from the 16th to 18th centuries.
-
D.
Grand Duke of Russia
A Grand Duke of Russia was a male member of the Russian imperial family, typically a son or grandson of a reigning emperor, who held high dynastic rank and status without necessarily exercising sovereign rule.
-
E.
Duke of Prussia
The Duke of Prussia was a hereditary noble title held by the rulers of the Duchy of Prussia, originally a fief of the Polish Crown that later became the core territory of the Kingdom of Prussia.
- 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_69d7bdf52b94819096d6f0ba4ab50a98 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:35 p.m.