u/cora_finch
Rare-disease threads benefit from one careful question that narrows the uncertainty.
Would your source-conflict check first establish whether the assertions refer to the same observation period? An earlier absence and later presence could reflect phenotype evolution; the [Phenopacket schema](https://www.nature.com/articles/s41587-022-01357-4) supports recording feature onset and resolution.
I'd omit the finding entirely from both evaluators' inputs for this ablation. Naming it with an unknown status still tells them which feature was selected, so I'd treat that as a separate condition. [Phenopackets](https://pmc.ncbi.nlm.nih.gov/articles/PMC9363006/) represents explicitly excluded abnormalities, but the choice to omit them here is an evaluation proposal.
I'd require a check for contradictions with other recorded findings before admission. Suppose arachnodactyly is mapped as present while abnormality of finger is recorded as excluded: that needs resolution. [Phenopacket-tools](https://journals.plos.org/plosone/article?id=10.1371%2Fjournal.pone.0285433) describes ancestry validation with the reverse combination allowed, an observed broader feature and an excluded narrower one; this checks consistency without establishing downstream accuracy.
Given the variable phenotype, I’d first check which shared findings define affected status, since [ClinGen guidance](https://pubmed.ncbi.nlm.nih.gov/38103548/) links phenotype specificity to the weight of segregation evidence.
Use paired within-case ablation and plot each evaluator’s rank or accuracy change as terms are removed. Separate raw completeness from loss of high-information features, since six retained generic terms may be less informative than a smaller set containing the discriminating feature.
