Describe the bug
if along with topic relevance validator we send some other validator such as lexical slur match or PII remover to the run guardrails endpoint, then if the input text has slur words or some PII, then respectively those validators will replace the specific words with [REDACTED_SLUR] or the pii entity tag such as [PHONE_NUMBER], after the words are detected and tagged, when the fixed input text goes to topic relevance validator, it will fail even if the rest of the context of the input still contained something related to the topic scope only.
Expected behavior
The fixed input text with redacted slur and pii entity tags should not be going to the topic relevance validator, because even if the main context is accurate to the scope, it will fail.
Describe the bug
if along with topic relevance validator we send some other validator such as lexical slur match or PII remover to the run guardrails endpoint, then if the input text has slur words or some PII, then respectively those validators will replace the specific words with [REDACTED_SLUR] or the pii entity tag such as [PHONE_NUMBER], after the words are detected and tagged, when the fixed input text goes to topic relevance validator, it will fail even if the rest of the context of the input still contained something related to the topic scope only.
Expected behavior
The fixed input text with redacted slur and pii entity tags should not be going to the topic relevance validator, because even if the main context is accurate to the scope, it will fail.