<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Neural Graph Reasoning: Complex Logical Query Answering Meets Graph Databases · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2303.14617/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/2303.14617/feed.xml" rel="self" type="application/rss+xml" /><item><title>Neural Graph Reasoning: Complex Logical Query Answering Meets Graph Databases — mentioned by freeone3000</title><link>https://news.ycombinator.com/item?id=36474029</link><guid isPermaLink="false">urn:hackerpapers:mention:2303.14617:36474029</guid><pubDate>Mon, 26 Jun 2023 00:04:56 GMT</pubDate><description>&lt;p&gt;In every model I’ve worked with, all of those steps are EXPLICIT. You take input, then tokenize, then embed, feed to model, then convert from embeddings to tokens, then back to words. There’s actually a lot of work done in embedding space! Chained execution, neural graph reasoning (see https://arxiv.org/pdf/2303.14617.pdf), even basic IR tasks like clustering and retrieval. There’s been no real effort to especially expose it because that is what you get by default. Even OpenAI has an “embed” endpoint. So you’re not going to see a huge push for it the same way you won’t see a push for…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2303.14617/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.DB</category></item></channel></rss>
