Skip to content

The output is generated, but it is determined to be misaligned with the AWS Responsible AI policy.

0

I am facing this issue while passing the image to extract the content from the AWS Nova Pro model. Even if the page does not contain any vioilating, misleading, or false information, it returns the output as: "The generated text has been blocked by our content filters." I am processing a large volume of complex PDFs, page by page. And then each page from the PDF goes on the process of content extraction. Any suggestions would be appreciated.

1 Answer
0

I understand you're encountering challenges with Amazon Nova's content filters while processing complex PDFs for content extraction. This situation you're describing is known as an RAI (Responsible AI) output deflection error. It occurs when the generated output is deemed to be misaligned with AWS's Responsible AI policy, even if the input itself doesn't appear to contain violating content.

Here are some suggestions to address this issue:

  1. Review your prompts: Examine the prompts you're using for content extraction. Even if the PDF content seems benign, the way you're framing the request to the model might be triggering the content filters. Try to optimize your prompts to reduce the likelihood of generating undesired outcomes.

  2. Break down the content: If you're processing large, complex PDFs, try breaking them down into smaller, more manageable chunks. This might help isolate any problematic sections and reduce the chances of triggering content filters for the entire document.

  3. Implement error handling: Since you're processing a large volume of PDFs, implement robust error handling in your workflow. When you encounter the "The generated text has been blocked by our content filters" message, log it, skip that particular page or section, and continue with the rest of the document.

  4. Human review: For pages that consistently trigger the content filter, consider implementing a human review process. This can help identify patterns in the content that might be causing issues and allow for manual processing of these sections.

  5. Evaluate alternative approaches: If certain types of content or documents consistently trigger the filters, you might need to consider alternative approaches for those specific cases, such as using different AI services or implementing custom processing logic.

  6. Contact AWS Support: If you believe the content filters are being overly restrictive for your use case, consider reaching out to AWS Support. They may be able to provide more specific guidance or investigate if there's an issue with the model's behavior.

Remember, Amazon Nova's outputs are probabilistic, and the service is designed to err on the side of caution when it comes to content moderation. It's important to implement appropriate oversight and testing in your workflow, especially if the extracted content will be used for consequential decisions or surfaced directly to end users.

Lastly, always evaluate the outputs for accuracy and appropriateness for your specific use case, even when they pass the content filters. This is particularly crucial when dealing with complex documents that may contain nuanced or context-dependent information.

Sources
Error handling - Amazon Nova
Responsible use - Amazon Nova

answered 10 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.