Triple
T18292836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian pogroms of 1881–1882 |
E438158
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | violent riot wave |
C29308
|
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: violent riot wave Context triple: [Russian pogroms of 1881–1882, instanceOf, violent riot wave]
-
A.
violent confrontation
A violent confrontation is an intense, hostile encounter between individuals or groups in which physical force or threats are used to assert power, resolve conflict, or inflict harm.
-
B.
social upheaval
Social upheaval is a period of intense, widespread disruption and transformation in a society’s norms, institutions, and power structures, often driven by economic, political, or cultural conflicts.
-
C.
anti-Jewish riot
chosen
An anti-Jewish riot is a violent, collective attack by a non-Jewish population against Jewish individuals, communities, or property, typically fueled by antisemitic prejudice, political tensions, or social unrest.
-
D.
religious revolt
A religious revolt is a collective uprising driven primarily by spiritual or doctrinal grievances, in which believers challenge established religious or political authorities they see as violating sacred principles.
-
E.
hostile mob
A hostile mob is an autonomous game entity that actively seeks out and attacks players or other targets under specific conditions, often posing a persistent threat within the game world.
- 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_69d8b915e3e881909125d760c15d0c29 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:35 a.m.