← Latest papers
🤖 machine learning

LLM Features Can Hurt GNNs: Concatenation Interference on Homophilous Graph Benchmarks

This paper reveals that simply concatenating LLM-generated node features to GNN inputs can systematically degrade performance on homophilous benchmarks, a phenomenon driven by the LLM's standalone discriminability rather than graph homophily, and proposes a discriminability threshold to predict when such concatenation will be harmful.

Original authors: Zhongyuan Wang, Pratyusha Vemuri

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

Original authors: Zhongyuan Wang, Pratyusha Vemuri

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 Idea: When "Extra Help" Actually Hurts

Imagine you are trying to solve a difficult puzzle (classifying nodes on a graph) with very few clues (only a small number of labeled examples). You have a smart assistant (a Graph Neural Network, or GNN) who is pretty good at solving it using the clues you gave it (the original features).

Recently, many people started adding a "super-smart" consultant (an LLM, like GPT-4) to the team. The idea was: "If we just paste the consultant's notes right next to our original clues, the team will get even better."

This paper says: Sometimes, that's true. But often, it's a disaster.

The authors found that if you simply paste the LLM's notes next to the original clues without teaching the team how to ignore the bad parts, the team actually gets worse at solving the puzzle. In some cases, the accuracy drops so much it's like the consultant is shouting nonsense over the original clues, confusing everyone.


The Analogy: The Overcrowded Classroom

Think of the Graph Neural Network as a student taking a test.

  • The Original Features (Forig): These are the textbook notes the student has studied. They are clear and helpful.
  • The LLM Features (FLLM): These are a 384-page stack of new notes generated by an AI.
  • The Problem: The student only has time to study for a short exam (a small dataset with few labels).

If you hand the student their textbook plus that massive 384-page stack of AI notes and say, "Just read everything and answer the questions," the student gets overwhelmed. They spend so much time trying to process the extra noise that they forget the textbook. Their test score plummets.

The paper found that on famous, "homophilous" datasets (where similar things are grouped together, like a library where all biology books are on one shelf), adding these AI notes dropped the test scores by 17 points on the PubMed dataset. That's a huge failure.

Why Does This Happen? (The "Noise" vs. "Signal" Rule)

The authors discovered a simple rule to predict when the AI notes will help and when they will hurt. They call this Δsig\Delta_{sig} (LLM-alone discriminability).

  • The Rule: If the AI notes are clear and distinct on their own (High Signal), adding them helps.
  • The Rule: If the AI notes are vague or muddy on their own (Low Signal), adding them hurts.

The Metaphor:

  • High Signal (Helpful): Imagine the AI notes are a clear, highlighted map. Adding this to your textbook helps you find the answer faster.
  • Low Signal (Harmful): Imagine the AI notes are a blurry, scribbled mess that looks like it might be a map but is mostly just random lines. If you force the student to look at this blurry mess while trying to read the textbook, they get confused and make mistakes.

The paper found that on datasets like PubMed and Cora, the AI notes were "blurry" (low signal). When pasted in, they confused the model. But on datasets like WikiCS, the notes were "clear" (high signal), and the model got smarter.

What About the "Curse of Dimensionality"?

You might think, "Maybe the model just got confused because there were too many numbers (dimensions) to process?"

The authors tested this. They replaced the AI notes with:

  1. Pure Random Noise: (Like static on a radio).
  2. Same-source Redundancy: (Just copying the textbook notes again).

The Result:

  • Pure random noise hurt the model twice as much as the AI notes did.
  • This proves the AI notes did contain some useful information (they were better than pure noise).
  • However, that useful information wasn't enough to overcome the confusion caused by having so many extra numbers to process with so little training data. The "cost" of the extra noise was still higher than the "benefit" of the extra info.

The Solution: The "Volume Knob"

If you must use the AI notes (maybe your boss requires it), how do you fix the problem?

The authors tried several "cheap fixes":

  • Layer Normalization: Tried to smooth out the notes. Result: Made it worse.
  • Dropping Dimensions: Throwing away half the notes. Result: Helped a little, but not enough.
  • The Scalar Gate (The Volume Knob): This is a simple switch that learns how much of the AI notes to listen to.

The Winner: The "Volume Knob" worked best. It learned to turn the volume of the AI notes down to almost zero (about 10% volume) when the notes were blurry.

  • This recovered 89% of the lost accuracy.
  • But here's the kicker: The absolute best fix was to just delete the AI notes entirely and stick to the original textbook. The "Volume Knob" is only useful if you are forced to keep the AI notes in the system for some other reason.

Summary of Findings

  1. Don't just paste: Simply pasting LLM features next to graph features often hurts performance on small datasets.
  2. Check the signal first: If the LLM features aren't very informative on their own, don't add them.
  3. The "Small Data" Trap: This problem is worst when you have very few labeled examples (like the standard benchmarks used in research). If you have a huge amount of data, the problem disappears.
  4. The Fix: If you must use them, use a "gate" to mute them when they are bad. But honestly, it's often better to just leave them out.

The Bottom Line: The paper doesn't say LLMs are bad for graphs. It says that how you add them matters. The "brute force" method of just concatenating them is often a mistake that confuses the model, especially when data is scarce. You need smarter ways to integrate them (like the joint training methods used in other successful papers), or you risk making your AI dumber.

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 →