Triple
T2586821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle for Henderson Field |
E58023
|
entity |
| Predicate | casualtiesJapanese |
P35438
|
FINISHED |
| Object | over 2,000 killed |
—
|
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 2,000 killed | Statement: [Battle for Henderson Field, casualtiesJapanese, over 2,000 killed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: casualtiesJapanese Context triple: [Battle for Henderson Field, casualtiesJapanese, over 2,000 killed]
-
A.
casualtiesJapan
Indicates that an event or action resulted in casualties (deaths and/or injuries) occurring in Japan.
-
B.
JapaneseCasualtiesWounded
Indicates that the relationship specifies the number of Japanese individuals who were wounded (but not killed) as casualties in a particular event or context.
-
C.
casualties
Indicates that an event, action, or situation resulted in people being killed or injured.
-
D.
casualtiesDescription
Indicates a textual description of the human losses (such as deaths, injuries, or missing persons) resulting from an event or incident.
-
E.
casualtiesAssociatedWithEvent
chosen
Indicates that certain casualties (deaths or injuries) are linked to, or resulted from, a specific event.
- 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_69ab4ac019c8819094add11c46706e32 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd3f6f6ac8190abff7b8b6ff3c023 |
completed | March 7, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69abd0d19308819089ee942513d567a4 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:49 p.m.