AI incident ·
AI-Powered 'Insights' Feature for the Los Angeles Times Allegedly Justifies Ku Klux Klan’s History
In brief
An AI system built by Perplexity and deployed by Los Angeles Times and Patrick Soon Shiong allegedly harmed Los Angeles Times Readers, Los Angeles Times and 1 other.
- Risk domain
- Discrimination and Toxicity
- Occurred
- Coverage
- 2 reports
What happened
The Los Angeles Times removed its AI-generated “insights” feature after it is alleged to have produced a defense of the Ku Klux Klan. The AI reportedly framed the hate group as a product of societal change rather than an extremist movement. The AI tool, developed by Perplexity and promoted by owner Patrick Soon-Shiong, was designed to provide “different views” on opinion pieces.
Laws that address this harm
Policy angle: Classified under Discrimination and Toxicity (Exposure to toxic content) in the MIT AI Risk Repository taxonomy; 5 recorded instruments address this use case.
- Colorado AI Act
- India DPDP Act
- Law No. 132/2025 on artificial intelligence
- NYC Local Law 144 (automated employment decision tools)
- EU AI Act
Matched from the record's risk domain and country to the instruments recorded here. A reviewer can correct the match in the repository (data/external/incident_overrides.yaml).
News reports (2)
Titles link to the original publisher; report text is not reproduced here.
Who was involved
- Alleged deployer
- Los Angeles Times, Patrick Soon Shiong
- Alleged developer
- Perplexity
- Alleged harmed party
- Los Angeles Times Readers, Los Angeles Times, General Public
Classification (MIT AI Risk Repository taxonomy)
- Risk domain
- Discrimination and Toxicity
- Risk subdomain
- 1.2 Exposure to toxic content
- Causal entity
- AI
- Intent
- Unintentional
- Timing
- Post-deployment
- Harm level
- —
- Sectors
- —
- Countries
- —
Risk entries describing this failure mode
Entries from the MIT AI Risk Repository coded to subdomain 1.2.
- Harmful Content
"The LLM-generated content sometimes contains biased, toxic, and private information"
- Toxicity
"Toxicity means the generated content contains rude, disrespectful, and even illegal information"
- Toxic Training Data
"Following previous studies [96], [97], toxic data in LLMs is defined as rude, disrespectful, or unreasonable language that is opposite to a polite, positive, and healthy language environment, including hate speech, offe...
- Not-Suitable-for-Work (NSFW) Prompts
"Inputting a prompt contain an unsafe topic (e.g., notsuitable-for-work (NSFW) content) by a benign user. "
- Controversial Opinions
The controversial views expressed by large models are also a widely discussed concern. Bang et al. (2021) evaluated several large models and found that they occasionally express inappropriate or extremist views when disc...
- Toxicity and Abusive Content
This typically refers to rude, harmful, or inappropriate expressions.
- Harmful responses
"Current Frontier AI mdoels amplify existing biases within their training data and can be manipulated into providing potentially harmful responses, for example abusive language or discriminatory responses91,92. This is n...
- Violation of social norms
"Second, because LLMs are trained on internet text data, there is also a risk that model weights encode functions which, if deployed in particular contexts, would violate social norms of that context. Following the princ...
Incidents in the same risk subdomain
- KBS AI Translation Subtitles Reportedly Broadcast Profanity During Artemis II Launch Livestream
- Grok Allegedly Generated Publicly Visible Sexist Abuse Targeting Swiss Finance Minister Karin Keller-Sutter After X User Prompt
- Trump Reportedly Posted Purportedly AI-Generated Racist Video Depicting Barack and Michelle Obama as Apes on Truth Social
- Tencent's WeChat-Integrated Yuanbao Chatbot Reportedly Insulted User During Coding Debug Request
- Alleged Harmful Outputs and Data Exposure in Children's AI Products by FoloToy, Miko, and Character.AI
- AI Training Dataset for Detecting Nudity Allegedly Found to Contain CSAM Images of Identified Victims
Source record: incident #964 on the AI Incident Database · all 2 reports