← Latest papers
🤖 AI

ABox Abduction for Inconsistent Knowledge Bases under Repair Semantics

This paper addresses the ABox abduction problem for inconsistent knowledge bases by defining suitable notions of abduction under repair semantics and providing a comprehensive complexity analysis for light-weight description logics DL-Lite and EL_bot.

Original authors: Anselm Haak, Patrick Koopmann, Yasir Mahmood, Anni-Yasmin Turhan

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

Original authors: Anselm Haak, Patrick Koopmann, Yasir Mahmood, Anni-Yasmin Turhan

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 a detective trying to solve a mystery, but your evidence board is a mess. You have a set of facts (the Knowledge Base) and a specific observation you are trying to explain (the Fact).

In a perfect world, your facts would all fit together perfectly. But in the real world, data is often messy. Maybe a sensor malfunctioned, or two reports contradict each other. When your facts clash, standard logic says, "Everything is true, and nothing is true," which makes it impossible to solve the mystery.

This paper is about how to keep solving mysteries even when your evidence board is broken.

The Core Problem: The Broken Evidence Board

The authors are working with Description Logics, which is a fancy way of saying "a structured way to organize facts about the world," like a medical database or a map of relationships.

  • The Scenario: You have a patient. The database says their glucose is "High" and "Low" at the same time. This is a contradiction (inconsistency).
  • The Goal: You observe that the patient is in a "Diabetic Coma." You want to know: "What extra fact, if we added it to our messy database, would explain why the patient is in a coma?" This is called Abduction.

The Old Way vs. The New Way

The Old Way (Classical Semantics):
If your database has a contradiction, classical logic throws its hands up. It says, "If you have a contradiction, then anything follows." So, you could "explain" the coma by saying "The patient is a unicorn," because the logic is so broken that unicorns are now true too. This is useless.

The New Way (Repair Semantics):
The authors propose a smarter approach. Instead of throwing away the whole database, they say: "Let's look at the different ways we can fix the contradictions."

  • Repair 1: Maybe the "High" reading was wrong. Let's ignore it.
  • Repair 2: Maybe the "Low" reading was wrong. Let's ignore that one.

These are called Repairs. The paper looks at two ways to use these repairs:

  1. Brave Semantics: "If the explanation works in at least one way of fixing the mess, let's accept it." (Optimistic)
  2. AR Semantics: "The explanation must work in every single possible way of fixing the mess." (Cautious)

The "Conflict-Confining" Rule

Here is the tricky part. If you add a new fact to explain the coma, you don't want to accidentally break the database even more.

  • The Analogy: Imagine you are trying to fix a leaky boat. You add a patch (the hypothesis). If your patch causes new holes to appear in the hull, you haven't really helped.
  • The Paper's Rule: They introduce a concept called Conflict-Confining. This means your new explanation should not create new contradictions. It should only work with the contradictions that already existed.

The Complexity Landscape (The "Difficulty" of the Puzzle)

The paper is a massive study of how hard it is to find these explanations. They tested this on two types of logic systems:

  1. DL-Lite: A simpler, lighter system (like a basic spreadsheet).
  2. EL⊥: A slightly more complex system (like a spreadsheet with formulas).

They found that the difficulty of finding an explanation depends heavily on:

  • Which logic system you use.
  • Which "fixing" strategy you use (Brave vs. AR).
  • What rules you set for the explanation (e.g., "Must not create new holes," "Must be the smallest possible explanation").

Key Findings:

  • For the simple system (DL-Lite): Finding explanations is often surprisingly easy. In some cases, it's as easy as just checking if the observation itself fits without breaking things further.
  • For the complex system (EL⊥): It gets much harder. Sometimes, finding an explanation is as hard as solving a puzzle that requires checking every possible combination of variables (a level of difficulty known as Σ2P\Sigma^P_2 or Π2P\Pi^P_2 in computer science).
  • The "Non-Convex" Surprise: In the complex system, you might find that a small explanation works, and a huge explanation works, but a medium-sized one in the middle doesn't work. It's like finding that a small key and a giant key open a door, but a medium key jams it. This makes finding the "best" explanation much harder.

Summary of the "Map"

The authors created a "complexity map" (Table 1 in the paper) that tells you exactly how hard a specific type of abduction problem is.

  • Easy (NL/P): You can solve this quickly, even on a small computer.
  • Medium (NP/coNP): You might need a powerful computer, but it's doable.
  • Hard (DP, Σ2P\Sigma^P_2, Π2P\Pi^P_2): This requires massive computing power and time, often involving guessing and checking many layers of possibilities.

The Bottom Line

This paper doesn't just say "we can fix broken data." It provides a rigorous mathematical map of how hard it is to find good explanations when data is broken. It tells us that while some types of messy data can be fixed easily, others require incredibly complex reasoning, and the rules we set for our explanations (like "don't make new conflicts") can drastically change how difficult the task is.

They also point out that in the future, they want to see how this works when the data is huge (Data Complexity) and when we allow the explanation to introduce brand new people or objects into the story, which might make things even harder.

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 →