Conflict Sources:
-
Contradictory relationships, such as conflicting drug-disease assertions (e.g., “VX-561 TREATS CF” vs. “VX-561 ABANDONED”).
-
Conflicting classification labels arising from different pipelines or entity resolution stages.
-
Sentiment polarity shifts over time within the same entity or assertion context.
Resolution Mechanism:
-
Initial detection is performed at the Step Agent level through pattern recognition and rule-based triggers.
-
Vault adjudicates when possible, applying expert-labeled judgments to resolve ambiguous or contentious cases.
-
If Vault lacks decisive input, contradictions are flagged, labeled with uncertainty meta-tags, and tracked indefinitely until a decisive trigger (event, annotation, or signal) intervenes.
-
Keymaker continuously monitors contradiction density by topic and prioritizes unresolved contradictions in Q&A selection routines (see Selection Logic Doc).
Confidence Weights Adjustment:
-
Contradicted data receives a weighted confidence decay of -0.15 per contradiction instance to reflect deteriorating trust.
-
If the contradiction remains unresolved for more than two complete cycles, an additional decay layer is applied to emphasize deprecation.
-
Additional meta-layer for contradiction tracking to differentiate between data-originated, temporal, and intentional contradictions. This enables fine-grained decay logic and conflict categorization, improving long-term resolution accuracy.