Triple
T25220967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chlodwig zu Hohenlohe-Schillingsfürst |
E631961
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Prime Minister of Bavaria |
C49885
|
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: Prime Minister of Bavaria Context triple: [Chlodwig zu Hohenlohe-Schillingsfürst, instanceOf, Prime Minister of Bavaria]
-
A.
Minister President of Prussia
The Minister President of Prussia was the head of government of the Kingdom (and later Free State) of Prussia, responsible for leading the Prussian cabinet and directing the state's domestic and, at times, broader German political affairs.
-
B.
Chancellor of the German Empire
The Chancellor of the German Empire was the head of government and chief executive officer of the empire, responsible for directing imperial policy and administration under the authority of the German Emperor from 1871 to 1918.
-
C.
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.
-
D.
chancellor of Austria
The chancellor of Austria is the head of government who leads the federal cabinet, directs national policy, and represents the executive branch in the Republic of Austria.
-
E.
Prime Minister of East Germany
The Prime Minister of East Germany was the head of government of the German Democratic Republic, responsible for leading the Council of Ministers and implementing state and party policies.
- 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_69e75a8e0f688190a7aebe9a4815e25b |
completed | April 21, 2026, 11:07 a.m. |
Created at: April 21, 2026, 1:03 p.m.