Triple
T19823098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adolf of Holstein-Gottorp |
E476247
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Duke of Holstein-Gottorp |
C42663
|
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: Duke of Holstein-Gottorp Context triple: [Adolf of Holstein-Gottorp, instanceOf, Duke of Holstein-Gottorp]
-
A.
Duke of Brunswick-Lüneburg
The Duke of Brunswick-Lüneburg was a title held by various princes of the Holy Roman Empire who ruled over the duchy of Brunswick-Lüneburg in what is now northern Germany, often dividing and reuniting its territories among different dynastic lines.
-
B.
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.
-
C.
Grand Duke of Mecklenburg-Schwerin
The Grand Duke of Mecklenburg-Schwerin was the hereditary sovereign ruler of the Grand Duchy of Mecklenburg-Schwerin, a German state within the Holy Roman Empire and later the German Confederation and German Empire, until the monarchy’s abolition in 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_69d8e51c7c188190b926f3a2a7b5f881 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:50 p.m.