Triple
T19834699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2005 Nalchik raid |
E476557
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | insurgency-related incident |
C3287
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: insurgency-related incident Context triple: [2005 Nalchik raid, instanceOf, insurgency-related incident]
-
A.
looting incident
A looting incident is an event in which individuals or groups unlawfully seize goods or property, typically during periods of disorder, disaster, or weakened authority.
-
B.
conflict-related killing
Conflict-related killing is the intentional or unintentional taking of life that occurs in the context of, or as a direct consequence of, an armed conflict or organized violence between groups.
-
C.
armed uprising
An armed uprising is a collective, often organized rebellion in which a group uses weapons and force to challenge, resist, or overthrow an existing authority or government.
-
D.
guerrilla conflict
chosen
Guerrilla conflict is a form of irregular warfare in which small, mobile groups use hit-and-run tactics, ambushes, and sabotage to challenge a larger, conventionally organized force, often relying on local support and intimate knowledge of the terrain.
-
E.
police brutality incident
A police brutality incident is an event in which law enforcement officers use excessive, unwarranted, or illegal force or misconduct against civilians, resulting in physical, psychological, or civil rights harm.
- F. None of above.
Provenance (1 batch)
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_69d8e51c7c188190b926f3a2a7b5f881 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:50 p.m.