ontologies and knowledge-based systemsnlp.chonbuk.ac.kr/ai2018/slides/ch14_all.pdfsemantic web...

Ontologies and Knowledge-based Systems

Is there a flexible way to represent relations?

How can knowledge bases be made to interoperatesemantically?

c©D. Poole and A. Mackworth 2017 Artificial Intelligence, Lecture 14.1, 1 / 12

Choosing Individuals and Relations

How to represent: “Pen #7 is red.”

red(pen7). It’s easy to ask “What’s red?”Can’t ask “what is the color of pen7?”

color(pen7, red). It’s easy to ask “What’s red?”It’s easy to ask “What is the color of pen7?”Can’t ask “What property of pen7 has value red?”

prop(pen7, color , red). It’s easy to ask all these questions.

prop(Individual ,Property ,Value) is the only relation needed:called individual-property-value representationor triple representation


Universality of prop

To represent “a is a parcel”

prop(a, type, parcel), where type is a special property

prop(a, parcel , true), where parcel is a Boolean property


Reification

To represent scheduled(cs422, 2, 1030, cc208). “section 2 ofcourse cs422 is scheduled at 10:30 in room cc208.”

Let b123 name the booking:

prop(b123, course, cs422).

prop(b123, section, 2).

prop(b123, time, 1030).

prop(b123, room, cc208).

We have reified the booking.

Reify means: to make into an individual.

What if we want to add the year?


Semantic Networks / Knowledge Graphs

When you only have one relation, prop, it can be omitted withoutloss of information.Logic:

prop(Individual ,Property ,Value)

triple:

〈Individual ,Property ,Value〉

simple sentence:

Individual Property Value.

graphically:

Obj ValProp


An Example Semantic Network / Knowledge Graph

comp_2347owned_by

craig

room

r107

building comp_sci

deliver_to

mingroom

buildingr117

model

lemon_laptop_10000

brand

lemon_computer

logolemon_disc

color

brown

size

medium

weight

light

packing

cardboard_box


Equivalent Logic Program

prop(comp 2347, owned by , craig).

prop(comp 2347, deliver to,ming).

prop(comp 2347,model , lemon laptop 10000).

prop(comp 2347, brand , lemon computer).

prop(comp 2347, logo, lemon disc).

prop(comp 2347, color , brown).

prop(craig , room, r107).

prop(r107, building , comp sci)....


A Structured Semantic Network / Knowledge Graph

comp_2347owned_by

craig

room

r107

building

comp_sci

deliver_to

mingroom

building

r117

type

logolemon_disccolorbrown

size

mediumweight

light

packing

cardboard_box

subClassOf

subClassOf

computer

lemon_computer

lemon_laptop_10000


Logic of Property

An arc cp−→ v from a class c with a property p to value v means

every individual in the class has value v on property p:

prop(Obj , p, v)←prop(Obj , type, c).

Example:

prop(X ,weight, light)←prop(X , type, lemon laptop 10000).

prop(X , packing , cardboard box)←prop(X , type, computer).


Logic of Property Inheritance

You can do inheritance through the subclass relationship:

prop(X , type,T )←prop(S , subClassOf ,T ) ∧prop(X , type, S).


Multiple Inheritance

An individual is usually a member of more than one class. Forexample, the same person may be a wine expert, a teacher, afootball coach,. . . .

The individual can inherit the properties of all of the classes itis a member of: multiple inheritance.

With default values,what is an individual inherits conflictingdefaults from the different classes? multiple inheritanceproblem.


Choosing Primitive and Derived Properties

Associate an property value with the most general class withthat property value.

Don’t associate contingent properties of a class with the class.For example, if all of current computers just happen to bebrown.


Knowledge Sharing

A conceptualization is a map from the problem domain intothe representation. A conceptualization specifies:

I What sorts of individuals are being modeledI The vocabulary for specifying individuals, relations and

propertiesI The meaning or intention of the vocabulary

If more than one person is building a knowledge base, theymust be able to share the conceptualization.

An ontology is a specification of a conceptualization.An ontology specifies the meanings of the symbols in aninformation system.

c©D. Poole and A. Mackworth 2017 Artificial Intelligence, Lecture 14.2, Page 1 1 / 20

Mapping from a conceptualization to a symbol


Semantic Web

Ontologies are published on the web in machine readable form.

Builders of knowledge bases or web sites adhere to and referto a published ontology:

