Triple

T20541156
Position Surface form Disambiguated ID Type / Status
Subject Egon Zimmermann E504335 entity
Predicate familyName P18 FINISHED
Object Zimmermann 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: Zimmermann | Statement: [Egon Zimmermann, familyName, Zimmermann]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Zimmermann
Context triple: [Egon Zimmermann, familyName, Zimmermann]
  • A. Zimmermann chosen
    Zimmermann is a German surname commonly associated with the occupation of a carpenter or builder.
  • B. Zimmermann
    Zimmermann was a zoologist who formally described the Indian muntjac, a small deer species native to South and Southeast Asia.
  • C. Zschepplin
    Zschepplin is a small municipality in the German state of Saxony, situated northeast of Leipzig within its wider metropolitan area.
  • D. von Hindenburg
    Von Hindenburg is a German noble family name most famously associated with Paul von Hindenburg, the World War I field marshal and later President of Germany.
  • E. Helmuth
    Helmuth is a masculine given name of German origin, historically borne by several notable military and political figures.
  • 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_69e0b4b476648190bc6019622ae54d3c completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6a29224f081908298d104161c5bb9 completed April 20, 2026, 10:02 p.m.
Created at: April 16, 2026, 11:37 a.m.