FLOWREADER: Min-Cost Flow Optimization for Multi-Modal Long Document Q&A
FLOWREADER addresses the challenge of answering questions from fragmented multimodal long documents by reframing evidence assembly as a min-cost flow optimization problem on a node graph, which unifies scoring, routing, and adaptive compute to outperform top- retrieval baselines on benchmarks dominated by scattered evidence.
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 trying to solve a complex mystery, but the clues are scattered across a massive library. Some clues are written on sticky notes (text), some are drawn on whiteboards (images), and others are hidden inside complex spreadsheets (tables). The problem is that these clues are often broken up: a single fact might be split between a chart on page 5 and a paragraph on page 12, or a table might be so wide it spans three different slides.
Most current AI systems act like a frantic librarian who grabs the top 5 most relevant-looking pages and hands them to a detective (the AI). If the answer requires connecting a chart on page 5 to a sentence on page 12, the librarian often misses the connection because they are looking at pages in isolation.
FLOWREADER is a new system that changes how the librarian works. Instead of just grabbing pages, it treats the entire library as a giant, interconnected map and uses a mathematical concept called "Minimum-Cost Flow" to find the best path to the answer.
Here is how it works, step-by-step:
1. The Map (The Multimodal Graph)
First, FLOWREADER builds a map of the document.
- Nodes: Every piece of information (a paragraph, a cell in a table, a chart) is a "node" on the map.
- Edges: Lines connect these nodes if they are related. A line might connect a chart to the text describing it, or a table header to the data rows below it.
- The Goal: The system wants to find a path from the "Question" (where you start) to the "Answer" (where you end up) by traveling through the most useful clues.
2. The Traffic Flow (Min-Cost Flow)
Instead of just picking the "best" 5 pages, FLOWREADER treats the search like managing traffic on a highway.
- The Budget: Imagine you have a fixed amount of "fuel" (a budget) to send a convoy of trucks from the start to the finish.
- The Cost: Every road (connection between clues) has a "cost."
- If a road connects two very relevant, high-quality clues, the cost is low (easy to travel).
- If a road connects weak or irrelevant clues, the cost is high (hard to travel).
- The Optimization: The system calculates the most efficient way to send your "fuel" to reach the answer. It naturally avoids dead ends and finds the smoothest, most logical chain of evidence, even if that chain jumps between text, tables, and images.
3. The Filter (Replicator Dynamics)
Once the system finds all the possible routes, it might have too many of them, and some might be duplicates.
- Think of this like a reality TV show elimination round.
- The system runs a game where different routes compete. The "winners" are routes that are both high quality (good clues) and diverse (not just repeating the same fact).
- This ensures the final list of clues is short, non-redundant, and covers all the necessary angles.
4. The Double-Check (System 2 Gate)
Sometimes, the first attempt isn't enough. Maybe the clues are too fragmented, or the answers from different routes contradict each other.
- The Gatekeeper: A smart gatekeeper checks the situation. If the "traffic" is stuck (low saturation) or the drivers (AI workers) are giving conflicting reports, the gate opens.
- The Refinement: This triggers a "System 2" pass—a slower, more deliberate second look. The system might add a new bridge between two disconnected parts of the map or re-evaluate the clues.
- Efficiency: Crucially, this second look only happens when absolutely necessary, saving time and computing power.
Why It Matters (The Results)
The paper tested this system on VisDoMBench, a benchmark full of difficult questions about scientific papers, slides, and tables where information is often broken apart.
- The Problem with Old Methods: Traditional methods (Top-K retrieval) often fail here because they can't "see" the connection between a chart and a distant paragraph.
- FLOWREADER's Success: By using the "traffic flow" method, FLOWREADER excelled at these fragmented tasks.
- It beat the previous best system on PaperTab (long tables) by a significant margin.
- It also improved performance on SlideVQA (slides with mixed text and images).
- Overall, it was highly competitive across all tests, proving that treating evidence assembly as a flow problem works better than just grabbing the top few chunks.
In Summary
FLOWREADER stops treating a document like a pile of separate pages. Instead, it sees the document as a living network. It uses math to route its "attention" like water flowing through pipes, finding the most efficient, connected path to the answer, and only doing extra work when the path looks shaky. This makes it much better at solving puzzles where the clues are scattered across different types of media.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.