Triple
T12588502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Möhne River |
E300533
|
entity |
| Predicate | hasStructure |
P35
|
FINISHED |
| Object | Möhne Dam spillway |
E44569
|
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: Möhne Dam spillway | Statement: [Möhne River, hasStructure, Möhne Dam spillway]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Möhne Dam spillway Context triple: [Möhne River, hasStructure, Möhne Dam spillway]
-
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.
Eider-Sperrwerk
The Eider-Sperrwerk is a major storm surge barrier and lock complex in northern Germany that protects the low-lying Eider estuary and surrounding coastal areas from North Sea flooding.
-
D.
Diemel Dam
Diemel Dam is a German reservoir dam that was one of the targets attacked during the World War II Dambusters Raid.
-
E.
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.
- 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_69d7bde87b648190bcd0266e9efde098 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d954bd5e8c8190a2f233b91682341f |
completed | April 10, 2026, 7:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f671926a7c8190a41725cfde7836b1 |
completed | May 2, 2026, 9:50 p.m. |
Created at: April 9, 2026, 5:06 p.m.