<?xml version='1.0' encoding='UTF-8'  ?><rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:dc="http://purl.org/dc/elements/1.1/">	<channel rdf:about="http://www.semanlink.net/tag/reranker">		<title>Reranking</title>		<link>http://www.semanlink.net/tag/reranker</link>		<description>Documents tagged with Reranking</description>		<items>			<rdf:Seq>							<rdf:li resource="http://www.semanlink.net/doc/2024/09/engineering_blog_journey_to_su"/>				<rdf:li resource="http://www.semanlink.net/doc/2024/03/benjamin_clavie_sur_x_docume"/>			</rdf:Seq>		</items>	</channel>		<item rdf:about="http://www.semanlink.net/doc/2024/09/engineering_blog_journey_to_su">		<title>Engineering Blog: Journey to superhuman performance on scientific tasks</title>		<link>http://www.semanlink.net/doc/2024/09/engineering_blog_journey_to_su</link>		<description>&gt; TLDR: The decision though to ignore cost and latency led to a very different system than you&apos;ll normally see in this kind of work. It takes minutes to answer questions and uses 100k tokens, but that helps us push past human-level on  benchmarks
&gt;
&gt; - A big finding is that the strong effect of chunk size, parsing quality, and embedding choice vanishes with **LLM rerank/context summary** (RCS). It&apos;s slower and more compute, but it makes the systems very robust.
&gt; - Another finding was how important it is to do multiple retrieval strategies. Using LLMs, you can get query expansion easily by having LLMs rewrite the question multiple ways. We also found exploiting sci lit metadata - i.e., citation graph - helped a lot		</description>		<dc:date>2024-09-20T11:18:59Z</dc:date>	</item>	<item rdf:about="http://www.semanlink.net/doc/2024/03/benjamin_clavie_sur_x_docume">		<title>Benjamin Clavié sur X : &quot;Introducing rerankers: a lightweight library to provide a unified way to use various reranking methods&quot;</title>		<link>http://www.semanlink.net/doc/2024/03/benjamin_clavie_sur_x_docume</link>		<dc:date>2024-03-16T10:28:38Z</dc:date>	</item></rdf:RDF>