Latest LoCoMo-retrieval only scores across @10 @20 @200 achievement & its artifact#14
Open
tatavishnurao wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds benchmark artifacts for the
full_topk_rerankLoCoMo retrieval run.The run demonstrates a strong retrieval-only ceiling using SochDB candidate retrieval followed by full top-k cross-encoder reranking over the LoCoMo benchmark set.
This result differs from all the previous runs as the individual categorical scores every category on k=200 hits 90 above including multi-hops score to be @hit = 0.966292 and @recall = 0.916063. This is truly an achievements with the latest PR changes done on the ongoing build that focus on benchmark retrieval sake. This does not misalign with the principles of SochDB.
Benchmark Pipeline
The numbers come from a retrieval-only pipeline:
Key Results
Category Results
K=20
K=100
K=200
Note to onboarding developers that this is purely retrieval only scores and truly reproducible by anyone on the build verison: 2.0.12