Triple
T30373141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tarakan operation |
E772604
|
entity |
| Predicate | casualtiesJapaneseKilled |
P41519
|
FINISHED |
| Object | over 1,500 |
—
|
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 1,500 | Statement: [Tarakan operation, casualtiesJapaneseKilled, over 1,500]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: casualtiesJapaneseKilled Context triple: [Tarakan operation, casualtiesJapaneseKilled, over 1,500]
-
A.
casualtiesJapanKilled
chosen
Indicates that the casualties were individuals from Japan who were killed.
-
B.
casualtiesJapan
Indicates that an event or action resulted in casualties (deaths and/or injuries) occurring in Japan.
-
C.
JapaneseCasualtiesSurvivors
Indicates the number or status of Japanese individuals who were casualties but survived an event or conflict.
-
D.
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.
-
E.
officialDeathTollReportedByJapanese
Indicates that the officially recorded number of deaths was reported by Japanese authorities or sources.
- 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_69f2248d71408190aec0d5c2001b1cff |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 7:59 p.m.