Triple
T9079117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maximilian of Baden |
E217568
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Chancellor of the German Empire |
C25575
|
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: Chancellor of the German Empire Context triple: [Maximilian of Baden, instanceOf, Chancellor of the German Empire]
-
A.
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.
-
B.
Vice-Chancellor of Germany
The Vice-Chancellor of Germany is the deputy to the Federal Chancellor, appointed from among the federal ministers to assume the Chancellor’s duties when they are unable to perform them and to support leadership of the federal government.
-
C.
Prussian statesman
A Prussian statesman is a political leader or high-ranking government official from the Kingdom of Prussia who shaped its domestic policies, diplomacy, and military strategy, often influencing broader European affairs.
-
D.
anti-king of Germany
An anti-king of Germany was a rival claimant elected by a faction of princes in opposition to a reigning or officially recognized German king or Holy Roman Emperor, typically during periods of dynastic or political conflict.
-
E.
King of Germany
The King of Germany is a conceptual class representing a sovereign monarch who historically ruled over the German kingdom within the Holy Roman Empire, embodying supreme political and symbolic authority over its territories and subjects.
- 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_69ca83d6c14c8190bc056d927f00a2a2 |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:12 p.m.