Triple
T17985757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ludwig Otto Friedrich Wilhelm |
E430227
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | monarch of Bavaria |
C7864
|
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: monarch of Bavaria Context triple: [Ludwig Otto Friedrich Wilhelm, instanceOf, monarch of Bavaria]
-
A.
Bavarian monarch
chosen
A Bavarian monarch is the sovereign ruler of Bavaria, historically holding supreme political authority and symbolic leadership over the Bavarian state and its people.
-
B.
Duke of Bavaria
The Duke of Bavaria is a noble title historically held by the ruler of the Bavarian duchy, signifying high-ranking authority and governance within the region of Bavaria in the Holy Roman Empire and later German territories.
-
C.
German Emperor
A German Emperor is the sovereign ruler who held the imperial title over the German Empire, symbolizing supreme political and military authority within the unified German state from 1871 to 1918.
-
D.
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.
-
E.
Grand Duke of Baden
The Grand Duke of Baden was the hereditary sovereign ruler of the Grand Duchy of Baden, a German state that existed from 1806 to 1918 within the Holy Roman Empire’s successor systems and later the German Empire.
- 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_69d8b90364248190a37381adea932f42 |
completed | April 10, 2026, 8:46 a.m. |
Created at: April 10, 2026, 10:23 a.m.