Triple

T22459037
Position Surface form Disambiguated ID Type / Status
Subject Edu Weitzel Douwes Dekker E555182 entity
Predicate hasSurname P18 FINISHED
Object Weitzel 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: Weitzel | Statement: [Edu Weitzel Douwes Dekker, hasSurname, Weitzel]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Weitzel
Context triple: [Edu Weitzel Douwes Dekker, hasSurname, Weitzel]
  • A. Weitzel chosen
    Weitzel is a surname of likely German or Dutch origin borne by individuals such as Edu Weitzel Douwes Dekker.
  • B. Welper
    Welper is a district of the town of Hattingen in North Rhine-Westphalia, Germany.
  • C. Weierbach
    Weierbach is a district of the town Idar-Oberstein in Rhineland-Palatinate, Germany, known for its residential character within the wider gemstone and jewelry region.
  • D. Eickeloh
    Eickeloh is a small municipality in Lower Saxony, Germany, situated in the Heidekreis district.
  • E. Eichelbaum
    Eichelbaum is a German-language surname borne by various individuals, including figures in law, arts, and public life.
  • 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_69e11e51fdec8190adfdf9f8a6362221 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15b7e01fc8190825c3dc024484440 completed April 29, 2026, 1:14 a.m.
Created at: April 16, 2026, 8:48 p.m.