Triple

T21338994
Position Surface form Disambiguated ID Type / Status
Subject Friedrich Jeckeln E526129 entity
Predicate familyName P18 FINISHED
Object Jeckeln 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: Jeckeln | Statement: [Friedrich Jeckeln, familyName, Jeckeln]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jeckeln
Context triple: [Friedrich Jeckeln, familyName, Jeckeln]
  • A. Jeckeln chosen
    Jeckeln is a German surname most infamously associated with Friedrich Jeckeln, a high-ranking Nazi SS officer and war criminal responsible for mass atrocities during World War II.
  • B. Jaeckel
    Jaeckel is a German-origin surname most notably associated with American character actor Richard Jaeckel.
  • C. Schröck
    Schröck is a German surname and place name that appears as a variant spelling of Schrock.
  • D. Jungmann
    Jungmann is the nickname of the Bücker Bü 131, a German 1930s biplane widely used as a primary trainer aircraft before and during World War II.
  • E. Jekki
    Jekki is an alternative name for the Jek language, a Northeast Caucasian language spoken by the Jek people in parts of Azerbaijan.
  • 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_69e0b51c33048190ab27cede74ef798c completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e898dbea44819096dd25701ee462f9 completed April 22, 2026, 9:46 a.m.
Created at: April 16, 2026, 4:44 p.m.