Skip to content

Frequently asked questions

What happens if the AI makes a classification error?

Short answer

A person corrects it before it reaches anyone. At Innguma the AI proposes the classification of each signal, and the analyst reviews it in Factory, the space where Innguma processes and structures signals: correcting, discarding or validating. Each signal links to the publication it comes from, so any piece of information can be checked at its origin. AI processes; people decide what is published and who receives it.

How often does generative AI get things wrong?

Often enough that nothing should be published without review. Two independent studies on news measure it:

  • EBU and BBC, October 2025. 22 public broadcasters from 18 countries evaluated more than 3,000 responses from ChatGPT, Copilot, Gemini and Perplexity on current affairs. 45% had at least one significant problem; 31%, serious problems of source attribution; and 20%, major accuracy errors, such as invented details or outdated information[1].
  • Tow Centre, Columbia University, March 2025. Eight AI search engines were given fragments of real articles and asked to identify the headline, outlet, date and URL. Taken together, they answered incorrectly more than 60% of the 1,600 queries[2].

Both studies measure assistants that search and answer, not a classification system with review. What they show is the kind of failure to expect: attribution, dates and details that are plausible but false.

Which classification errors are common, and how are they detected?

Type of error Illustrative example How it is detected
Entity confused A company with the same name as a competitor, but from another sector The entity does not fit the rest of the signal or the source
Main topic wrongly assigned A technology mentioned in passing in an interview is tagged as the central topic When the source is opened, the mention occupies a single line
Wrong type of event An announcement of intent is classified as a launch The text uses the future or conditional tense
Tone misread An ironic headline, or a news item with nuances, is marked as positive The tone does not match the content
Imprecise place The company’s headquarters is assigned instead of the country where the event takes place The signal does not appear when filtering by the relevant country
Summary that claims too much A figure or conclusion that the source does not contain Cross-checking against the linked source

The last case is the most delicate. OWASP classes it as a misinformation risk: false content that seems credible, made worse by excessive trust on the part of the reader[3]. NIST calls it confabulation: erroneous content presented with confidence[4].

What controls does Innguma have against these errors?

  • Human review in Factory. It is the analyst’s working environment, where the signals the AI has filtered, grouped and classified are reviewed and validated.
  • Source always linked. Each signal links to the publication it comes from, so the data can be checked at its origin.
  • Decisions by people. What is published and who receives it is decided by the team, not by the AI.
  • A reviewable history. What has been validated is kept in the Library with its tags, comments and source, so the team can review what was validated and why.

If your organisation connects an assistant through MCP and enables automatic publication, the same principle applies: your team decides what is published without review and what passes through a person first.

How do you work well with automatic classification?

  1. Treat each tag as a proposal, not as a fact.
  2. Review more carefully whatever is going to be distributed or will support a decision.
  3. Open the original source before quoting a figure, a date or a statement.
  4. When a correction matters, explain it in a comment so that the team shares the criterion.
  5. If an error keeps recurring, adjust the filters or the definition of the watch, rather than correcting it again and again.

Sources and references

  1. [1] EBU. International study ‘News Integrity in AI Assistants’, coordinated by the EBU and led by the BBC. Press release, 22 October 2025
  2. [2] Jaźwińska, K. and Chandrasekar, A. AI Search Has a Citation Problem. Tow Center for Digital Journalism, Columbia Journalism Review. 6 March 2025
  3. [3] OWASP GenAI Security Project. LLM09:2025 Misinformation. 2025
  4. [4] NIST. AI 600-1, Artificial Intelligence Risk Management Framework: Generative Artificial Intelligence Profile. July 2024

Related