Triple
T1894563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dominican Civil War |
E41948
|
entity |
| Predicate | militaryCasualtiesDominican |
P6773
|
FINISHED |
| Object | hundreds 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: hundreds killed | Statement: [Dominican Civil War, militaryCasualtiesDominican, hundreds killed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryCasualtiesDominican Context triple: [Dominican Civil War, militaryCasualtiesDominican, hundreds killed]
-
A.
militaryCasualtiesEstimate
chosen
Indicates an estimated number of people killed, wounded, or missing as a result of military conflict or operations.
-
B.
UScasualties
Indicates the number or occurrence of casualties suffered by the United States in a given conflict, event, or situation.
-
C.
CubanCasualtiesKilled
Indicates that Cuban individuals were killed as casualties in a specific event or conflict.
-
D.
casualtiesGrenadianAndCuban
Indicates that the relationship involves casualties suffered by both Grenadian and Cuban parties in a given event or context.
-
E.
casualtiesUnitedStates
Indicates that the event or situation resulted in casualties (deaths and/or injuries) among United States personnel or citizens.
- 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_69a8864b6de0819098d089f6a1b910a7 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb16c09e48190a345c95eab59fd87 |
completed | March 7, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69abafe7e7e88190b58c0df59187c0c2 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:34 p.m.