I a symbol defined by an ontology means the same thing acrossweb sites that obey the ontology.

I if someone wants to refer to something not defined, theypublish an ontology defining the terminology.Others adopt the terminology by referring to the new ontology.In this way, ontologies evolve.

I Separately developed ontologies can have mappings betweenthem published.


Challenges of building ontologies

They can be huge: finding the appropriate terminology for aconcept may be difficult.

How one divides the world can depend on the application.Different ontologies describe the world in different ways.

People can fundamentally disagree about an appropriatestructure.

Different knowledge bases can use different ontologies.

To allow KBs based on different ontologies to inter-operate,there must be mapping between ontologies.

It has to be in user’s interests to use an ontology.

The computer doesn’t understand the meaning of the symbols.The formalism can constrain the meaning, but can’t define it.


Semantic Web Technologies

XML the Extensible Markup Language provides genericsyntax.〈tag . . . /〉 or〈tag . . . 〉 . . . 〈/tag〉.URI a Uniform Resource Identifier is a name of an individual(resource). This name can be shared. Often in the form of aURL to ensure uniqueness.

RDF the Resource Description Framework is a language oftriples

OWL the Web Ontology Language, defines some primitiveproperties that can be used to define terminology. (Doesn’tdefine a syntax).


Main Components of an Ontology

Individuals the things / objects in the world (not usuallyspecified as part of the ontology)

Classes sets of individuals

Properties between individuals and their values


Individuals

Individuals are things in the world that can be named.(Concrete, abstract, concepts, reified).

Unique names assumption (UNA): different names refer todifferent individuals.

The UNA is not an assumption we can universally make:“The Queen”, “Elizabeth Windsor”, etc.

Without the determining equality, we can’t count!

In OWL we can specify:

owl:SameIndividual(i1, i2)

owl:DifferentIndividuals(i1, i3)


Classes

A class is a set of individuals. E.g., house, building,officeBuilding

One class can be a subclass of another

owl:SubClassOf(house, building)

owl:SubClassOf(officeBuilding , building)

The most general class is owl:Thing.

Classes can be declared to be the same or to be disjoint:

owl:EquivalentClasses(house, singleFamilyDwelling)

owl:DisjointClasses(house, officeBuilding)

Different classes are not necessarily disjoint.E.g., a building can be both a commercial building and aresidential building.


Properties

A property is between an individual and a value.

A property has a domain and a range.

rdfs:domain(livesIn, person)

rdfs:range(livesIn, placeOfResidence)

An ObjectProperty is a property whose range is an individual.

A DatatypeProperty is one whose range isn’t an individual,e.g., is a number or string.

There can also be property hierarchies:

owl:subPropertyOf(livesIn, enclosure)

owl:subPropertyOf(principalResidence, livesIn)


Properties











Properties (Cont.)

One property can be inverse of another

owl:InverseObjectProperties(livesIn, hasResident)

Properties can be declared to be transitive, symmetric,functional, or inverse-functional.

(Which of these are only applicable to object properties?)

We can also state the minimum and maximal cardinality of aproperty.

owl:minCardinality(principalResidence, 1)

owl:maxCardinality(principalResidence, 1)


Properties (Cont.)



Properties can be declared to be transitive, symmetric,functional, or inverse-functional.(Which of these are only applicable to object properties?)





Property and Class Restrictions

We can define complex descriptions of classes in terms ofrestrictions of other classes and properties.E.g., A homeowner is a person who owns a house.

homeOwner ⊆ person∩{x : ∃h ∈ house such that x owns h}

owl:subClassOf(homeOwner,person)

owl:subClassOf(homeOwner ,

owl:ObjectSomeValuesFrom(owns, house))


OWL Class Constructors

owl:Thing ≡ all individualsowl:Nothing ≡ no individualsowl:ObjectIntersectionOf(C1, . . . ,Ck) ≡ C1 ∩ · · · ∩ Ck

owl:ObjectUnionOf(C1, . . . ,Ck) ≡ C1 ∪ · · · ∪ Ck

owl:ObjectComplementOf(C ) ≡ Thing \ Cowl:ObjectOneOf(I1, . . . , Ik) ≡ {I1, . . . , Ik}owl:ObjectHasValue(P, I ) ≡ {x : x P I}owl:ObjectAllValuesFrom(P,C ) ≡ {x : x P y → y ∈ C}owl:ObjectSomeValuesFrom(P,C ) ≡

