Triple
T2033513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Möhne Dam |
E44569
|
entity |
| Predicate | attackedWith |
P22414
|
FINISHED |
| Object | bouncing bombs |
—
|
LITERAL 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: bouncing bombs | Statement: [Möhne Dam, attackedWith, bouncing bombs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attackedWith Context triple: [Möhne Dam, attackedWith, bouncing bombs]
-
A.
attackedIn
Indicates that one entity carried out an attack in the location, context, or time frame specified by another entity or value.
-
B.
attackType
Indicates the specific method, style, or category of attack used in an aggressive or hostile action between entities.
-
C.
assaultedBy
Indicates that an entity has been attacked or subjected to violent physical aggression by another entity.
-
D.
notableAttack
Indicates that an entity carried out, was involved in, or is strongly associated with a particularly significant or well-known attack.
-
E.
weaponUsedAgainst
chosen
Indicates that a particular weapon or instrument is employed in an act of aggression, attack, or harm directed toward a specific target or entity.
- F. None of above.
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_69a889144f2481909932f0746a93023d |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb93255248190bd47a54a7b3c7447 |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb7a8125881909c0cb58b777c1faa |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:39 p.m.