Triple
T28691236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khmelnytsky Uprising massacres |
E729290
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | anti-Jewish violence |
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: anti-Jewish violence Context triple: [Khmelnytsky Uprising massacres, instanceOf, anti-Jewish violence]
-
A.
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.
-
B.
anti-Armenian violence
Anti-Armenian violence refers to acts of physical, psychological, or structural harm, including discrimination, persecution, and mass atrocities, specifically targeting Armenians because of their ethnic or national identity.
-
C.
anti-Danish pogrom
An anti-Danish pogrom is a violent, organized attack or campaign of persecution directed against Danish people or communities, typically driven by ethnic, national, or political hostility.
-
D.
intra-Jewish conflict
Intra-Jewish conflict refers to the historical and contemporary tensions, disagreements, and power struggles among diverse Jewish groups over religious authority, cultural identity, political ideology, and communal norms.
-
E.
anti-Black violence
Anti-Black violence is the systemic, institutional, and interpersonal use of physical, psychological, economic, or symbolic force that targets Black people and communities, rooted in anti-Black racism and histories of enslavement, colonialism, and racial hierarchy.
- 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_69f043e60b6c8190ac2cd042e77fe6e9 |
completed | April 28, 2026, 5:21 a.m. |
Created at: April 28, 2026, 5:36 a.m.