Triple
T17402126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles Frederick, Grand Duke of Baden |
E423116
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Grand Duke of Baden |
C38531
|
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 of Baden Context triple: [Charles Frederick, Grand Duke of Baden, instanceOf, Grand Duke of Baden]
-
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.
Duke of Württemberg
The Duke of Württemberg was the hereditary sovereign ruler of the Duchy of Württemberg, a historical German territory within the Holy Roman Empire and later the German Confederation.
-
C.
Grand Duke of Saxe-Weimar-Eisenach
The Grand Duke of Saxe-Weimar-Eisenach was the hereditary sovereign ruler of the Grand Duchy of Saxe-Weimar-Eisenach, a German state that existed within the Holy Roman Empire, the Confederation of the Rhine, the German Confederation, and later the German Empire until 1918.
-
D.
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.
-
E.
Duke of Saxe-Weimar
The Duke of Saxe-Weimar was a hereditary noble title held by the ruler of the historical German duchy of Saxe-Weimar within the Holy Roman Empire and later German states.
- 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_69d889d710288190bf0f4762801fefae |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:45 a.m.