Triple
T21919000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ejército de Liberación Nacional de Bolivia |
E541251
|
entity |
| Predicate | typeOfConflictActor |
P6060
|
FINISHED |
| Object | non-state armed 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: non-state armed group | Statement: [Ejército de Liberación Nacional de Bolivia, typeOfConflictActor, non-state armed group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfConflictActor Context triple: [Ejército de Liberación Nacional de Bolivia, typeOfConflictActor, non-state armed group]
-
A.
conflictRole
chosen
Indicates that an entity plays a specific role or position within a conflict or dispute between parties.
-
B.
conflictType
Indicates the specific kind or category of conflict that characterizes the relationship or interaction between entities.
-
C.
partnerInConflictWith
Indicates that two entities are engaged as opposing partners or sides within the same conflict or dispute.
-
D.
conflictSpecific
Indicates a specific, concrete instance or type of conflict that exists between the related entities.
-
E.
settingOfConflict
Indicates the location or context in which a conflict between entities takes place.
- 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.