Triple
T2826356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Surigao Strait |
E54931
|
entity |
| Predicate | U.S.destroyerAttack |
P33335
|
FINISHED |
| Object | torpedo attacks by PT boats and destroyers |
—
|
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: torpedo attacks by PT boats and destroyers | Statement: [Battle of Surigao Strait, U.S.destroyerAttack, torpedo attacks by PT boats and destroyers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: U.S.destroyerAttack Context triple: [Battle of Surigao Strait, U.S.destroyerAttack, torpedo attacks by PT boats and destroyers]
-
A.
dateHitByTorpedo
Indicates the specific date on which an entity was struck by a torpedo.
-
B.
locationOfTorpedoAttack
chosen
Indicates the place where a torpedo attack occurred or was carried out.
-
C.
opposingForcesAtSinking
Indicates that two or more forces are acting in opposition to each other at the time or location of a sinking event.
-
D.
battleshipsDamaged
Indicates that one or more battleships have sustained damage, typically as a result of combat or hostile action.
-
E.
sunkBy
Indicates that one entity (typically a vessel or structure) was caused to sink or be destroyed in water by another 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_69ab49e100c0819082a40cb797383243 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abde94ba848190b2c990936e07e6bb |
completed | March 7, 2026, 8:15 a.m. |
| PD | Predicate disambiguation | batch_69abdd0acab881909e8c25cbef83678c |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:59 p.m.