Triple
T2687856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Edson's Ridge |
E57526
|
entity |
| Predicate | casualtiesJapanKilled |
P41519
|
FINISHED |
| Object | over 600 |
—
|
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 | Statement: [Battle of Edson's Ridge, casualtiesJapanKilled, over 600]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: casualtiesJapanKilled Context triple: [Battle of Edson's Ridge, casualtiesJapanKilled, over 600]
-
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.
notableVictims
Indicates that the object is a person or group who is especially well-known or significant as a victim of the subject.
-
D.
casualtiesCiviliansKilled
Indicates that the relationship records the number of civilian deaths resulting from a specific event or action.
-
E.
militaryCasualtiesEstimate
Indicates an estimated number of people killed, wounded, or missing as a result of military conflict or operations.
- 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_69ab4a5028388190a36f3baf1588309e |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd9f1ba3081909a349a2f30f8f9c9 |
completed | March 7, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69abd81c9b4c81908e5e0da6ac5f828b |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd891bcd481909af5340a64ff69f9 |
completed | March 7, 2026, 7:49 a.m. |
Created at: March 6, 2026, 9:54 p.m.