Triple
T20253829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Nek |
E498628
|
entity |
| Predicate | AustralianCasualtiesEstimate |
P118691
|
FINISHED |
| Object | over 230 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 230 killed | Statement: [Battle of the Nek, AustralianCasualtiesEstimate, over 230 killed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AustralianCasualtiesEstimate Context triple: [Battle of the Nek, AustralianCasualtiesEstimate, over 230 killed]
-
A.
AustralianCasualties
chosen
Indicates the number or details of casualties suffered by Australian forces or people in a specific conflict, event, or incident.
-
B.
killedAustralianSoldiers
Indicates that one entity caused the death of Australian soldiers.
-
C.
numberOfVictimsFromAustralia
Indicates the count of victims whose origin or nationality is Australia.
-
D.
militaryCasualtiesEstimate
Indicates an estimated number of people killed, wounded, or missing as a result of military conflict or operations.
-
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.
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_69da6275fa6c8190952924930adee150 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e673aa42348190852ae8313f4494ca |
completed | April 20, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69e55b1b23f88190bdcbe2f81dd226dd |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:41 p.m.