Triple

T20259045
Position Surface form Disambiguated ID Type / Status
Subject No. 617 Squadron RAF E498780 entity
Predicate targeted P860 FINISHED
Object Möhne Dam 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: Möhne Dam | Statement: [No. 617 Squadron RAF, targeted, Möhne Dam]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Möhne Dam
Context triple: [No. 617 Squadron RAF, targeted, Möhne Dam]
  • A. Möhne Dam chosen
    Möhne Dam is a major German gravity dam in North Rhine-Westphalia, historically known for being breached by the RAF’s “Dambusters” raid during World War II.
  • B. Schwelm Dam
    Schwelm Dam is a German reservoir dam that was one of the targets attacked during the World War II Dambusters Raid.
  • C. Edersee Dam
    The Edersee Dam is a large gravity dam in Germany’s Eder Valley, historically known for being one of the key German dams attacked by the RAF’s “Dambusters” using bouncing bombs during World War II.
  • D. Ennepe Dam
    Ennepe Dam is a German reservoir dam in North Rhine-Westphalia that was one of the targets of the World War II Dambusters Raid.
  • E. Diemel Dam
    Diemel Dam is a German reservoir dam that was one of the targets attacked during the World War II Dambusters Raid.
  • 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_69da6275fa6c8190952924930adee150 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e674c84e848190a6e8956698b84026 completed April 20, 2026, 6:47 p.m.
Created at: April 11, 2026, 11:41 p.m.