Triple
T15720090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Condor |
E381068
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | campaign of political repression |
C948
|
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: campaign of political repression Context triple: [Operation Condor, instanceOf, campaign of political repression]
-
A.
state repression campaign
chosen
A state repression campaign is a coordinated effort by government authorities to control, intimidate, or eliminate perceived opponents through legal, extralegal, or violent means.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
Fascist campaign
A fascist campaign is a coordinated political effort that promotes authoritarian nationalism, suppresses opposition, and seeks to consolidate power under a dictatorial leadership through propaganda, coercion, and the erosion of democratic institutions.
- 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_69d86d9bf930819082b30cf6d169297c |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:45 a.m.