Triple
T38081584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kengir uprising |
E950866
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | anti-Soviet resistance event |
C2054
|
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: anti-Soviet resistance event Context triple: [Kengir uprising, instanceOf, anti-Soviet resistance event]
-
A.
anti-Soviet revolt
chosen
An anti-Soviet revolt is an organized uprising or resistance movement aimed at challenging, weakening, or overthrowing Soviet political control, ideology, or military presence.
-
B.
resistance movement
A resistance movement is an organized effort by a group of people to oppose, undermine, or overthrow an existing power, authority, or occupying force, often through political, social, or guerrilla actions.
-
C.
anti-fascist resistance
Anti-fascist resistance is organized or spontaneous opposition—ranging from political activism to armed struggle—aimed at undermining, obstructing, and ultimately defeating fascist regimes, movements, and ideologies.
-
D.
anti-Chinese incident
An anti-Chinese incident is an event or action, ranging from verbal harassment to physical violence or discriminatory policies, specifically targeting individuals, communities, or institutions perceived as Chinese.
-
E.
anti-Mongol revolt
An anti-Mongol revolt is an organized uprising by subject peoples or rival powers aimed at resisting, expelling, or overthrowing Mongol rule and influence.
- 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_69f76f03a3608190a73fd6df87c792a8 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:21 p.m.