Triple

T21715435
Position Surface form Disambiguated ID Type / Status
Subject Georg Atzerodt E536014 entity
Predicate familyName P18 FINISHED
Object Atzerodt NE NERFINISHED

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: Atzerodt | Statement: [Georg Atzerodt, familyName, Atzerodt]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Atzerodt
Context triple: [Georg Atzerodt, familyName, Atzerodt]
  • A. Atzerodt chosen
    Atzerodt is the surname of George Atzerodt, a German-born conspirator involved in the plot to assassinate U.S. President Abraham Lincoln.
  • B. Oppenau
    Oppenau is a small town in the Black Forest region of southwestern Germany, known for its scenic valleys, surrounding mountains, and outdoor recreation opportunities.
  • C. Erasbach
    Erasbach is a small locality in Bavaria, Germany, best known as the birthplace of the composer Christoph Willibald Gluck.
  • D. Baar-Ebenhausen
    Baar-Ebenhausen is a Bavarian municipality in southern Germany known for its residential character and location along the Ilm River.
  • E. Blatzheim
    Blatzheim is a village and district within the town of Kerpen in North Rhine-Westphalia, Germany.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0c46c6dd88190a595375fa6ebd701 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69efb53761b48190954a46e8155a84f0 completed April 27, 2026, 7:12 p.m.
Created at: April 16, 2026, 6:47 p.m.