Triple
T21590052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Son My |
E532754
|
entity |
| Predicate | civilianCasualtiesApproximate |
P34802
|
FINISHED |
| Object | hundreds |
—
|
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: hundreds | Statement: [Son My, civilianCasualtiesApproximate, hundreds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: civilianCasualtiesApproximate Context triple: [Son My, civilianCasualtiesApproximate, hundreds]
-
A.
casualtiesCiviliansKilled
chosen
Indicates that the relationship records the number of civilian deaths resulting from a specific event or action.
-
B.
casualtiesEstimate
Indicates an estimated number of people killed, injured, or otherwise harmed as a result of an event or incident.
-
C.
nativeCasualties
Indicates that native or indigenous people suffered deaths or injuries as a result of a particular event, action, or conflict.
-
D.
militaryCasualtiesEstimate
Indicates an estimated number of people killed, wounded, or missing as a result of military conflict or operations.
-
E.
primaryCasualtiesFrom
Indicates that an entity is the main source or cause of the casualties experienced by another entity.
- 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_69e0c46251648190876f0427cf2d321b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eefadd0ec88190929c76137bd1603e |
completed | April 27, 2026, 5:57 a.m. |
| PD | Predicate disambiguation | batch_69e632109d048190b4ac3f14fe48d1a0 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:32 p.m.