Triple
T10539664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Hill 70 |
E248661
|
entity |
| Predicate | CanadianCasualtiesApprox |
P94437
|
FINISHED |
| Object | about 9000 |
—
|
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: about 9000 | Statement: [Battle of Hill 70, CanadianCasualtiesApprox, about 9000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: CanadianCasualtiesApprox Context triple: [Battle of Hill 70, CanadianCasualtiesApprox, about 9000]
-
A.
UScasualties
Indicates the number or occurrence of casualties suffered by the United States in a given conflict, event, or situation.
-
B.
nativeCasualties
Indicates that native or indigenous people suffered deaths or injuries as a result of a particular event, action, or conflict.
-
C.
militaryCasualtiesEstimate
Indicates an estimated number of people killed, wounded, or missing as a result of military conflict or operations.
-
D.
NATOcasualtiesMilitaryKilled
Indicates that members of NATO military forces were killed as casualties.
-
E.
casualtiesCountry
Indicates that the specified country is the one in which the recorded casualties (deaths or injuries) occurred or to which those casualties belong.
- 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_69d381c5c7448190bec34bee7ec72bac |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d50a5730d88190b266a940faf53f65 |
completed | April 7, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69d4fb9729288190a0149f127acd7ae3 |
completed | April 7, 2026, 12:41 p.m. |
| PDg | Predicate description generation | batch_69d4fe06d4a48190b1a45dd1d4e16df0 |
completed | April 7, 2026, 12:52 p.m. |
Created at: April 6, 2026, 12:32 p.m.