50/100

Moderate evidence

ProblemPublished recordMedia & ArtsProblem Space

Journalists’ Perceptions of Artificial Intelligence and Disinformation Risks

Truvace record
TRV-2026-2939raw data (JSON)
Version
v1Published
First published
Evidence type
Survey
Sources
1 sourcePeer-reviewed
sha256
4c4ef3e53c2e…check it

This study examines journalists’ perceptions of the impact of artificial intelligence (AI) on disinformation, a growing concern in journalism due to the rapid expansion of generative AI and its influence on news production and media organizations. Using a quantitative approach, a structured survey was administered to 504 journalists in the Basque Country, identified through official media directories and with the support of the Basque Association of Journalists. This survey, conducted online and via telephone be…

The problem

In a survey of 504 journalists in the Basque Country, 89.88% said AI will considerably or significantly increase the risks of disinformation, citing difficulty detecting false content and deepfakes and the risk of inaccurate data.

What this doesn’t fix

The results capture journalists' perceptions in one region, the Basque Country, rather than measured disinformation outcomes.

Sources

1 on file
  1. Journalism and Mediadoi:10.3390/journalmedia6030133
    Peer-reviewed2025-08-30

Cite this record

v1

Truvace Impact Record TRV-2026-2939, v1: “Journalists’ Perceptions of Artificial Intelligence and Disinformation Risks.” Truvace, 2026-11-15. /record/TRV-2026-2939 (accessed on the day you copy it). sha256 4c4ef3e53c2e59f3…

Change history

1 version

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv14c4ef3e53c2e…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-2939 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.