Triple

T20961078
Position Surface form Disambiguated ID Type / Status
Subject Eder E516244 entity
Predicate hasDam P8736 FINISHED
Object Edersee 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: Edersee Dam | Statement: [Eder, hasDam, Edersee Dam]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Edersee Dam
Context triple: [Eder, hasDam, Edersee Dam]
  • A. Edersee Dam chosen
    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.
  • B. Schluchsee Dam
    Schluchsee Dam is a hydroelectric and water regulation dam in Germany’s Black Forest that creates the Schluchsee reservoir, a major regional lake and recreation area.
  • C. Schwelm Dam
    Schwelm Dam is a German reservoir dam that was one of the targets attacked during the World War II Dambusters Raid.
  • D. Hohenwarte Dam
    Hohenwarte Dam is a large hydroelectric and flood-control dam on the Saale River in Thuringia, Germany, forming one of the country’s significant reservoir lakes.
  • E. Sorpe Dam
    The Sorpe Dam is a German earth-fill dam in the Ruhr region that was a key target of the RAF’s World War II “Dambusters” raid, Operation Chastise.
  • 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_69e0b4fde6c48190af1398e7e734629e completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6fb6f134081908b1ed48ce708f3d5 completed April 21, 2026, 4:22 a.m.
Created at: April 16, 2026, 1:31 p.m.