Triple
T9123296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gerhard Schröder (CDU politician, 1910–1989) |
E218909
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | government minister of Germany |
C6682
|
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: government minister of Germany Context triple: [Gerhard Schröder (CDU politician, 1910–1989), instanceOf, government minister of Germany]
-
A.
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.
-
B.
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.
-
C.
East German politician
An East German politician is a public official or political figure who was active in the governance, administration, or party structures of the former German Democratic Republic (GDR) before its reunification with West Germany in 1990.
-
D.
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.
-
E.
cabinet minister
chosen
A cabinet minister is a high-ranking government official who heads a specific department or ministry and participates in collective decision-making within the executive branch.
- 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_69ca83dddd548190983b96c664f7f367 |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:17 p.m.