Triple

T19528919
Position Surface form Disambiguated ID Type / Status
Subject Bernhard Line E488606 entity
Predicate relatedTo P37 FINISHED
Object Knickebein 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: Knickebein | Statement: [Bernhard Line, relatedTo, Knickebein]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Knickebein
Context triple: [Bernhard Line, relatedTo, Knickebein]
  • A. Knickebein chosen
    Knickebein was a German World War II radio navigation system used by the Luftwaffe to guide bombers accurately to their targets, particularly during night raids over Britain.
  • B. Klötze
    Klötze is a small town in the Altmark region of Saxony-Anhalt in central Germany.
  • C. Kröpcke
    Kröpcke is a central square and major public transport hub in Hanover, Germany, known as a key meeting point and commercial area in the city center.
  • D. Schmarbeck
    Schmarbeck is a small watercourse in Lower Saxony, Germany, known as one of the minor streams feeding into the Örtze River within the Lüneburg Heath region.
  • E. Schmarbeck
    Schmarbeck is a small village in Lower Saxony, Germany, that forms part of the collective municipality of Faßberg.
  • 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_69d8e8da8bec819081f400199491ccc3 completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e6363d43148190af25caaa57accf9b completed April 20, 2026, 2:20 p.m.
Created at: April 10, 2026, 1:41 p.m.