A Reddit prototype turns paper search into a claim-graph contradiction check

A self-post on r/MachineLearning offers an interesting view of where research tooling could go next. Two students say they kept running into the same literature problem: papers can make opposite claims about the same topic, but unless a reader happens to see both, the conflict is easy to miss. Their prototype tries to make that mismatch visible automatically instead of leaving it buried inside search results and note-taking.

The system works by extracting causal claims from papers and storing them in a relationship graph. In the authors' example, the tool looks for statements such as "X improves Y," "X reduces Y," or "X enables Y," then checks whether another paper asserts the opposite relationship. When it finds a conflict, it surfaces both papers side by side. The students say they tested the prototype on roughly 50 papers from one professor's publication list and that it surfaced conflicting findings they likely would not have noticed by reading abstracts alone.

How the prototype is built

• Python and FastAPI on the backend
• React on the frontend
• Neo4j as the graph database
• OpenAlex for paper data
• LLMs for claim extraction

That stack matters because it shifts the center of literature tooling away from retrieval and toward relationship analysis. Search systems are already good at finding papers. The harder problem is showing when two studies appear to disagree and doing so at the level of claims rather than keywords. If a tool like this becomes reliable enough, it could help researchers identify contested findings earlier, whether they are planning experiments, reviewing prior work, or checking whether a citation is being treated as consensus too casually.

The authors are also clear about the current limits. Claim extraction can drop important conditions from sentences, the system sometimes proposes odd hypotheses, and domain filtering still needs work. They also admit that part of the architecture evolved through exploratory "vibe coding" while testing the idea. That honesty is useful because the value of the prototype is not that it can definitively judge scientific contradictions today. It is that it treats literature review as a claim-graph problem that might be partially automatable.

For real research workflows, trust will be the deciding issue. A contradiction label is only helpful if the surrounding evidence remains intact. Differences in dataset, setup, measurement, or experimental assumptions can make two surface-level claims look incompatible when they are not. Even so, the Reddit post is a strong signal that research tooling is moving beyond ranking and retrieval. It is starting to ask whether LLMs, graph databases, and structured metadata can help researchers inspect disagreement directly, not just search around it.