Triple

T25927279
Position Surface form Disambiguated ID Type / Status
Subject Heinz Riesenhuber E653339 entity
Predicate instanceOf P0 FINISHED
Object federal minister of Germany C1775 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: federal minister of Germany
Context triple: [Heinz Riesenhuber, instanceOf, federal 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. Prime Minister of Bavaria
    The Prime Minister of Bavaria is the head of government of the German federal state of Bavaria, responsible for leading the state cabinet, setting policy priorities, and representing Bavaria at the federal and international levels.
  • D. German federal government
    The German federal government is the central executive authority of the Federal Republic of Germany, consisting primarily of the Federal Chancellor and federal ministers, responsible for implementing laws and directing national policy.
  • E. federal ministerial office chosen
    A federal ministerial office is a governmental entity headed by a federal minister, responsible for developing, implementing, and overseeing policies and administrative functions within a specific national portfolio or sector.
  • 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_69e7ab3eb9b881909c1390690551f868 completed April 21, 2026, 4:52 p.m.
Created at: April 22, 2026, 8:36 a.m.