{x : ∃y ∈ C such that x P y}owl:ObjectMinCardinality(n,P,C ) ≡

{x : #{y |xPy and y ∈ C} ≥ n}owl:ObjectMaxCardinality(n,P,C ) ≡

{x : #{y |xPy and y ∈ C} ≤ n}


OWL Predicates

rdf:type(I ,C ) ≡ I ∈ Crdfs:subClassOf(C1,C2) ≡ C1 ⊆ C2

owl:EquivalentClasses(C1,C2) ≡ C1 ≡ C2

owl:DisjointClasses(C1,C2) ≡ C1 ∩ C2 = {}rdfs:domain(P,C ) ≡ if xPy then x ∈ Crdfs:range(P,C ) ≡ if xPy then y ∈ Crdfs:subPropertyOf(P1,P2) ≡ xP1y implies xP2yowl:EquivalentObjectProperties(P1,P2) ≡ xP1y if and only if xP2yowl:DisjointObjectProperties(P1,P2) ≡ xP1y implies not xP2yowl:InverseObjectProperties(P1,P2) ≡ xP1y if and only if yP2xowl:SameIndividual(I1, . . . , In) ≡∀j∀k Ij = Ikowl:DifferentIndividuals(I1, . . . , In) ≡ ∀j∀k j 6= k implies Ij 6= Ikowl:FunctionalObjectProperty(P) ≡ if xPy1 and xPy2 then y1 = y2owl:InverseFunctionalObjectProperty(P) ≡

if x1Py and x2Py then x1 = x2owl:TransitiveObjectProperty(P) ≡ if xPy and yPz then xPzowl:SymmetricObjectProperty ≡ if xPy then yPx


Knowledge Sharing

One ontology typically imports and builds on other ontologies.

OWL provides facilities for version control.

Tools for mapping one ontology to another allowinter-operation of different knowledge bases.

The semantic web promises to allow two pieces of informationto be combined if

I they both adhere to an ontologyI these are the same ontology or there is a mapping between

them.


Example: Apartment Building

An apartment building is a residential building with more than twounits and they are rented.

Declaration(ObjectProperty(:numberOfunits))

FunctionalObjectProperty(:numberOfunits)

ObjectPropertyDomain(:numberOfunits :ResidentialBuilding)

ObjectPropertyRange(:numberOfunits

ObjectOneOf(:two :one :moreThanTwo))

Declaration(Class(:ApartmentBuilding))

EquivalentClasses(:ApartmentBuilding

ObjectIntersectionOf(

:ResidentialBuilding

ObjectHasValue(:numberOfunits :moreThanTwo)

ObjectHasValue(:ownership :rental)))


Aristotelian definitions

Aristotle [350 B.C.] suggested the definition if a class C in termsof:

Genus: the super-class

Differentia: the attributes that make members of the class Cdifferent from other members of the super-class

“If genera are different and co-ordinate, their differentiae arethemselves different in kind. Take as an instance the genus ’animal’and the genus ’knowledge’. ’With feet’, ’two-footed’, ’winged’,’aquatic’, are differentiae of ’animal’; the species of knowledge arenot distinguished by the same differentiae. One species ofknowledge does not differ from another in being ’two-footed’.”

Aristotle, Categories, 350 B.C.


Example: hotel ontology

Define the following:

Room

BathRoom

StandardRoom - what is rented as a room in a hotel

Suite

RoomOnly

Hotel

HasForRent

AllSuitesHotel

NoSuitesHotel

HasSuitesHotel


Top-Level Ontology — Basic Formal Ontology (BFO)

1: if entity continues to exist through time then2: it is a continuant3: if it doesn’t need another entity for its existence then4: it is an independent continuant5: if it has matter as a part then6: it is a material entity7: if it is a single coherent whole then8: it is an object

9: else it is an immaterial entity

10: else it is a dependent continuant11: if it a region in space then12: it is a spatial region13: else if it is a property then14: if it is a property all objects have then15: it is a quality

16: . . . role . . . disposition . . . function . . .

17: else18: it is an occurrent19: if it depends on a continuant then20: if it happens over time then21: it is a process22: else23: it is a process boundary

24: else if it involves space and time then25: it is a spatio-temporal region26: else27: it is a temporal region


Continuants vs Occurrents

A continuant exists in an instance of time and maintains itsidentity through time.

An occurrent has temporal parts.

Continuants participate in occurrents.

a person, a life, a finger, infancy: what is part of what?

a holiday, the end of a lecture, an email, the sending of anemail, the equator, earthquake, a smile, a laugh, the smell ofa flower


Continuants

a pen, a person, Newtonian mechanics, the memory of a pastevent:

objects

a flock of birds, the students in CS422, a card collection:object aggregates

a city, a room, a mouth, the hole of a doughnut: site

the dangerous part of a city, part of Grouse Mountain withthe best view: fiat part of an object.


Continuants

a pen, a person, Newtonian mechanics, the memory of a pastevent: objects





Continuants


a flock of birds, the students in CS422, a card collection:

object aggregates




Continuants






Continuants



a city, a room, a mouth, the hole of a doughnut:

site



Continuants






Continuants




the dangerous part of a city, part of Grouse Mountain withthe best view:

fiat part of an object.


Continuants






Knowledge Engineering

Overview:

Roles of people involved in a knowledge-based system

How representation and reasoning systems interact withhumans.

Knowledge-based interaction and debugging tools

Building representation and reasoning systems

c©D. Poole and A. Mackworth 2016 Artificial Intelligence, Lecture 14.3, Page 1

Knowledge-based system architecture

DomainExpert

KnowledgeEngineer

KnowledgeBase

InferenceEngine

User Interface User


Roles for people in a KBS

Software engineers build the inference engine and userinterface.

Knowledge engineers design, build, and debug the knowledgebase in consultation with domain experts.

Domain experts know about the domain, but nothing aboutparticular cases or how the system works.

Users have problems for the system, know about particularcases, but not about how the system works or the domain.


Users

How can users provide knowledge when

they don’t know the internals of the system

they aren’t experts in the domain

they don’t know what information is relevant

they don’t know the syntax of the system

but they have essential information about the particular caseof interest?


Querying the User

The system can determine what information is relevant andask the user for the particular information.

A top-down derivation can determine what information isrelevant. There are three types of goals:

I Goals for which the user isn’t expected to know the answer, sothe system never asks.

I Goals for which the user should know the answer, and forwhich they have not already provided an answer.

I Goals for which the user has already provided an answer.


Yes/No questions

The simplest form of a question is a ground query.

Ground queries require an answer of “yes” or “no”.

The user is only asked a question ifI the question is askable, andI the user hasn’t previously answered the question.

When the user has answered a question, the answer needs tobe recorded.


Electrical Domain

In the electrical domain:

The designer of a house:I will know how switches and lights are connected by wires,I won’t know if the light switches are up or down.

A new resident in a house:I won’t know how switches and lights are connected by wires,I will know (or can observe) if the light switches are up or down.


Functional Relations

You probably don’t want to ask ?age(fred , 0), ?age(fred , 1),?age(fred , 2), . . .

You probably want to ask for Fred’s age once, and succeed forqueries for that age and fail for other queries.

This exploits the fact that age is a functional relation.

Relation r(X ,Y ) is functional if, for every X there exists aunique Y such that r(X ,Y ) is true.


Getting information from a user

The user may not know the vocabulary that is expected bythe knowledge engineer.

Either:I The system designer provides a menu of items from which the

user has to select the best fit.I The user can provide free-form answers. The system needs a

large dictionary to map the responses into the internal formsexpected by the system.


More General Questions

Example: For the subgoal p(a,X , f (Z )) the user can be asked:

for which X ,Z is p(a,X , f (Z )) true?

Should users be expected to give all instances which are true,or should they give the instances one at a time, with thesystem prompting for new instances?

Example: For which S ,C is enrolled(S ,C ) true?

Psychological issues are important.


Re-asking Questions

For the case when a user provides instances one at a time: Whenshould the system repeat a question or not ask a question?Example: Query Ask? Response

?p(X ) yes p(f (Z ))?p(f (c)) no?p(a) yes yes?p(X ) yes no?p(c) no


When to ask the user

Don’t ask a question that is

an instance of a positive answer that has alreadybeen given oror instance of a query to which the user has repliedno.


Delaying Asking the User

Should the system ask the question as soon as it’sencountered, or should it delay the goal until more variablesare bound?

Example consider query ?p(X ) & q(X ), where p(X ) is askable.

I If p(X ) succeeds for many instances of X and q(X ) succeedsfor few (or no) instances of X it’s better to delay asking p(X )and prove q(X ) first.

I If p(X ) succeeds for few instances of X and q(X ) succeeds formany instances of X , don’t delay.


Multiple Information Sources

Asking the user is just one instance of using multiple informationsources. There are many types of subgoals:

those the system has rules about

those the system has facts about

those that the user should be able to answer

those that a web site may be able to answer (e.g., flightarrival times)

those that a database may be able to answer (e.g., someone’sphone number, or the meaning of a word)

Each information source has its own characteristics.


Assumptions

Some subgoals you don’t know if they are true; they areassumptions or hypotheses.

You want to collect the assumptions needed to prove the goal.

Example: in the electrical domain, ok may be assumable.


Explanation

The system must be able to justify that its answer is correct,particularly when it is giving advice to a human.

The same features can be used for explanation and fordebugging the knowledge base.

There are three main mechanisms:I Ask HOW a goal was derived.I Ask WHYNOT a goal wasn’t derived.I Ask WHY a subgoal is being proved.


How did the system prove a goal?

If g is derived, there must be a rule instance

g ⇐ a1 & . . . & ak .

where each ai is derived.

If the user asks HOW g wasderived, the system can display this rule. The user can then ask

HOW i.

to give the rule that was used to prove ai .

The HOW command moves down the proof tree.


Why Did the System Ask a Question?

It is useful to find out why a question was asked.

Knowing why a question was asked will increase the user’sconfidence that the system is working sensibly.

It helps the knowledge engineer optimize questions asked ofthe user.

An irrelevant question can be a symptom of a deeper problem.

The user may learn something from the system by knowingwhy the system is doing something.


WHY question

When the system asks the user a question g , the user canreply with

WHY

This gives the instance of the rule

h⇐ · · · & g & · · ·

that is being tried to prove h.

When the user asks WHY again, it explains why h was proved.


Debugging Knowledge Bases

There are four types of nonsyntactic errors that can arise inrule-based systems:

An incorrect answer is produced; that is, some atom that isfalse in the intended interpretation was derived.

Some answer wasn’t produced; that is, the proof failed whenit should have succeeded, or some particular true atom wasn’tderived.

The program gets into an infinite loop.

The system asks irrelevant questions.


Debugging Incorrect Answers

An incorrect answer is a derived answer which is false in theintended interpretation.

An incorrect answer means a clause in the KB is false in theintended interpretation.

If g is false in the intended interpretation, there is a proof forg using g ⇐ a1 & . . . & ak . Either:

I Some ai is false: debug it.I All ai are true. This rule is buggy.


Debugging Missing Answers

WHYNOT g . g fails when it should have succeeded.Either:

I There is an atom in a rule that succeeded with the wronganswer, use HOW to debug it.

I There is an atom in a body that failed when it should havesucceeded, debug it using WHYNOT.

I There is a rule missing for g .


Debugging Infinite Loops

There is no automatic way to debug all such errors: haltingproblem.

There are many errors that can be detected:I If a subgoal is identical to an ancestor in the proof tree, the

program is looping.I Define a well-founded ordering that is reduced each time

through a loop.


Implementing Knowledge-based Systems

To build an interpreter for a language, we need to distinguish

Base language the language of the RRS being implemented.

Metalanguage the language used to implement the system.

They could even be the same language!


Implementing the base language

Let’s use the definite clause language as the base language and themetalanguage.

We need to represent the base-level constructs in themetalanguage.

We represent base-level terms, atoms, and bodies asmeta-level terms.

We represent base-level clauses as meta-level facts.

In the non-ground representation base-level variables arerepresented as meta-level variables.


Representing the base level constructs

Base-level atom p(t1, . . . , tn) is represented as the meta-levelterm p(t1, . . . , tn).

Meta-level term oand(e1, e2) denotes the conjunction ofbase-level bodies e1 and e2.

Meta-level constant true denotes the object-level empty body.

The meta-level atom clause(h, b) is true if “h if b” is a clausein the base-level knowledge base.


Example representation

The base-level clauses

connected to(l1,w0).

connected to(w0,w1)← up(s2).

lit(L)← light(L) ∧ ok(L) ∧ live(L).

can be represented as the meta-level facts

clause(connected to(l1,w0), true).

clause(connected to(w0,w1), up(s2)).

clause(lit(L), oand(light(L), oand(ok(L), live(L)))).


Making the representation pretty

Use the infix function symbol “&” rather than oand .I instead of writing oand(e1, e2), you write e1 & e2.

Instead of writing clause(h, b) you can write h⇐ b, where ⇐is an infix meta-level predicate symbol.

I Thus the base-level clause “h← a1 ∧ · · · ∧ an” is representedas the meta-level atom h⇐ a1 & · · · & an.


Example representation

The base-level clauses

connected to(l1,w0).

connected to(w0,w1)← up(s2).

lit(L)← light(L) ∧ ok(L) ∧ live(L).

can be represented as the meta-level facts

connected to(l1,w0)⇐ true.

connected to(w0,w1)⇐ up(s2).

lit(L)⇐ light(L) & ok(L) & live(L).


Vanilla Meta-interpreter

prove(G ) is true when base-level body G is a logical consequenceof the base-level KB.

prove(true).

prove((A & B))←prove(A) ∧prove(B).

prove(H)←(H ⇐ B) ∧prove(B).


Example base-level KB

live(W )⇐connected to(W ,W1) &

live(W1).

live(outside)⇐ true.

connected to(w6,w5)⇐ ok(cb2).

connected to(w5, outside)⇐ true.

ok(cb2)⇐ true.

?prove(live(w6)).


Expanding the base-level

Adding clauses increases what can be proved.

Disjunction Let a; b be the base-level representation for thedisjunction of a and b. Body a; b is true when a is true, or bis true, or both a and b are true.

Built-in predicates You can add built-in predicates such as Nis E that is true if expression E evaluates to number N.


Expanded meta-interpreter

prove(true).

prove((A & B))←prove(A) ∧ prove(B).

prove((A;B))← prove(A).

prove((A;B))← prove(B).

prove((N is E ))←N is E .

prove(H)←(H ⇐ B) ∧ prove(B).


Depth-Bounded Search

Adding conditions reduces what can be proved.

% bprove(G ,D) is true if G can be proved with a proof tree ofdepth less than or equal to number D.

bprove(true,D).

bprove((A & B),D)←bprove(A,D) ∧ bprove(B,D).

bprove(H,D)←D ≥ 0 ∧ D1 is D − 1 ∧(H ⇐ B) ∧ bprove(B,D1).


Ask-the-user meta-interpreter

% aprove(G ) is true if G is a logical consequence of the base-levelKB and yes/no answers provided by the user.

aprove(true).

aprove((A& B))← aprove(A) ∧ aprove(B).

aprove(H)← askable(H) ∧ answered(H, yes).

aprove(H)←askable(H) ∧ unanswered(H) ∧ ask(H,Ans) ∧record(answered(H,Ans)) ∧ Ans = yes.

aprove(H)← (H ⇐ B) ∧ aprove(B).


Meta-interpreter to collect rules for WHY

% wprove(G ,A) is true if G follows from base-level KB, and A is alist of ancestor rules for G .

wprove(true,Anc).

wprove((A& B),Anc)←wprove(A,Anc) ∧wprove(B,Anc).

wprove(H,Anc)←(H ⇐ B) ∧wprove(B, [(H ⇐ B)|Anc]).


Delaying Goals

Some goals, rather than being proved, can be collected in a list.

To delay subgoals with variables, in the hope that subsequentcalls will ground the variables.

To delay assumptions, so that you can collect assumptionsthat are needed to prove a goal.

To create new rules that leave out intermediate steps.

To reduce a set of goals to primitive predicates.


Delaying Meta-interpreter

% dprove(G ,D0,D1) is true if D0 is an ending of list of delayableatoms D1 and KB ∧ (D1 − D0) |= G .

dprove(true,D,D).

dprove((A& B),D1,D3)←dprove(A,D1,D2) ∧ dprove(B,D2,D3).

dprove(G ,D, [G |D])← delay(G ).

dprove(H,D1,D2)←(H ⇐ B) ∧ dprove(B,D1,D2).


Example base-level KB

live(W )⇐connected to(W ,W1) &

live(W1).

live(outside)⇐ true.

connected to(w6,w5)⇐ ok(cb2).

connected to(w5, outside)⇐ ok(outside connection).

delay(ok(X )).

?dprove(live(w6), [ ],D).


Meta-interpreter that builds a proof tree

% hprove(G ,T ) is true if G can be proved from the base-level KB,with proof tree T .

hprove(true, true).

hprove((A& B), (L& R))←hprove(A, L) ∧hprove(B,R).

hprove(H, if (H,T ))←(H ⇐ B) ∧hprove(B,T ).


ontologies and knowledge-based systemsnlp.chonbuk.ac.kr/ai2018/slides/ch14_all.pdfsemantic web...

Documents