cchance 13 minutes ago

Was super excited that it was going to be the actual papers, kinda cool but just being abstracts doesn't go very far, good luck getting the papers working thats gonna be pretty cool once working, then to feed it all into a vector db XD

lgas a day ago

It just extracts the abstracts?

  • jerpint a day ago

    For now , yes - abstracts and other metadata

    • rrekaf a day ago

      do you plan on adding descriptions of figures and tables?

      • jerpint 19 hours ago

        will probably focus on getting the text out of the papers first, figures might be a good next step after that

sbpost a day ago

The example you give doesn't seem to work - the raw txt does not have authors.

  • jerpint 19 hours ago

    you're right - I hadn't noticed! I fixed it now, thanks for pointing it out

jmartin2683 a day ago

This would be awesome wrapped in an MCP server/tool call :)

  • jerpint a day ago

    whoa - i haven't yet played with MCP - might be a good first project!

westurner a day ago

If you train an LLM on only formally verified code, it should not be expected to generate formally verified code.

Similarly, if you train an LLM on only published ScholarlyArticles ['s abstracts], it should not be expected to generate publishable or true text.

Traceability for Retraction would be necessary to prevent lossy feedback.