apol commited on
Commit
bee1874
·
verified ·
1 Parent(s): de5c92f

Upload audited dataset v0.1.0 metadata

Browse files
Files changed (6) hide show
  1. .gitignore +5 -0
  2. CHANGELOG.md +13 -0
  3. CITATION.cff +15 -0
  4. CONTRIBUTING.md +26 -0
  5. LICENSE +6 -0
  6. README.md +185 -0
.gitignore ADDED
@@ -0,0 +1,5 @@
 
 
 
 
 
 
1
+ output/
2
+ *.xlsx
3
+ *.png
4
+ *.inspect.ndjson
5
+ .DS_Store
CHANGELOG.md ADDED
@@ -0,0 +1,13 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ # Changelog
2
+
3
+ ## 0.1.0 — 2026-08-11
4
+
5
+ - Initial claim-level schema.
6
+ - Deep anchor files for Romania, Moldova, New Hampshire, Brazil 2026, and U.S. 2026.
7
+ - Prospective watchlists for the two October/November 2026 elections.
8
+ - Explicit separation of occurrence, reach, attribution, behavioural effect, electoral effect, and institutional outcome.
9
+ - Claim-level anchor enrichment from the Romania and Moldova source ledgers, including separate domestic-financing, platform-network, synthetic-persona, and InfoLeaders evidence.
10
+ - Global comparative queue of 36 source-linked candidates across the Americas, Europe, Asia, and Africa, with boundary and second-review flags.
11
+ - Reproducible relational audit with identifier, reference, enum, date, evidence, and source-minimum checks.
12
+ - Source/current-output integrity hashes and a release audit with zero errors and seven explicit live-update warnings.
13
+ - Pre-release corrections to the Moldova payment denominator, candidate-date ambiguity, timeline-to-claim joins, and source-role vocabularies.
CITATION.cff ADDED
@@ -0,0 +1,15 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ cff-version: 1.2.0
2
+ message: "If you use this dataset, please cite it and the original sources for substantive claims."
3
+ title: "AI-Enabled Election Manipulation Cases"
4
+ type: dataset
5
+ authors:
6
+ - name: "Apol"
7
+ version: 0.1.0
8
+ date-released: 2026-08-11
9
+ license: CC-BY-4.0
10
+ keywords:
11
+ - elections
12
+ - artificial intelligence
13
+ - political manipulation
14
+ - deepfakes
15
+ - agency transfer
CONTRIBUTING.md ADDED
@@ -0,0 +1,26 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ # Contributing corrections and new cases
2
+
3
+ This dataset accepts evidence corrections, source replacements, and proposed cases. A submission should identify the stable record ID, state one atomic correction or addition, link the strongest available source, and explain whether it changes occurrence, reach, attribution, behavioural effect, electoral effect, or institutional outcome.
4
+
5
+ ## Minimum evidence
6
+
7
+ - Prefer an authoritative primary record plus independent corroboration.
8
+ - Quote only the smallest passage necessary to locate the evidence; do not redistribute copyrighted articles or harmful media.
9
+ - Separate creator, sponsor, distributor, platform, beneficiary, attributed state actor, and responding institution.
10
+ - Report the denominator for every scale figure. Accounts, calls, completed calls, views, followers, impressions, recipients, and unique voters are not interchangeable.
11
+ - Do not infer belief, turnout, votes, seats, or a result from reach alone.
12
+ - Include counterevidence, denials, acquittals, reversed orders, and unresolved attribution.
13
+
14
+ ## Promotion from `candidates`
15
+
16
+ A candidate can enter the included corpus only after it has a stable `case_id`, claim-level coding, source-role links, an event timeline, an agency-transfer path, and an explicit statement of the maximum conclusion warranted by the evidence. Boundary cases may remain in `candidates` when the main value is comparison rather than demonstrated harm.
17
+
18
+ ## Local validation
19
+
20
+ ```bash
21
+ node scripts/build-data.mjs
22
+ node scripts/validate-data.mjs
23
+ node scripts/audit-data.mjs
24
+ ```
25
+
26
+ A release must finish with zero audit errors. Warnings require written disposition in the changelog or source ledger.
LICENSE ADDED
@@ -0,0 +1,6 @@
 
 
 
 
 
 
 
1
+ Creative Commons Attribution 4.0 International
2
+
3
+ This work is licensed under the Creative Commons Attribution 4.0 International License.
4
+ To view a copy of this license, visit https://creativecommons.org/licenses/by/4.0/
5
+
6
+ The license covers the original selection, coding, and metadata in this repository. Third-party sources remain subject to their own rights and terms.
README.md CHANGED
@@ -1,3 +1,188 @@
1
  ---
2
  license: cc-by-4.0
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
3
  ---
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
  ---
2
  license: cc-by-4.0
