Triple

T13415716
Position Surface form Disambiguated ID Type / Status
Subject Michael Streicher E313206 entity
Predicate hasSurname P18 FINISHED
Object Streicher E78876 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: Streicher | Statement: [Michael Streicher, hasSurname, Streicher]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Streicher
Context triple: [Michael Streicher, hasSurname, Streicher]
  • A. Streicher chosen
    Streicher is a German surname most infamously associated with Julius Streicher, a prominent Nazi propagandist and publisher of the antisemitic newspaper Der Stürmer.
  • B. Stradner
    Stradner is a surname most notably associated with Austrian-American actress Rosa Stradner.
  • C. Estreicher
    Estreicher is a Polish family name most notably associated with Karol Estreicher Sr., a prominent 19th-century bibliographer and historian of Polish literature.
  • D. Kreuzer
    The Kreuzer was a small silver coin and monetary unit used for centuries in various German-speaking states within the Holy Roman Empire and beyond.
  • E. Stöcker
    Stöcker is a German surname that is a variant of the name Stoker.
  • 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_69d806ad0c44819088833ae1ec9e9690 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69dbaeb6e904819098cc9153fd2feaf5 completed April 12, 2026, 2:39 p.m.
NED1 Entity disambiguation (via context triple) batch_69f7308095548190afb659b84f2775f2 completed May 3, 2026, 11:24 a.m.
Created at: April 9, 2026, 9:39 p.m.