Same Graph Cross-Task Transfer in GNNs: Protocols and Predictors
This paper establishes a leakage-free evaluation protocol for same-graph cross-task transfer between node classification and link prediction in GNNs, revealing that transfer is strongly directional and predictable based on graph homophily, and introduces the CoTask Score to guide mechanism selection and avoid negative transfer.
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 mysteries in a giant, bustling city. In this city, the "graph" is the map of all the streets and connections between people. Usually, detectives specialize in just one type of case: either figuring out who a person is (like, "Is this person a baker or a baker's assistant?") or predicting who will become friends with whom next ("Will Alice and Bob hang out?"). For a long time, scientists building computer brains to solve these puzzles treated these as two totally separate jobs, using different rulebooks for each. But in the real world, the city map is the same for both jobs, and the clues for one often help with the other. The big question is: if you teach your computer brain to solve the "who is who" puzzle first, will it automatically get better at the "who will be friends" puzzle? Or does the reverse work? And more importantly, could trying to mix these clues actually confuse the computer and make it worse at both?
This paper dives into that exact question, but with a very strict set of rules to make sure the answer is real and not just a trick of the experiment. The researchers set up a "leakage-free" protocol, which is like making sure the detective doesn't accidentally peek at the answer key while studying the clues. They tested this on three different types of computer brains (called GCN, GraphSAGE, and GPS) across eleven different city maps. What they found is that the relationship between these two tasks is not a fair fight; it's a one-way street that depends entirely on how the city is built.
Here is the surprising twist they uncovered: Teaching the computer to identify people first (Node Classification) almost always helps it predict friendships later (Link Prediction), but only if the city is "homophilic." Think of homophily as a neighborhood where people who look alike or have the same job tend to live on the same street. In these friendly neighborhoods, knowing who lives where gives you a huge hint about who will become friends. It's like knowing that all the bakers live on Baker Street; if you see two people on that street, you can guess they might be friends.
However, the reverse is much trickier. If you teach the computer to predict friendships first and then try to use that knowledge to identify people, it often backfires. In fact, in many cases, it makes the computer worse at identifying people than if it had just started from scratch. The authors found that this "friendship-first" approach only works in a very specific, rare type of city: one where the street layout is so obvious that predicting friendships is easy, but figuring out who people are is still a mystery. In these "structure-dominant" cities, the friendship clues act like a structural map that helps the computer learn the layout, which then helps it guess the people's identities. But if the city is messy or the clues are weak, trying to reuse the friendship knowledge is like trying to drive a car using a map of a different country—it just leads to a crash.
The researchers also introduced a new way to measure success called the "CoTask Score." Imagine you are running a bakery and a coffee shop in the same building. You want to know if hiring one person to do both jobs saves money without ruining the quality of either. The CoTask Score is their way of calculating if the combined effort is actually better than doing the two jobs separately. They found that the safest bet is usually to train the computer to do both jobs at the same time, rather than trying to reuse a finished product from one job for the other.
In short, the paper suggests that while reusing knowledge between these two tasks is possible, it's not a magic bullet. You can't just assume that solving one problem will automatically solve the other. The direction matters, and the type of data matters. If your data is full of similar neighbors, teaching the computer to identify them first is a great shortcut. But if you try to teach it to predict friendships first to help with identification, you might just be wasting your time or making things worse. The key takeaway is that before you try to mix these tasks, you need to check your "city map" to see which direction the wind is blowing, or you might end up flying the wrong way.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.