Triple

T11806883
Position Surface form Disambiguated ID Type / Status
Subject Irmfried Eberl E280768 entity
Predicate givenName P17 FINISHED
Object Irmfried E279615 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: Irmfried | Statement: [Irmfried Eberl, givenName, Irmfried]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Irmfried
Context triple: [Irmfried Eberl, givenName, Irmfried]
  • A. Irmfried chosen
    Irmfried is a masculine German given name most notably borne by Irmfried Eberl, an Austrian physician and Nazi SS officer who served as a commandant of extermination camps during World War II.
  • B. Othmar
    Othmar is a masculine given name of Germanic origin, notably borne by the Swiss-American civil engineer Othmar Ammann.
  • C. Aribert
    Aribert is a Germanic given name, historically borne by medieval nobles and clergy, derived from elements meaning "army" and "bright."
  • D. Gebhard
    Gebhard is a German given name most famously borne by Gebhard Leberecht von Blücher, the Prussian field marshal who helped defeat Napoleon at Waterloo.
  • E. Reimund
    Reimund is a masculine given name, primarily used in German-speaking regions, that is a variant of the name Raymond.
  • 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_69d6ab26aae88190b2489efcb2a24234 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d8a5c8324481909a54852a9bb714e0 completed April 10, 2026, 7:24 a.m.
NED1 Entity disambiguation (via context triple) batch_69f131726ab08190ae777bee3ac6df43 completed April 28, 2026, 10:15 p.m.
Created at: April 8, 2026, 9:42 p.m.