Triple
T4162880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Chechen War |
E91571
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russian–Chechen conflict |
C5554
|
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: Russian–Chechen conflict Context triple: [Second Chechen War, instanceOf, Russian–Chechen conflict]
-
A.
guerrilla conflict
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.
-
B.
civil conflict
chosen
Civil conflict is a sustained, organized struggle within a country between the state and one or more internal groups, or among such groups themselves, involving political, social, or economic grievances and often resulting in violence.
-
C.
Soviet–Finnish War
The Soviet–Finnish War, also known as the Winter War (1939–1940), was a conflict in which the Soviet Union invaded Finland to secure territory and strategic depth, facing unexpectedly strong Finnish resistance in harsh winter conditions.
-
D.
border conflict
A border conflict is a dispute between neighboring states or groups over the ownership, control, or demarcation of a shared territorial boundary.
-
E.
campaign of the Russian Civil War
A campaign of the Russian Civil War is a coordinated series of military operations conducted by opposing factions over a specific region and period, aimed at achieving strategic political and territorial objectives within the broader conflict.
- 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_69aed9626ebc8190a39de631788bea3e |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:44 p.m.