Triple
T348214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Falklands War |
E6985
|
entity |
| Predicate | casualtiesMilitary |
P6773
|
FINISHED |
| Object | over 900 killed in total |
—
|
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 900 killed in total | Statement: [Falklands War, casualtiesMilitary, over 900 killed in total]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: casualtiesMilitary Context triple: [Falklands War, casualtiesMilitary, over 900 killed in total]
-
A.
casualties
Indicates that an event, action, or situation resulted in people being killed or injured.
-
B.
casualtiesEstimate
Indicates an estimated number of people killed, injured, or otherwise harmed as a result of an event or incident.
-
C.
militaryCasualtiesEstimate
chosen
Indicates an estimated number of people killed, wounded, or missing as a result of military conflict or operations.
-
D.
casualtiesUnitedStates
Indicates that the event or situation resulted in casualties (deaths and/or injuries) among United States personnel or citizens.
-
E.
casualtiesBritishWounded
Indicates the number of British individuals who were wounded as a result of a specific event or action.
- 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_69a2e7951ba08190960e90823b5078f3 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eb1c1c908190b3a01de893207ed1 |
completed | Feb. 28, 2026, 1:18 p.m. |
| PD | Predicate disambiguation | batch_69a2e955d1f88190bd687c46fa7c5469 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.