Radfact silently assumes that a comparison is not entailed if LLM request fails
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 103
- Forks
- 14
- Avg merge
- 6h 13m
- Merged PRs (30d)
- 1
Description
`Run the processor on a single phrase.
If LLM fails to respond, we return a default NOT_ENTAILMENT with no evidence.
If LLM tries to rephrase the input, we log a warning and correct it.
`
Engine should retry with exponential retries and stop if a request cannot be completed. This will ensure all sentences are evaluated instead of assuming NOT_ENTAILMENT
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the processor's single-phrase path and the LLM request failure handling described in the issue. Trace how a failed request currently becomes NOT_ENTAILMENT, then verify that failures are retried with exponential backoff and that processing stops when a request cannot be completed, rather than returning default evidence-free results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100