Triple
T31447200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Mal Tiempo |
E802222
|
entity |
| Predicate | casualtiesCuban |
P1399
|
FINISHED |
| Object | low |
—
|
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: low | Statement: [Battle of Mal Tiempo, casualtiesCuban, low]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: casualtiesCuban Context triple: [Battle of Mal Tiempo, casualtiesCuban, low]
-
A.
CubanCasualtiesKilled
Indicates that Cuban individuals were killed as casualties in a specific event or conflict.
-
B.
casualtiesGrenadianAndCuban
Indicates that the relationship involves casualties suffered by both Grenadian and Cuban parties in a given event or context.
-
C.
CubanCasualtiesWounded
Indicates that Cuban individuals were injured or wounded as a result of a particular event or conflict.
-
D.
casualties
chosen
Indicates that an event, action, or situation resulted in people being killed or injured.
-
E.
nativeCasualties
Indicates that native or indigenous people suffered deaths or injuries as a result of a particular event, action, or conflict.
- 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_69f348c5a6bc819092a557e95438976f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6bbbef7a88190b0affdec1d41c1e0 |
completed | May 3, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: April 30, 2026, 9:10 p.m.