docs: fix misleading description for LLMContextPrecisionWithoutReference #2239
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
dosubot
bot
added
the
size:XS
anistark
requested changes
Sep 1, 2025
There was a problem hiding this comment.
Thanks for the PR @Rahul2512Chauhan
Please take a look at the comments left.
| @@ -56,7 +56,7 @@ Ragas is a library that provides tools to supercharge the evaluation of Large La | |||
|
|
|||
| <div class="toggle-list"><span class="arrow">→</span> How can I make evaluation results more explainable?</div> | |||
| <div style="display: none;"> | |||
| The best way is to trace and log your evaluation, then inspect the results using LLM traces. You can follow a detailed example of this process <a href="/howtos/customizations/metrics/tracing/">here</a>. | |||
| The best way is to trace and log your evaluation, then inspect the results using LLM traces. You can follow a detailed example of this process <a href="https://docs.ragas.io/en/stable/howtos/customizations/metrics/tracing/">here</a>. | |||
There was a problem hiding this comment.
Please remove this. Not relevant to this PR.
| @@ -17,7 +17,8 @@ The following metrics uses LLM to identify if a retrieved context is relevant or | |||
|
|
|||
| ### Context Precision without reference | |||
|
|
|||
| `LLMContextPrecisionWithoutReference` metric can be used when you have both retrieved contexts and also reference answer associated with a `user_input`. To estimate if a retrieved contexts is relevant or not this method uses the LLM to compare each of the retrieved context or chunk present in `retrieved_contexts` with `response`. | |||
| `LLMContextPrecisionWithoutReference` metric can be used when you have retrieved contexts (`retrieved_contexts`) associated with a `user_input`. This metric does not require a reference answer. To estimate if a retrieved context is relevant, this method uses the LLM to compare each of the retrieved contexts or chunks in `retrieved_contexts` with the response. | |||
There was a problem hiding this comment.
Suggested change
| `LLMContextPrecisionWithoutReference` metric can be used when you have retrieved contexts (`retrieved_contexts`) associated with a `user_input`. This metric does not require a reference answer. To estimate if a retrieved context is relevant, this method uses the LLM to compare each of the retrieved contexts or chunks in `retrieved_contexts` with the response. | |
| `LLMContextPrecisionWithoutReference` metric can be used when you have retrieved contexts (`retrieved_contexts`) associated with a `user_input`. This metric does not require a reference answer. To estimate if a retrieved context is relevant, this method uses the LLM to compare each of the retrieved contexts or chunks in `retrieved_contexts` with the `response`. |
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.
This PR fixes misleading documentation for the LLMContextPrecisionWithoutReference metric.
Old docs suggested that reference context is required.
Updated docs correctly reflect that only retrieved contexts (
retrieved_contexts) and user_input are required, matching the actual implementation.Closes #1981