← Latest papers
🤖 AI

Rethinking Explanations: Formalizing Contrast in Description Logics

This paper proposes a user-centered framework for contrastive explanations in Description Logics that addresses the limitations of existing justification and abductive reasoning methods by formally defining and evaluating how to explain why a fact holds true instead of an alternative foil.

Original authors: Yasir Mahmood, Arnab Sharma, Axel-Cyrille Ngonga Ngomo, Balram Tiwari

Published 2026-05-06
📖 5 min read🧠 Deep dive

Original authors: Yasir Mahmood, Arnab Sharma, Axel-Cyrille Ngonga Ngomo, Balram Tiwari

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you are walking through a giant, magical library where every book represents a rule about how the world works. This library is built on a very strict, logical language called Description Logic (DL). In this library, a computer can look at a person (let's call him Alice) and a set of rules, and it can tell you, "Yes, Alice is hired!"

The Old Way: "Why?"

Usually, if you ask the computer, "Why is Alice hired?", it gives you a Justification. It pulls out the specific pages from the library that prove Alice is hired.

  • Analogy: It's like a teacher showing you the exact steps in a math problem to prove the answer is 5. It's accurate, but it only tells you about the "winner."

The New Problem: "Why Alice and not Bob?"

The authors of this paper noticed something humans do naturally: we don't just want to know why something happened; we want to know why it happened instead of something else.

Imagine Alice gets the job, but her friend Bob doesn't.

  • If you ask, "Why Alice?", the computer lists Alice's great skills.
  • If you ask, "Why not Bob?", the computer lists Bob's missing skills.
  • But Bob is confused. He doesn't want two separate lists. He wants to know: "Why Alice and not me?" He wants to see the difference between them.

The paper argues that giving two separate answers is unsatisfying. You need a Contrastive Explanation (CE) that highlights the specific gap between the two.

The Solution: The "Difference Finder"

The researchers created a new way to formalize this "Why P instead of Q?" question. They call the thing that happened the Fact (Alice) and the thing that didn't happen the Foil (Bob).

To explain the difference, they look at three things:

  1. What Alice had that Bob didn't: (e.g., Alice published in AI).
  2. What Bob had that Alice didn't: (e.g., Bob published in pure Math).
  3. What Bob was missing that would have made him hired: (e.g., Bob needed to publish in AI).

The Creative Analogy: The Race
Imagine a race between Alice and Bob.

  • Fact: Alice won.
  • Foil: Bob lost.
  • Old Explanation: "Alice ran fast." (True, but doesn't explain why Bob lost).
  • New Contrastive Explanation: "Alice ran fast because she trained on hills, whereas Bob trained on flat ground. If Bob had trained on hills (the missing piece), he would have won, but he didn't."

The paper formalizes this by taking the "proof" for Alice and the "proof" for Bob (even though Bob's proof is hypothetical) and finding the symmetric difference. They strip away the things both of them share (like "both are qualified") and focus only on the unique factors that decided the outcome.

The "What If" Scenario (Abduction)

Sometimes, the computer has to guess what would make the Foil true. This is called Abduction.

  • Analogy: If Bob didn't get hired, the computer asks, "What would have to be true for Bob to get hired?" It might say, "If Bob had published in AI."
  • The paper's method combines the real proof for Alice with this "what if" scenario for Bob to show exactly where the paths diverged.

Handling Glitches (Inconsistencies)

Sometimes, the rules in the library are tricky. What if the rules say "You can't be an AI Expert and a Theorist at the same time"?

  • If Bob is a Theorist, and the computer says, "If Bob were an AI Expert, he would be hired," there is a conflict.
  • The paper adds a safety net: it identifies these conflicts. It tells you, "Bob would be hired if he were an AI Expert, BUT that contradicts his nature as a Theorist." This prevents the explanation from breaking the logic of the library.

What They Actually Did

The authors didn't just write theory; they built a prototype (a working computer program) to test this.

  • They tested it on about 40 different real-world knowledge bases (like medical or technical databases).
  • They found that their method works quickly (in less than a second for most cases) and produces very short, easy-to-read explanations (usually just 1 or 2 sentences of logic).
  • They proved mathematically that for certain types of logic (called EL), this process is efficient and doesn't get stuck in an endless loop.

Summary

This paper is about upgrading how computers explain decisions. Instead of just saying "Here is why X happened," they now say, "Here is why X happened instead of Y." They do this by mathematically comparing the "winning" evidence with the "losing" (or hypothetical) evidence, stripping away the common parts, and showing you exactly what made the difference. They built a tool to do this, and it works fast and accurately on complex data.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →