Triple
T37339382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Bunker Hill |
E926987
|
entity |
| Predicate | casualtiesIn1945KamikazeAttack |
P187745
|
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, casualtiesIn1945KamikazeAttack, over 600 killed or wounded]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: casualtiesIn1945KamikazeAttack Context triple: [USS Bunker Hill, casualtiesIn1945KamikazeAttack, 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.
locationOfKamikazeAttack
Indicates the place where a kamikaze attack occurred or was carried out.
-
C.
casualtiesWhenSunk
Indicates the number of people killed or injured as a direct result of an entity (typically a vessel) being sunk.
-
D.
casualtiesJapan
Indicates that an event or action resulted in casualties (deaths and/or injuries) occurring in Japan.
-
E.
dateOfMajorKamikazeAttack
Indicates the specific calendar date on which a major kamikaze attack occurred.
- 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_69f76eb4e8a881908bd40da28f36fc7e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb8c38a9688190be524246f5682107 |
completed | May 6, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9c6e0481908565bd849e869b24 |
completed | May 6, 2026, 3:13 p.m. |
| PDg | Predicate description generation | batch_69fb8c37931c81909da038c18ed9add2 |
completed | May 6, 2026, 6:45 p.m. |
Created at: May 3, 2026, 4:16 p.m.