Enable technical accuracy evaluator for hallucination detection #13
+6
−6
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
- Add evaluator: technical-accuracy field to hallucination-detector prompt - Fix shallow copy bug in TechnicalAccuracyEvaluator that prevented verification results from persisting - Verification results now properly show [supported/unsupported/unverifiable] status with justifications and source URLs
…eb search and LLM.
Contributor
|
@ayo6706, can we have a screenshot of what this looks like? |
Collaborator
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Fixes the technical accuracy evaluator not running on the hallucination detector prompt. Violations now include real-time web verification with [supported/unsupported/unverifiable] status, justifications, and source URLs.