DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to check whether two papers agree on a specific claim with Thesys Core

Select two library PDFs, turn on Compare, and see which retrieved passage pairs support or contradict a claim.

  • Research
  • Intermediate
  • 90 minutes
  • From the README
  • Any agent

Credentials. Compare needs a TYPESAFE_API_KEY and chat needs an OPENAI_API_KEY in backend/.env, so keep that file out of shared repos and screenshots.

Who it is forA researcher writing a related-work section who needs to see where two papers agree or disagree on one result.

The problemReading two long papers side by side to find where they conflict on one claim is slow and easy to get wrong.

The outcomeA side panel listing passage pairs from both papers, each labeled corroboratory, contradictory, or neutral, with a confidence value.

What you need first

  • Docker, or Python 3.11+ and Node.js 20+ for the local setup
  • An OpenAI API key for chat
  • A contact email for the EMAIL setting used by citation lookup
  • A TypeSafe API key only if you want the Compare feature

Steps

  1. Run cp backend/.env.example backend/.env and set OPENAI_API_KEY, EMAIL, and TYPESAFE_API_KEY in backend/.env.
  2. Run docker compose up --build from the repo root and open http://127.0.0.1:5000.
  3. Upload the two papers to the library, then select both PDFs.
  4. Turn Compare on, ask about one specific claim, and read the side panel of labeled pairs with confidence.
  5. Open the cited passages to confirm each label before you use it in your writing.

Prompt for your agent

Use the Sreehari05055/thesys-core repo with a valid TYPESAFE_API_KEY to compare the two library papers <paper A> and <paper B> on the claim <claim text>. Output the list of passage pairs with their labels and confidence values. Verify that each pair shows the matching passages in both PDFs.

Caveat. Compare is unavailable without TYPESAFE_API_KEY, and the labels are model classifications that still need your reading of the passages.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page