Link Prediction or Perdition: the Seeds of Instability in Knowledge Graph Embeddings
This paper reveals that high-performing Knowledge Graph Embedding models suffer from significant instability across random seeds and hyperparameter configurations, challenging the reliability of current rank-based evaluation metrics and the robustness of link prediction results.
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
The Big Picture: The "Magic Crystal Ball" Problem
Imagine you have a massive, incomplete encyclopedia of facts (a Knowledge Graph). It knows that "Paris is the capital of France," but it doesn't know who the current president of a specific country is.
To fill in the blanks, scientists use Knowledge Graph Embedding Models (KGEMs). Think of these models as magic crystal balls. You ask the crystal ball, "Who is the president?" and it looks at all the facts it knows, does some complex math, and predicts the answer.
The paper argues that while these crystal balls are great at getting the right answer on average, they are incredibly unreliable when you look at the specific details. If you ask the same question to the same crystal ball twice, but you flip a coin to decide how to start the process (a "random seed"), you might get two completely different lists of top candidates, even though the crystal ball claims it is equally confident both times.
The Core Problem: The "Same Score, Different Story"
In the world of machine learning, we usually judge these models by a single score, like MRR (Mean Reciprocal Rank). Think of this score as a report card grade.
- The Paper's Finding: If you train a model five times with different random seeds, they all get an "A" (a high MRR score).
- The Catch: Even though they all got an "A," the specific answers they give are totally different.
The Analogy: The Restaurant Review
Imagine three food critics (the models) reviewing a restaurant.
- Critics 1, 2, and 3 all give the restaurant a 5-star rating (High MRR).
- However, when you ask them to list their top 3 favorite dishes:
- Critic 1 says: Steak, Salad, Soup.
- Critic 2 says: Pizza, Tacos, Sushi.
- Critic 3 says: Burger, Fries, Ice Cream.
If you were a customer trying to decide what to order based only on the 5-star rating, you'd think they all agree. But in reality, they are recommending completely different meals. If you are a doctor trying to find a treatment for a disease (a real-world use case mentioned in the paper), getting a list of "Burgers" instead of "Medicine" because of a random coin flip is dangerous.
The Investigation: What Causes the Chaos?
The authors acted like detectives to figure out why these models change their minds. They isolated the "random ingredients" in the training process:
- Initialization: How the model starts its brain (like rolling dice to set the initial weights).
- Triple Ordering: The order in which the model reads the facts (like reading a book from page 1 to 100 vs. page 100 to 1).
- Negative Sampling: How the model learns what is wrong (like a teacher giving you wrong answers to correct).
- Dropout: Randomly turning off parts of the model's brain during training (like a student taking a test with their eyes closed for a few seconds).
- Hardware: The actual computer chip (GPU) used to run the model.
The Shocking Discovery:
The paper found that changing just one of these ingredients is enough to cause massive instability.
- The Analogy: Imagine baking a cake. If you change the brand of flour, the oven temperature, or the order you mix the eggs, you might end up with a cake that tastes exactly the same (same MRR score) but has a completely different texture or shape (different predictions).
- The Hardware Twist: They even found that using a different brand of computer chip (GPU) caused the same level of chaos as changing the random seeds. This means if you train a model on a computer in New York and run it on a computer in Tokyo, you might get different results, even if you use the exact same code.
The "Voting" Fix: Does It Work?
The authors tested a common solution called Voting. This is like asking five different critics to vote on the best dish and taking the majority.
- The Result: Voting helped a little bit. It made the models slightly more consistent.
- The Limit: It didn't fix the problem completely. The models still disagreed on many details. Plus, it costs more time and money to train five models instead of one.
The Bottom Line: Performance Stability
The most important takeaway is this: A high score does not guarantee reliability.
- Old Way: "This model has the highest score, so it's the best."
- New Reality: "This model has the highest score, but it's a gamble. It might give you the right answer today and a completely different (but equally 'high-scoring') answer tomorrow."
The paper concludes that we need to stop just looking at the "report card grade" (MRR) and start checking if the model is stable. If we are using these models to make real-world decisions (like finding drug treatments or completing knowledge bases), we need to know that the model isn't just guessing randomly every time we run it.
Summary in One Sentence
Just because a Knowledge Graph model gets a high score on a test doesn't mean it's trustworthy; tiny random changes in how it's trained can cause it to give completely different answers, making it risky to rely on for important decisions.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.