<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Poly-Vector Retrieval: Reference and Content Embeddings for Legal Documents · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2504.10508/</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/2504.10508/feed.xml" rel="self" type="application/rss+xml" /><item><title>Poly-Vector Retrieval: Reference and Content Embeddings for Legal Documents — mentioned by joaoli131</title><link>https://news.ycombinator.com/item?id=43967801</link><guid isPermaLink="false">urn:hackerpapers:mention:2504.10508:43967801</guid><pubDate>Mon, 12 May 2025 21:49:28 GMT</pubDate><description>&lt;p&gt;Embeddings are still underrated—even in RAG. Legal text is deeply hierarchical and full of pointers (“Art. 5 CF”, “see Art 34”). One vector per article leaves too much on the table. Things that moved the needle for us: – *Multi-layer embeds* vectors for every paragraph and every structural level (chapter → book). Retriever picks the right granularity. (arXiv:2411.07739) – *Propositional queries* strip speech-act fluff (“could you please…”) before embedding. Similarity + top-k recall jump. (arXiv:2503.10654) – *Poly-vector retrieval* two vectors per norm—one for content, one for the…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2504.10508/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.IR</category></item></channel></rss>
