← Latest papers
💻 computer science

GRAFT: Graph-Matched Retrieval and Fusion of Tables in Data Lakes

The paper proposes GRAFT, a novel framework that models table retrieval in data lakes as a graph matching problem using an IGMS objective and an implicit Q-learning-based subgraph generation process to effectively integrate joinable and unionable tables, thereby significantly outperforming existing baselines in retrieval accuracy and evidence sufficiency.

Original authors: Daomin Ji, Hui Luo, Zhifeng Bao, Shane Culpepper, Shazia Sadiq

Published 2026-07-15
📖 6 min read🧠 Deep dive

Original authors: Daomin Ji, Hui Luo, Zhifeng Bao, Shane Culpepper, Shazia Sadiq

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 clues aren't in a single notebook. Instead, they are scattered across thousands of different filing cabinets in a massive, chaotic library called a "Data Lake." Some cabinets have lists of names, others have lists of numbers, and some have maps. To solve your case, you can't just grab the cabinet that looks most like your question; you need to find a specific chain of cabinets that can be snapped together like Lego bricks to build the full picture.

This is the problem GRAFT (Graph-Matched Retrieval and Fusion of Tables) tries to solve. The authors, a team of researchers from RMIT, University of Wollongong, and The University of Queensland, argue that old ways of searching these data lakes are like trying to solve a jigsaw puzzle by only looking at the color of the pieces, ignoring the shape.

The Old Way: The "Lonely Clue" Mistake

Previous methods acted like a lonely detective who picks up the single file that has the most matching words to their question. If you ask, "Who are the Computer Science professors?", the old system might grab a file full of professor names but miss the file that links them to their departments, or the file that lists the different types of professors.

The paper explicitly argues against two common strategies:

  1. Point-wise retrieval: Picking tables one by one based on how well they match the words in your question. The authors show this often returns a pile of disconnected files that can't be joined together.
  2. Greedy expansion: Starting with one file and just adding the next file that seems most related to the previous one. The paper suggests this is like following a breadcrumb trail that leads you in circles, missing the crucial bridge that connects two distant parts of the puzzle.

In a test using real-world datasets (called Spider and BIRD), these old methods often failed to find the "bridge" tables needed to connect the dots, leading to incomplete or wrong answers.

The New Way: GRAFT's "Master Blueprint"

GRAFT changes the game by treating the search like a graph matching problem. Instead of just reading words, it builds a "Master Blueprint" (called an Intent Graph) from your question. This blueprint maps out exactly what you need: the entities (like "Professor"), the attributes (like "Name"), and the invisible connections (like "works in Department") that must exist.

Then, it looks at the Data Lake as a giant, messy map of tables. It tries to find a path through this map that fits the blueprint perfectly.

To do this, GRAFT uses a clever scoring system called IGMS (Information-theoretic Graph Matching Score). Think of IGMS as a "usefulness meter" that checks three things at once:

  1. Relevance: Does this file actually talk about what I asked?
  2. Connectivity: Can this file actually be snapped onto the others I've already found?
  3. Diversity: Is this file adding new information, or is it just a copy of what I already have?

The paper proves mathematically that this scoring system is "submodular," which is a fancy way of saying it's smart about avoiding redundancy. It ensures you don't get two files that say the exact same thing, which would just clutter your evidence.

The "Self-Teaching" Detective

Here is where it gets really cool. The Data Lake doesn't come with a "Answer Key" telling the computer which tables are the right ones. So, how does GRAFT learn to find them?

The authors created a self-teaching loop. They built a robot that generates its own practice problems. It grabs a random chunk of the Data Lake, shrinks it down into a fake "question" (an intent graph), and then tries to rebuild the original chunk from that question. By doing this millions of times, the system learns a "value function"—basically, a gut feeling about which path through the data lake is most likely to lead to the right answer.

They used a technique called Implicit Q-learning (IQL) to train this gut feeling. In their experiments, they generated 200,000 of these self-made practice trajectories. The paper suggests that this self-generated training data is crucial because it allows the system to learn without needing humans to manually label thousands of examples.

The Results: Faster and Smarter

When the researchers tested GRAFT against the old methods, the results were measured and specific:

  • Accuracy: GRAFT improved the F1 score (a measure of overall accuracy) by 7.8% and the Sufficiency (the ability to find all necessary pieces) by 10.6% compared to the strongest previous method (JAR).
  • Speed: Even though it's doing complex math, GRAFT is fast. It takes about 3.5 seconds to find the answer on the Spider dataset. This is much faster than the "structure-aware" competitor JAR, which took 22.4 seconds, and is on par with the faster but less accurate greedy methods.
  • Real-world impact: In a task called "training data enrichment" (where the goal is to find extra data to make a prediction model better), GRAFT helped lower the error rate (RMSE) to 3.65 and boosted accuracy to 0.748, outperforming all other methods.

What the Paper Does Not Claim

It's important to know what GRAFT doesn't do. The paper does not claim that GRAFT can solve every possible data problem instantly.

  • It does not claim to be a "magic bullet" that works without any setup; it requires building a graph of the data lake first.
  • It does not suggest that the "self-generated" training data is perfect; the authors note that the quality of the training depends on how well the "compression operator" (the robot that shrinks the data) works.
  • The paper explicitly rules out the idea that simply adding more tables (high recall) is enough. They show that if you add too many redundant tables, the prediction models actually get worse because they get confused by the noise. GRAFT specifically avoids this by penalizing duplicate information.

The Bottom Line

The authors suggest that by treating table retrieval as a puzzle-matching game rather than a word-search, and by teaching the computer to learn from its own generated practice runs, we can build autonomous data agents that are much better at finding the right evidence. In their tests, this approach consistently beat the competition, finding the right mix of tables to answer complex questions without getting lost in the noise. It's a step toward a future where your computer doesn't just find a file for you, but assembles the whole story for you.

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 →