Triple
T21919033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Quebrada del Yuro |
E541252
|
entity |
| Predicate | ambush |
P77747
|
FINISHED |
| Object | Bolivian forces ambushed Che Guevara’s guerrilla group |
—
|
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: Bolivian forces ambushed Che Guevara’s guerrilla group | Statement: [Battle of Quebrada del Yuro, ambush, Bolivian forces ambushed Che Guevara’s guerrilla group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ambush Context triple: [Battle of Quebrada del Yuro, ambush, Bolivian forces ambushed Che Guevara’s guerrilla group]
-
A.
surpriseAttack
chosen
Indicates an aggressive action initiated unexpectedly against a target that is unprepared or unaware.
-
B.
plannedAttack
Indicates that an entity has intentionally prepared and organized an attack against a target.
-
C.
attackType
Indicates the specific method, style, or category of attack used in an aggressive or hostile action between entities.
-
D.
attackedFrom
Indicates that one entity initiated an attack against another entity originating from a specific source location or position.
-
E.
bombBay
Indicates that an entity serves as or is located in the bomb bay compartment of an aircraft, where bombs are stored and released.
- 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_69e0c47c4b9c8190a5586a75f5f36453 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f12339d88881909e726c9b081bd177 |
completed | April 28, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69e6be9ebf4c8190892df1a8e1313f88 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:44 p.m.