An Epistemological Level Interface For

An Epistemological Level Interface For

An Epistemological Level Interface for CYC Mark Derthick MCC 3500 West Balcones Center Drive Austin, TX 78759 (512)338-3724 [email protected] February, 1990 1 Abstract The eld of AI continues to b e p olarized by arguments b etween Neats, who advo cate a top-down approach b eginning with a clear for- malization of the problem to b e solved and develop broad theories, and the Scrues, who advo cate b ottom-up heuristic programs and more often develop systems of commercial use. Following McCarthy and Hayes's [1969] suggestion for a distinction b etween epistemologi- cal and heuristic levels, wehave added a logic-based interface to the CYC knowledge representation system, whichmakes it lo ok neat. A translator converts b etween epistemological level and heuristic level representations. This uncouples the KB from the underlying heuris- tic reasoning system. If a desired conclusion is not drawn, the blame can b e placed unambiguously on the knowledge enterer if the epis- temological semantics do not justify it, or otherwise on the system implementor. Over the short term, at least, one do es not haveto dep end on the other. As a matter of fact, CYC's implementors have satis ed its knowledge enterers over the long term. This pap er de- scrib es the advantages of making this distinction, the user's view of CYC, the implementor's view, and how the translator keeps them in tune. Contents 1 Intro duction 1 2 TAOverview 3 3 Constraint Language 4 4 \Frame" Language 5 5 TA Implementation 6 5.1 Tell :: ::: :: :: :: :: ::: :: :: :: :: ::: :: :: :: 6 5.1.1 Canonical Form :: ::: :: :: :: :: ::: :: :: :: 7 5.1.2 Sentential Form :: ::: :: :: :: :: ::: :: :: :: 9 5.2 Ask Intensionally : :: :: ::: :: :: :: :: ::: :: :: :: 12 5.3 Justify ::: :: :: :: :: ::: :: :: :: :: ::: :: :: :: 13 5.4 Ask Extensionally : :: :: ::: :: :: :: :: ::: :: :: :: 13 6 Conclusion 14 3 1 Intro duction The CYC Knowledge Base [Lenat and Guha, 1990] houses declarative rep- resentations of common-sense knowledge. Although the fo cus is on axiom- atization, axioms without inference pro cedures are of little use for problem solving. Therefore much e ort has of necessitygoneinto implementation of the supp orting reasoning system, termed the heuristic level [McCarthyand Hayes, 1969]. The motivation for the heuristic level (HL) is pragmatic|it should nd most of the desired conclusions quickly. Consequently,asCYC is applied to new domains, the HL evolves to accommo date the reasoning required. For instance it currently includes sp ecial facilities for increasing the eciency of inheritance, inverse slots, temp oral reasoning, part-whole structures, scripts, and higher-arity predicates. Driven by the need for e- cient execution, the HL's reasoning is suciently ad hoc that it cannot b e assigned a simple declarative semantics. Therefore in 1987 an epistemologi- cal level [McCarthyandHayes, 1969] logic, called the Constraint Language, was de ned that will remain relatively stable, and that has an intelligible semantics. The meaning of KB assertions is interpreted relative to this se- mantics. \Epistemological Level" and \Constraint Language Level" are used interchangeably. Atanygiven time, it is exp ected that the HL will b e incomplete and/or unsound with resp ect to the constraint language semantics. That is, the HL will fail to derive certain valid conclusions, and will derive certain invalid 1 conclusions. Still, the clean separation b etween epistemological and heuris- tic levels divides the problems inherent in the expressiveness/tractability tradeo b etween knowledge enterers, who may for the most part ignore im- plementation quirks, and the HL implementors, who have b een largely suc- cessful in providing the inferences that are actually wanted (see gure 1). This separation has allowed rather drastic mo di cation to the HL with only minimal disruption of work on the KB. For instance, in 1988 the HL used certainty factors, but in 1989 switchedtoa ve-valued default logic. The Constraint Language has had a two-valued logic throughout [Guha, 1990]. Although the epistemological/heuristic distinction was prop osed twenty years ago, and similar prop osals have also b een made [Newell, 1982, Levesque, 1 In non-monotonic reasoning systems unsoundness usually go es hand-in-hand with in- completeness, b ecause if you fail to derive an exceptional fact (Tweety is a p enguin) you will incorrectly derive facts using the assertion it would haveoverridden (Tweety ies). 1 Figure 1:Schematic representation of the relationship b etween the Epistemolog- ical Level and the Heuristic Level. All run-time reasoning takes place at the HL, but the translator can make this transparent, enabling the user to interact with CYC at either level. Currently human users primarily enter knowledge with the Unit Editor (UE) at the Heuristic Level, b ecause the organization of knowledge into frames makes browsing easier. For other programs, and for humans entering complex constraints, the Tell/Ask (TA) interface, at the Epistemological Level, is more appropriate. 2 1984, Dennett, 1978], it has b een used primarily to justify a divide and conquer approach at the level of scho ols of thought, rather than at the level of system mo dules: Neats worry ab out epistemology, and scrues worry ab out heuristics. Few systems have consciously chosen to combine a well- de ned expressive representation language with an incomplete and unsound heuristic inference algorithm. Indeed, at rst sight, a well-de ned semantics that do esn't quite t the system's b ehavior seems p ointless. However for a system attempting to represent all of common sense knowledge, the only alternative is declining to give a semantics indep endent of the program's b ehavior, b ecause no expressively adequate formal language will b e decidable. CYC's b ehavior is close enough to it's sp eci cation that (in Dennett's terms) taking an intentional stance is more pro ductive than taking a design stance. 2 TAOverview Levesque [1984] treats a KB as an abstract data typ e by de ning its b ehavior in terms of two op erations, Tell and Ask. In the same spirit, CYC's Tell/Ask interface, the TA, enables interaction with the system using the constraint language. Sentences are internally translated into the most ecient HL form 2 automatically.Theinterface consists of four functions: Ask Extensionally takes a sentence, set expression, or term and returns the truth value, set, or individual based on the current KB. Alterna- tively,given a formula, it can return a list of bindings for the unb ound variables that result in a true sentence. Ask Intensionally takes a sentence and returns true if a pro of can b e found for the sentence. For ground sentences these two functions b ehave identically,however for quanti ed sentences the result of one do es not necessarily entail anything ab out the result of the other (due to the non-monotonicity of the constraint language). For instance if we ask whether all birds y, and it happ ens that all currently known (to the KB) birds are known to y, Ask Extensionally 2 As brie y describ ed in section 5.4, one of the reasons CYC requires more functions is that there is no explicit introsp ection op erator. 3 will return true. Only if there is an axiom logically equivalent to \all birds y" (not just those individuals that are currently known to b e birds) will Ask 3 Intensionally return true. And if there is such an axiom, but some individual birds are known to b e exceptions, then Ask Extensionally will return false, but Ask Intensionally will return true. Justify Takes the same argumentasAskIntensionally, but returns the pro of tree, rather than just \true," if a pro of is found. Tell adds an axiom to the KB such that the sentence will b e (intensionally) true. Optionally it will create a unit to stand as a rei ed term for the sentence. This unit will have a slot holding the HL representation. So if the latter changes, due to incompatible changes in the co de or availabil- ity of more ecient implementations, the Epistemological Level handle can remain constant. Conceptually there could b e a Tell Extensionally also: Given \all birds y," Tell Extensionally would assert of all cur- rently known birds that they y. This do es not seem to b e very useful, anditrunsinto problems for disjunctions and existentials [Levesque, 1984]. The bulk of this pap er discusses the strategies used byTell to nd the most ecient frame language implementation of a constraint language prop o- sition. The other three functions can b e written easily given the mo dules built for Tell. 3 Constraint Language The constraint language (CL) closely resembles predicate calculus, with the main di erence b eing that quanti ers have explicit domains. That is, in- stead of (8x)(P (x)) we exp ect (8x 2 S )(P (x)). This is written in the CL as (#%ForAll x S (P x)). We use explicit domains (S) for two reasons. First, in common-sense utterances, \every" and \some" are usually used with an explicit or implicit domain. It seems that this re ects that there are few use- ful common-sense generalizations that apply to everything. Second, it makes extensional reasoning mucheasierby drastically cutting down the number 3 Ask Intensionally will not nd pro ofs of more than one step except in one common sp ecial case describ ed in section 5.1.1. 4 of bindings for the variables. Our notation for representing sets includes an unusual notation: (u s) indicates fxj(su x)g. For example (#%Student #%allInstances) = fstudentj(#%al l I nstances #%S tudent studentg repre- sents the set of all students. Of course one could always trivialize S as the universal set|(#%Thing #%allInstances), but in practice we rarely need to.

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    20 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us