← Latest papers
🤖 machine learning

Explaining Graph Neural Networks for Node Similarity on Graphs

This paper investigates explainable similarity search on graphs by evaluating mutual information and gradient-based explanation methods for Graph Neural Networks, demonstrating that gradient-based approaches offer superior actionable, consistent, and sparsifiable explanations for node similarity scores.

Original authors: Daniel Daza, Cuong Xuan Chu, Trung-Kien Tran, Daria Stepanova, Michael Cochez, Paul Groth

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

Original authors: Daniel Daza, Cuong Xuan Chu, Trung-Kien Tran, Daria Stepanova, Michael Cochez, Paul Groth

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 have a giant, complex map of connections, like a massive social network or a web of scientific citations. You've built a smart computer program (a Graph Neural Network, or GNN) that looks at this map and says, "Hey, these two people (or papers) are very similar."

Usually, when these programs make a decision, we want to know why. But most of the time, the "why" only works for clear-cut answers like "Is this a cat or a dog?" or "Will this person click this ad?"

This paper asks a different question: What if the computer just says, "These two things are 85% similar"? How do we explain why it thinks that?

The authors realized that the usual tools for explaining AI don't work well for this "similarity" task. So, they built a new set of tools to test which explanation methods actually make sense. Here is how they did it, using some everyday analogies.

The Problem: The "Black Box" Similarity Score

Think of the GNN as a chef who has tasted two dishes and declared, "These two soups are very similar."

  • The Old Way (Supervised Learning): If the chef said, "This is soup," we could ask, "Did you taste the carrots?" or "Was it the salt?" We know the target (Soup vs. Not Soup).
  • The New Problem (Similarity): The chef just says, "Soup A and Soup B are 90% alike." If we ask, "Why?", the old tools might point to random ingredients that don't actually explain the similarity. They might say, "It's the salt!" but then if you remove the salt, the similarity score doesn't change much. That's a bad explanation.

The Solution: Three Rules for a Good Explanation

The authors came up with three rules (criteria) that a good explanation for similarity must follow. They tested these rules by playing "what if" games with the graph (the map).

1. Actionable (The "What If" Test)

  • The Analogy: Imagine the explanation says, "The reason these two soups are similar is the basil."
  • The Test: If you take the basil out of both soups, the similarity score should drop. If you add more basil, the score should go up.
  • The Claim: A good explanation must let you change the input (the graph) in a predictable way. If the explanation says "basil" but removing it does nothing, the explanation is useless.

2. Consistent (The "Opposite Sides" Test)

  • The Analogy: Imagine the explanation splits the ingredients into two piles: "Good for similarity" (Pile A) and "Bad for similarity" (Pile B).
  • The Test: If you keep only the "Good" pile, the soups should become more similar. If you keep only the "Bad" pile, they should become less similar.
  • The Claim: The two piles must do opposite things. If keeping the "Good" pile makes them similar, but keeping the "Bad" pile also makes them similar (or does nothing), the explanation is confusing and inconsistent.

3. Sparse (The "Essentials Only" Test)

  • The Analogy: A good explanation shouldn't say, "The similarity is because of every single grain of salt in the ocean." It should say, "It's because of these three specific herbs."
  • The Test: Can you throw away 90% of the ingredients the explanation pointed to, and still get the same result?
  • The Claim: A good explanation should be able to be shrunk down to a tiny, essential list without losing its power.

The Experiment: Who Passed the Test?

The authors took two popular types of AI explainers and tested them against these three rules on various maps (datasets like citation networks and knowledge graphs).

Team A: The "Mutual Information" Explainers (The Guessers)

  • How they work: They try to find a small subgraph that "contains" the answer, kind of like guessing which part of the soup recipe is most important by trial and error.
  • The Result: They failed the tests.
    • They weren't Actionable: Removing the ingredients they pointed to didn't reliably change the similarity score.
    • They weren't Consistent: Sometimes keeping the "important" ingredients made the score go up, and sometimes it went down. It was a coin flip.
    • They weren't Sparse: You couldn't easily shrink their list of ingredients.

Team B: The "Gradient-Based" Explainers (The Calculators)

  • How they work: They use math to calculate exactly how much every single edge (connection) in the map pushes the similarity score up or down. It's like a precise scale measuring the weight of every ingredient.
  • The Result: They passed all three tests!
    • Actionable: If they said an edge increases similarity, removing it made the score drop. If they said it decreases similarity, removing it made the score rise.
    • Consistent: The "up" edges and "down" edges did exactly opposite things.
    • Sparse: You could throw away 90% of the edges they pointed to, and the remaining few still explained the similarity perfectly.

The Big Takeaway

The paper concludes that when you are trying to explain why two things are similar (a continuous score), the "Gradient-Based" methods are the winners. They give you a clear, reliable, and compact map of why the computer thinks two nodes are alike.

The "Mutual Information" methods, which work great for simple "Yes/No" questions (like "Is this a cat?"), get confused when the question is "How much do these two things resemble each other?"

In short: If you want to know why two people in a network are similar, don't ask the AI to guess which connections matter. Ask it to calculate the exact push and pull of every connection. That gives you a clear, trustworthy answer.

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 →