Triple
T22498829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stop Watching Us |
E556214
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | anti-surveillance campaign |
C46401
|
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-surveillance campaign Context triple: [Stop Watching Us, instanceOf, anti-surveillance campaign]
-
A.
mass surveillance revelation
A mass surveillance revelation is the public disclosure of previously hidden, large-scale monitoring of individuals or populations by governments or organizations, exposing the scope, methods, and implications of such surveillance.
-
B.
mass surveillance program
A mass surveillance program is a systematic, often government-led initiative that continuously collects, monitors, and analyzes large-scale data about populations to track behavior, communications, and activities.
-
C.
electronic surveillance program
An electronic surveillance program is a system that monitors, collects, and analyzes digital communications or electronic data to detect, track, or investigate activities of interest, often for security, intelligence, or law enforcement purposes.
-
D.
anti-violence campaign
An anti-violence campaign is a coordinated set of messages, activities, and policies designed to prevent, reduce, and raise awareness about violence by promoting nonviolent behaviors, support resources, and cultural change.
-
E.
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.
- F. None of above. chosen
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_69e11e5445bc8190b6a9481926db3355 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:50 p.m.