Triple

T950118
Position Surface form Disambiguated ID Type / Status
Subject Hans-Ulrich Rudel E20499 entity
Predicate burialPlace P196 FINISHED
Object Hannover, Germany E21642 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: Hannover, Germany | Statement: [Hans-Ulrich Rudel, burialPlace, Hannover, Germany]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hannover, Germany
Context triple: [Hans-Ulrich Rudel, burialPlace, Hannover, Germany]
  • A. Hamm, Germany
    Hamm is a city in the German state of North Rhine-Westphalia, known as an industrial and transportation hub in the eastern Ruhr area.
  • B. Nassau, Germany
    Nassau, Germany is a historic town on the Lahn River in the state of Rhineland-Palatinate, known as the ancestral seat of the House of Nassau.
  • C. Schröttinghausen, Germany
    Schröttinghausen is a small locality in Germany best known as the birthplace of influential astronomer Walter Baade.
  • D. Krefeld, Germany
    Krefeld, Germany is an industrial city in North Rhine-Westphalia known historically for its textile and silk production.
  • E. Hanover chosen
    Hanover is a historic city in northern Germany that served as the capital of the former Kingdom of Hanover and the ancestral seat of the British House of Hanover.
  • 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_69a493b0f2fc81908cd227480a5356a1 completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4b3c191ac819099ebf3cb32f096d8 completed March 1, 2026, 9:46 p.m.
NED1 Entity disambiguation (via context triple) batch_69acddfeb918819083f948183aaaeb09 completed March 8, 2026, 2:25 a.m.
Created at: March 1, 2026, 7:40 p.m.