Triple
T7260180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Bunker Hill (CV-17) |
E159628
|
entity |
| Predicate | casualtiesInKamikazeAttack |
P1399
|
FINISHED |
| Object | over 600 killed or wounded |
—
|
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: over 600 killed or wounded | Statement: [USS Bunker Hill (CV-17), casualtiesInKamikazeAttack, over 600 killed or wounded]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: casualtiesInKamikazeAttack Context triple: [USS Bunker Hill (CV-17), casualtiesInKamikazeAttack, over 600 killed or wounded]
-
A.
kamikazeHits
Indicates that an attacking entity deliberately crashes into and strikes a target in a suicidal or self-destructive manner.
-
B.
casualtiesJapan
Indicates that an event or action resulted in casualties (deaths and/or injuries) occurring in Japan.
-
C.
casualtiesInflictedOn
Indicates that one party has caused deaths or injuries to another party as a result of a harmful event or action.
-
D.
casualties
chosen
Indicates that an event, action, or situation resulted in people being killed or injured.
-
E.
casualtiesJapanKilled
Indicates that the casualties were individuals from Japan who were killed.
- 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_69c68838f9948190875fd60b2351230c |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb088dac8190b353f6ea3d686025 |
completed | March 27, 2026, 8:39 p.m. |
| PD | Predicate disambiguation | batch_69c6e76876608190ac4652bc7153302e |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:57 p.m.