Triple
T2180113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Diamond Hill |
E49020
|
entity |
| Predicate | BoerCasualties |
P37678
|
FINISHED |
| Object | over 30 killed and 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 30 killed and wounded | Statement: [Battle of Diamond Hill, BoerCasualties, over 30 killed and wounded]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BoerCasualties Context triple: [Battle of Diamond Hill, BoerCasualties, over 30 killed and wounded]
-
A.
dutchCasualties
Indicates that the relationship specifies the number or occurrence of casualties suffered by Dutch entities in a given event or context.
-
B.
militaryCasualtiesEstimate
Indicates an estimated number of people killed, wounded, or missing as a result of military conflict or operations.
-
C.
coalitionCasualties
Indicates that members of a coalition have suffered deaths or injuries as a result of a particular conflict, event, or action.
-
D.
PolishCasualties
Indicates the number or extent of casualties suffered by Polish forces or population in a given conflict or event.
-
E.
UScasualties
Indicates the number or occurrence of casualties suffered by the United States in a given conflict, event, or situation.
- 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_69a88aa72d348190a9544bb5b8a4e71d |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc4358fc88190a6f556c2de9fef8c |
completed | March 7, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69abbda0ec948190be88c1243d81a423 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abc434978c8190b9c4dd8411b87f23 |
completed | March 7, 2026, 6:22 a.m. |
Created at: March 4, 2026, 7:45 p.m.