Triple

T17622463
Position Surface form Disambiguated ID Type / Status
Subject Kurt Student E429742 entity
Predicate placeOfDeath P21 FINISHED
Object Lemgo, West Germany 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: Lemgo, West Germany | Statement: [Kurt Student, placeOfDeath, Lemgo, West Germany]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lemgo, West Germany
Context triple: [Kurt Student, placeOfDeath, Lemgo, West Germany]
  • A. Lemgo, Germany chosen
    Lemgo, Germany is a historic town in the Lippe district of North Rhine-Westphalia known for its well-preserved medieval and Renaissance architecture.
  • B. Lübbecke, Germany
    Lübbecke is a small town in North Rhine-Westphalia, Germany, known for its location at the foot of the Wiehen Hills and its traditional brewing industry.
  • C. Bergheim, Germany
    Bergheim is a town in western Germany’s North Rhine-Westphalia known for its historic center and proximity to the Cologne metropolitan area.
  • D. Lahnau, Germany
    Lahnau is a small municipality in the state of Hesse in central Germany, located near the city of Wetzlar.
  • E. Lemgo
    Lemgo is a historic town in the Lippe district of North Rhine-Westphalia, Germany, known for its well-preserved medieval architecture and Hanseatic heritage.
  • 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_69d889e37f308190a6aa0a69daff86c7 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e46db98c54819088dadec9f6bcc559 completed April 19, 2026, 5:52 a.m.
Created at: April 10, 2026, 5:52 a.m.