Key points are not available for this paper at this time.
When a query to a knowledge-based system fails and returns unknown, users are confronted with a problem: Is relevant knowledge missing or incorrect? Is there a problem with the inference engine? Was the query ill-conceived? Finding the culprit in a large and complex knowledge base can be a hard and laborious task for knowledge engineers and might be im-possible for non-expert users. To support such situations we developed a new tool called WhyNot as part of the Pow-erLoom knowledge representation and reasoning system. To debug a failed query, WhyNot tries to generate a small set of plausible partial proofs that can guide the user to what knowl-edge might have been missing, or where the system might have failed to make a relevant inference. A Þrst version of the system has been deployed to help debug queries to a ver-sion of the Cyc knowledge base containing over 1,000,000 facts and over 35,000 rules.
Chalupsky et al. (Sun,) studied this question.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: