Triple
T35535353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Informbiro period |
E1026917
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | political repression period |
C26802
|
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: political repression period Context triple: [Informbiro period, instanceOf, political repression period]
-
A.
mass political repression
Mass political repression is the systematic, large-scale use of coercion, surveillance, and violence by authorities to silence, control, or eliminate political opposition and dissent within a population.
-
B.
perpetrator of political repression
A perpetrator of political repression is an individual, group, or institution that intentionally uses coercive, violent, or manipulative means to silence, control, or punish people for their political beliefs, activities, or affiliations.
-
C.
victims of political repression
Individuals who have been unjustly targeted, persecuted, or punished by state or political authorities due to their beliefs, affiliations, or activities that are perceived as oppositional or threatening to the existing power structure.
-
D.
state repression campaign
A state repression campaign is a coordinated effort by government authorities to control, intimidate, or eliminate perceived opponents through legal, extralegal, or violent means.
-
E.
period of state terrorism
chosen
A period of state terrorism is a span of time during which a government systematically uses violence, intimidation, and repression—often outside legal norms—to control, coerce, or eliminate perceived opponents or populations.
- 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_69f76dff7e508190b28ceeee770dce23 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:04 p.m.