Triple

T3622921
Position Surface form Disambiguated ID Type / Status
Subject Helmut E76767 entity
Predicate hasNotableBearers P458 FINISHED
Object Helmut Kohl E10831 NE FINISHED

How this triple was built (2 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Helmut Kohl | Statement: [Helmut, hasNotableBearers, Helmut Kohl]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Helmut Kohl
Context triple: [Helmut, hasNotableBearers, Helmut Kohl]
  • A. Helmut Kohl chosen
    Helmut Kohl was a long-serving German chancellor best known for overseeing German reunification and shaping the early course of the European Union.
  • B. Gerhard Kohl
    Gerhard Kohl is an individual notable enough to be recognized as a namesake or prominent bearer of the surname Kohl.
  • C. Siegfried Kohl
    Siegfried Kohl is an individual notable for bearing the German surname "Kohl," which is associated with several prominent figures.
  • D. Hans-Dietrich Genscher
    Hans-Dietrich Genscher was a prominent German liberal politician who served for many years as Foreign Minister and Vice Chancellor, playing a key role in German reunification and European diplomacy.
  • E. Hans Kohl
    Hans Kohl is a relatively obscure individual primarily known only as a namesake associated with the surname Kohl.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 batches)

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_69ad85dae2fc81908d1ceadbc6af0089 completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adc2bc79008190abe6900adcbda8de completed March 8, 2026, 6:41 p.m.
NED1 Entity disambiguation (via context triple) batch_69b44f0e8d1c8190ae1728d07d5a9e87 completed March 13, 2026, 5:53 p.m.
Created at: March 8, 2026, 3:23 p.m.