Triple
T5359822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pointe du Hoc |
E102990
|
entity |
| Predicate | bombardedBy |
P63009
|
FINISHED |
| Object | Allied naval gunfire |
—
|
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: Allied naval gunfire | Statement: [Pointe du Hoc, bombardedBy, Allied naval gunfire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bombardedBy Context triple: [Pointe du Hoc, bombardedBy, Allied naval gunfire]
-
A.
bombed
Indicates that one entity attacked another using explosive weapons, causing or intending to cause destruction or damage.
-
B.
wasBombardedDuring
Indicates that an entity was subjected to a bombardment (e.g., shelling, bombing, or heavy attack) during a specified event or time period.
-
C.
bombBay
Indicates that an entity serves as or is located in the bomb bay compartment of an aircraft, where bombs are stored and released.
-
D.
resultOfBombing
Indicates that something exists or occurs as a consequence or outcome of a bombing event.
-
E.
wasBombedOn
Indicates that a location or target experienced a bombing event at a specific time or date.
- F. None of above. chosen
Provenance (4 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_69bd43daa3e4819090b59d127db70e57 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd86330e4c8190b5452226886287b3 |
completed | March 20, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69bd845f41f88190b75b8b64b9e41862 |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd85731dcc8190b4c1fe155967ab81 |
completed | March 20, 2026, 5:35 p.m. |
Created at: March 20, 2026, 2:02 p.m.