3
+ language:
4
+ - en
5
+ pretty_name: AI-Enabled Election Manipulation Cases
6
+ size_categories:
7
+ - n<1K
8
+ tags:
9
+ - elections
10
+ - political-disinformation
11
+ - generative-ai
12
+ - deepfakes
13
+ - agency-transfer
14
+ - dataset-card
15
+ configs:
16
+ - config_name: cases
17
+ data_files:
18
+ - split: data
19
+ path: data/cases.csv
20
+ - config_name: claims
21
+ data_files:
22
+ - split: data
23
+ path: data/claims.csv
24
+ - config_name: sources
25
+ data_files:
26
+ - split: data
27
+ path: data/sources.csv
28
+ - config_name: events
29
+ data_files:
30
+ - split: data
31
+ path: data/events.csv
32
+ - config_name: case_sources
33
+ data_files:
34
+ - split: data
35
+ path: data/case_sources.csv
36
+ - config_name: watchlist
37
+ data_files:
38
+ - split: data
39
+ path: data/watchlist.csv
40
+ - config_name: candidates
41
+ data_files:
42
+ - split: data
43
+ path: data/candidates.csv
44
  ---
45
+
46
+ # AI-Enabled Election Manipulation Cases
47
+
48
+ An auditable, claim-level dataset of election-related manipulation in which AI, algorithmic systems, synthetic media, coordinated networks, or automated distribution materially shaped the incident or the response.
49
+
50
+ **Research cut-off:** 11 August 2026. The rows are English-language research metadata; source material spans several languages. This is an evidence index, not a benchmark or a labelled text-classification corpus.
51
+
52
+ Version `0.1.0` centers five case families:
53
+
54
+ 1. Romania's annulled 2024 presidential election and 2025 repeat election.
55
+ 2. Moldova's 2024 presidential election and EU referendum, with linked evidence from the 2025 parliamentary campaign.
56
+ 3. The January 2024 New Hampshire AI-cloned Biden robocall.
57
+ 4. Brazil's October 2026 general election, currently an ongoing case and monitoring file.
58
+ 5. The United States' November 2026 midterm election, currently an ongoing case and monitoring file.
59
+
60
+ The dataset intentionally does **not** treat every case as a “deepfake case.” It separately records synthetic media, recommender-system amplification, coordinated inauthentic behaviour, bots, illicit finance, telecom delivery, and institutional response.
61
+
62
+ ## Release structure
63
+
64
+ The release has two deliberately different evidentiary layers:
65
+
66
+ - **Included corpus:** incidents and ongoing files that have been decomposed into atomic claims and joined to a source register and event timeline.
67
+ - **Comparative candidates:** a global research queue. These rows are useful leads and boundary cases, but they are not counted as fully included cases until claim-level coding is complete.
68
+
69
+ This distinction prevents a long list of reported “AI election incidents” from masquerading as a validated event dataset.
70
+
71
+ ### Coverage in `0.1.0`
72
+
73
+ | Layer | Rows | What the count means |
74
+ |---|---:|---|
75
+ | Included cases | 9 | Five case families: Romania, Moldova, New Hampshire, Brazil 2026, and U.S. 2026 |
76
+ | Atomic claims | 85 | Separately coded occurrence, mechanism, reach, attribution, effect, response, and counterevidence statements |
77
+ | Sources | 57 | Primary records, independent reporting, technical investigations, and explicit counterevidence |
78
+ | Timeline events | 31 | Observed, contested, and prospective events kept distinct |
79
+ | Case–source links | 63 | Source role and supported claim types |
80
+ | Defensive watch indicators | 12 | Brazil and U.S. 2026 monitoring rules; not incident predictions |
81
+ | Comparative candidates | 36 | Twelve Americas, twelve Europe, and twelve Asia/Africa leads, including boundary and reserve cases |
82
+
83
+ The release audit reports **0 errors** and **7 expected live-review warnings**. All seven warnings identify time-sensitive Brazil or U.S. 2026 claims that require updating as proceedings and campaigns evolve; they are not silently treated as final facts.
84
+
85
+ ## What is distinctive
86
+
87
+ - The unit of evidence is a **claim**, not a news article.
88
+ - Occurrence, reach, attribution, behavioural effect, electoral effect, and institutional outcome are separate claim types.
89
+ - Every non-open claim has an evidence label, confidence score, and explicit source links; unsourced open questions are explicitly labelled.
90
+ - Prospective and ongoing elections are never encoded as completed harms.
91
+ - The `agency_transfer_path` records who controls the system, what capacity is transferred away from citizens or institutions, and where power concentrates.
92
+ - Counterevidence and unresolved questions are first-class fields.
93
+
94
+ ## Files
95
+
96
+ | Config | Unit | Purpose |
97
+ |---|---|---|
98
+ | `cases` | Case or case family | Core comparative metadata and assessed mechanism |
99
+ | `claims` | Atomic claim | Evidence status, confidence, support, and counterevidence |
100
+ | `sources` | Source | Provenance and quality metadata |
101
+ | `events` | Dated event | Auditable case timeline |
102
+ | `case_sources` | Case–source link | Many-to-many source roles |
103
+ | `watchlist` | Observable indicator | Prospective monitoring for Brazil and U.S. 2026 |
104
+ | `candidates` | Comparative lead | Global comparison queue kept separate until full claim-level coding |
105
+
106
+ `data/stats.json` reports current row counts and `data/audit.json` records the automated quality-assurance result. `data/schema.json` contains the generated column order for every config.
107
+
108
+ ## Quick start (after Hub publication)
109
+
110
+ ```python
111
+ from datasets import load_dataset
112
+
113
+ cases = load_dataset(
114
+ "apol/ai-election-manipulation-cases",
115
+ "cases",
116
+ split="data",
117
+ )
118
+
119
+ claims = load_dataset(
120
+ "apol/ai-election-manipulation-cases",
121
+ "claims",
122
+ split="data",
123
+ )
124
+ ```
125
+
126
+ The configs are relational rather than independent training sets. Join `claims`, `events`, `case_sources`, and `watchlist` to `cases` with `case_id`; join `case_sources` and the pipe-delimited `claims.source_ids` to `sources` with `source_id`. Stable IDs are never reused for a different incident.
127
+
128
+ ## Evidence labels
129
+
130
+ - `established_evidence`: supported by a primary record or multiple high-quality independent sources.
131
+ - `strong_inference`: the inference is well supported but not directly observed or adjudicated.
132
+ - `plausible_hypothesis`: coherent and evidence-informed, but important links remain unverified.
133
+ - `speculative_scenario`: a forward-looking possibility; never counted as an observed event.
134
+ - `open_question`: the dataset records the uncertainty rather than resolving it.
135
+
136
+ Confidence is reported on a `0–1` scale and refers to the claim **as worded**, not to the case as a whole.
137
+
138
+ ## Reading a claim correctly
139
+
140
+ The dataset distinguishes six questions that are often collapsed in public discussion:
141
+
142
+ 1. **Occurrence:** did the content, network, payment, call, rule, or institutional act exist?
143
+ 2. **Reach:** what denominator was measured—attempts, completed calls, views, followers, accounts, or recipients?
144
+ 3. **Attribution:** who created, financed, directed, distributed, or merely benefited from it, and at what evidentiary level?
145
+ 4. **Behavioural effect:** did a person believe, prefer, abstain, turn out, or vote differently?
146
+ 5. **Electoral effect:** is there evidence about votes, seats, margins, or the result?
147
+ 6. **Institutional outcome:** what did a court, regulator, election authority, platform, or law-enforcement body do?
148
+
149
+ Evidence for one question is not silently promoted into another. In particular, views and virality are not treated as proof of persuasion, and an institutional decision is not automatically a causal estimate of changed votes.
150
+
151
+ ## Central limitation
152
+
153
+ Evidence of electoral effect is scarce. Reach, virality, exposure, or institutional alarm must not be translated into votes changed. Most cases therefore have strong evidence about occurrence and response, but `unknown` or low-confidence evidence for behavioural and electoral effects.
154
+
155
+ The source register also mixes different kinds of authority. A court order is authoritative evidence that an order was issued; a regulator's allegation is authoritative evidence of that allegation; a platform report is evidence of the platform's measurement or attribution. None is treated as omniscient evidence of every underlying fact.
156
+
157
+ ## Intended and unsuitable uses
158
+
159
+ Suitable uses include comparative case research, source discovery, institutional-response analysis, hypothesis generation, and testing how different evidence thresholds change a case narrative.
160
+
161
+ Do not use the release as:
162
+
163
+ - a prevalence estimate for all elections or all online political content;
164
+ - a causal estimate of votes changed;
165
+ - a list of proven foreign operations without consulting `actor_attribution_status` and the atomic claims;
166
+ - training data for reproducing deceptive media, targeting voters, or evading detection;
167
+ - a static forecast of the unfinished 2026 elections.
168
+
169
+ ## Ongoing-election protocol
170
+
171
+ Brazil and the United States in 2026 are versioned as-of files. Observed events, disputed allegations, legal rules, future deadlines, and defensive monitoring indicators remain separate. A scheduled election or plausible risk never becomes an incident row by implication. Later releases may revise ongoing records while preserving the changelog.
172
+
173
+ ## Methodology and ethics
174
+
175
+ See [`docs/methodology.md`](docs/methodology.md), [`docs/codebook.md`](docs/codebook.md), and [`docs/ethics-and-release.md`](docs/ethics-and-release.md).
176
+ Corrections and promotion criteria are documented in [`CONTRIBUTING.md`](CONTRIBUTING.md).
177
+
178
+ To reproduce the generated files locally:
179
+
180
+ ```bash
181
+ node scripts/build-data.mjs
182
+ node scripts/validate-data.mjs
183
+ node scripts/audit-data.mjs
184
+ ```
185
+
186
+ ## Citation
187
+
188
+ See [`CITATION.cff`](CITATION.cff). Cite original sources for substantive factual claims and this dataset for the coding and synthesis.