Top Banner
CS 561, Session 16-18 1 Inference in First-Order Logic Proofs Unification Generalized modus ponens Forward and backward chaining Completeness Resolution Logic programming
95

Inference in First-Order Logic

Jan 03, 2016

Download

Documents

lance-bruce

Inference in First-Order Logic. Proofs Unification Generalized modus ponens Forward and backward chaining Completeness Resolution Logic programming. Inference in First-Order Logic. Proofs – extend propositional logic inference to deal with quantifiers Unification - PowerPoint PPT Presentation
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Inference in First-Order Logic

CS 561, Session 16-18 1

Inference in First-Order Logic

• Proofs

• Unification• Generalized modus ponens• Forward and backward chaining

• Completeness

• Resolution

• Logic programming

Page 2: Inference in First-Order Logic

CS 561, Session 16-18 2

Inference in First-Order Logic

• Proofs – extend propositional logic inference to deal with quantifiers

• Unification• Generalized modus ponens• Forward and backward chaining – inference rules and reasoning

program• Completeness – Gödel’s theorem: for FOL, any sentence

entailed byanother set of sentences can be proved from that set

• Resolution – inference procedure that is complete for any set ofsentences

• Logic programming

Page 3: Inference in First-Order Logic

CS 561, Session 16-18 3

Logic as a representation of the World

FactsWorld Factfollows

Refers to (Semantics)

Representation: Sentences Sentenceentails

Page 4: Inference in First-Order Logic

CS 561, Session 16-18 4

Desirable Properties of Inference Procedures

entail

Follows – from-1

derivation

Facts Fact

Sentences Sentence

Page 5: Inference in First-Order Logic

CS 561, Session 16-18 5

Remember:propositionallogic

Page 6: Inference in First-Order Logic

CS 561, Session 16-18 6

Reminder

• Ground term: A term that does not contain a variable.• A constant symbol• A function applies to some ground term

• {x/a}: substitution/binding list

Page 7: Inference in First-Order Logic

CS 561, Session 16-18 7

Proofs

Page 8: Inference in First-Order Logic

CS 561, Session 16-18 8

Proofs

The three new inference rules for FOL (compared to propositional logic) are:

• Universal Elimination (UE):for any sentence , variable x and ground term ,

x {x/}

• Existential Elimination (EE):for any sentence , variable x and constant symbol k not in KB,

x {x/k}

• Existential Introduction (EI):for any sentence , variable x not in and ground term g in ,

x {g/x}

Page 9: Inference in First-Order Logic

CS 561, Session 16-18 9

Proofs

The three new inference rules for FOL (compared to propositional logic) are:

• Universal Elimination (UE):for any sentence , variable x and ground term ,

x e.g., from x Likes(x, Candy) and {x/Joe} {x/} we can infer Likes(Joe, Candy)

• Existential Elimination (EE):for any sentence , variable x and constant symbol k not in KB,

x e.g., from x Kill(x, Victim) we can infer{x/k} Kill(Murderer, Victim), if Murderer new

symbol

• Existential Introduction (EI):for any sentence , variable x not in and ground term g in ,

e.g., from Likes(Joe, Candy) we can inferx {g/x} x Likes(x, Candy)

Page 10: Inference in First-Order Logic

CS 561, Session 16-18 10

Example Proof

Page 11: Inference in First-Order Logic

CS 561, Session 16-18 11

Example Proof

Page 12: Inference in First-Order Logic

CS 561, Session 16-18 12

Example Proof

Page 13: Inference in First-Order Logic

CS 561, Session 16-18 13

Example Proof

4 & 5

Page 14: Inference in First-Order Logic

CS 561, Session 16-18 14

Search with primitive example rules

Page 15: Inference in First-Order Logic

CS 561, Session 16-18 15

Unification

Goal of unification: finding σ

Page 16: Inference in First-Order Logic

CS 561, Session 16-18 16

Unification

{y/John, x/OJ}

Page 17: Inference in First-Order Logic

CS 561, Session 16-18 17

Extra example for unification

P Q σ

Student(x) Student(Bob) {x/Bob}

Sells(Bob, x) Sells(x, coke) {x/coke, x/Bob}Is it correct?

Page 18: Inference in First-Order Logic

CS 561, Session 16-18 18

Extra example for unification

P Q σ

Student(x) Student(Bob) {x/Bob}

Sells(Bob, x) Sells(y, coke) {x/coke, y/Bob}

Page 19: Inference in First-Order Logic

CS 561, Session 16-18 19

More Unification Examples

1 – unify(P(a,X), P(a,b)) σ = {X/b}

2 – unify(P(a,X), P(Y,b)) σ = {Y/a, X/b}

3 – unify(P(a,X), P(Y,f(a)) σ = {Y/a, X/f(a)}

4 – unify(P(a,X), P(X,b)) σ = failure

Note: If P(a,X) and P(X,b) are independent, then we can replace X with Y and get the unification to work.

VARIABLE term

Page 20: Inference in First-Order Logic

CS 561, Session 16-18 20

Generalized Modus Ponens (GMP)

Page 21: Inference in First-Order Logic

CS 561, Session 16-18 21

Soundness of GMP

Page 22: Inference in First-Order Logic

CS 561, Session 16-18 22

Properties of GMP

• Why is GMP and efficient inference rule?

- It takes bigger steps, combining several small inferences into one

- It takes sensible steps: uses eliminations that are guaranteedto help (rather than random UEs)

- It uses a precompilation step which converts the KB to canonical

form (Horn sentences)

Remember: sentence in Horn from is a conjunction of Horn clauses(clauses with at most one positive literal), e.g.,(A B) (B C D), that is (B A) ((C D) B)

Page 23: Inference in First-Order Logic

CS 561, Session 16-18 23

Horn form

• We convert sentences to Horn form as they are entered into the KB

• Using Existential Elimination and And Elimination

• e.g., x Owns(Nono, x) Missile(x) becomes

Owns(Nono, M)Missile(M)

(with M a new symbol that was not already in the KB)

Page 24: Inference in First-Order Logic

CS 561, Session 16-18 24

Forward chaining

Page 25: Inference in First-Order Logic

CS 561, Session 16-18 25

Forward chaining example

Page 26: Inference in First-Order Logic

CS 561, Session 16-18 26

Example: Forward Chaining

Current available rules• A ^ C => E• D ^ C => F• B ^ E => F• B => C• F => G

Page 27: Inference in First-Order Logic

CS 561, Session 16-18 27

Example: Forward Chaining

Current available rules• A ^ C => E (1)• D ^ C => F (2)• B ^ E => F (3)• B => C (4)• F => G (5)

Percept 1. A (is true)Percept 2. B (is true)

then, from (4), C is true, then the premises of (1) will be satisfied, resulting to make E true, then the premises of (3) are going to be satisfied, thus F is true, and finally from (5) G is true.

Page 28: Inference in First-Order Logic

CS 561, Session 16-18 28

Backward chaining

Page 29: Inference in First-Order Logic

CS 561, Session 16-18 29

Backward chaining example

Page 30: Inference in First-Order Logic

CS 561, Session 16-18 30

A simple example

• B^C=> G• A^G=> I• D^G=>J• E=> C• D^C=>K• F=>C

• Q: I?

Page 31: Inference in First-Order Logic

CS 561, Session 16-18 31

A simple example

• B^C=> G• A^G=> I• D^G=>J• E=> C• D^C=>K• F=>C

• Q: I?

1. A^G2. A?

1. USER

3. G?1. B^C

1. USER2. E v F

Page 32: Inference in First-Order Logic

CS 561, Session 16-18 32

Another Example (from Konelsky)

• Nintendo example.• Nintendo says it is Criminal for a programmer to provide

emulators to people. My friends don’t have a Nintendo 64, but they use software that runs N64 games on their PC, which is written by Reality Man, who is a programmer.

Page 33: Inference in First-Order Logic

CS 561, Session 16-18 33

Forward Chaining

• The knowledge base initially contains:

• Programmer(x) Emulator(y) People(z) Provide(x,z,y) Criminal(x)

• Use(friends, x) Runs(x, N64 games)

Provide(Reality Man, friends, x)

• Software(x) Runs(x, N64 games) Emulator(x)

Page 34: Inference in First-Order Logic

CS 561, Session 16-18 34

Forward Chaining

• And we are going to add a number of additional facts, and forward-chain as we proceed to add them. These facts will be (each one added in turn, in the following slides):

• Programmer(Reality Man)

• People(friends)

• Software(U64)

• Use(friends, U64)

• Runs(U64, N64 games)

Page 35: Inference in First-Order Logic

CS 561, Session 16-18 35

Forward Chaining

Programmer(x) Emulator(y) People(z) Provide(x,z,y) Criminal(x)(1)

Use(friends, x) Runs(x, N64 games) Provide(Reality Man, friends, x) (2)

Software(x) Runs(x, N64 games) Emulator(x) (3)

Now we add atomic sentences to the KB sequentially, and call on the forward-chaining procedure:

• FORWARD-CHAIN(KB, Programmer(Reality Man))

Page 36: Inference in First-Order Logic

CS 561, Session 16-18 36

Forward Chaining

Programmer(x) Emulator(y) People(z) Provide(x,z,y) Criminal(x)(1)

Use(friends, x) Runs(x, N64 games) Provide(Reality Man, friends, x)(2)

Software(x) Runs(x, N64 games) Emulator(x) (3)

Programmer(Reality Man) (4)

• This new premise unifies with (1) with

subst({x/Reality Man}, Programmer(x))

but not all the premises of (1) are yet known, so nothing further happens.

Page 37: Inference in First-Order Logic

CS 561, Session 16-18 37

Forward Chaining

Programmer(x) Emulator(y) People(z) Provide(x,z,y) Criminal(x)(1)

Use(friends, x) Runs(x, N64 games) Provide(Reality Man, friends, x) (2)

Software(x) Runs(x, N64 games) Emulator(x) (3)

Programmer(Reality Man) (4)

• Continue adding atomic sentences:• FORWARD-CHAIN(KB, People(friends))

Page 38: Inference in First-Order Logic

CS 561, Session 16-18 38

Forward Chaining

Programmer(x) Emulator(y) People(z) Provide(x,z,y) Criminal(x) (1)

Use(friends, x) Runs(x, N64 games) Provide(Reality Man, friends, x) (2)

Software(x) Runs(x, N64 games) Emulator(x) (3)

Programmer(Reality Man) (4)

People(friends) (5)

• This also unifies with (1) with subst({z/friends}, People(z)) but other premises are still missing.

Page 39: Inference in First-Order Logic

CS 561, Session 16-18 39

Forward Chaining

Programmer(x) Emulator(y) People(z) Provide(x,z,y) Criminal(x)(1)

Use(friends, x) Runs(x, N64 games) Provide(Reality Man, friends, x)(2)

Software(x) Runs(x, N64 games) Emulator(x) (3) Programmer(Reality Man) (4)

People(friends) (5)

• Add:• FORWARD-CHAIN(KB, Software(U64))

Page 40: Inference in First-Order Logic

CS 561, Session 16-18 40

Forward Chaining

Programmer(x) Emulator(y) People(z) Provide(x,z,y) Criminal(x)(1)

Use(friends, x) Runs(x, N64 games) Provide(Reality Man, friends, x)(2)

Software(x) Runs(x, N64 games) Emulator(x) (3)

Programmer(Reality Man) (4)People(friends) (5)

Software(U64) (6)

• This new premise unifies with (3) but the other premise is not yet known.

Page 41: Inference in First-Order Logic

CS 561, Session 16-18 41

Forward Chaining

Programmer(x) Emulator(y) People(z) Provide(x,z,y) Criminal(x)(1)

Use(friends, x) Runs(x, N64 games) Provide(Reality Man, friends, x)(2)

Software(x) Runs(x, N64 games) Emulator(x) (3)

Programmer(Reality Man) (4)People(friends) (5)

Software(U64) (6)

• Add:• FORWARD-CHAIN(KB, Use(friends, U64))

Page 42: Inference in First-Order Logic

CS 561, Session 16-18 42

Forward Chaining

Programmer(x) Emulator(y) People(z) Provide(x,z,y) Criminal(x)(1)

Use(friends, x) Runs(x, N64 games) Provide(Reality Man, friends, x)(2)

Software(x) Runs(x, N64 games) Emulator(x)(3)

Programmer(Reality Man) (4)People(friends) (5)

Software(U64) (6)

Use(friends, U64) (7)

• This premise unifies with (2) but one still lacks.

Page 43: Inference in First-Order Logic

CS 561, Session 16-18 43

Forward Chaining

Programmer(x) Emulator(y) People(z) Provide(x,z,y) Criminal(x) (1)

Use(friends, x) Runs(x, N64 games) Provide(Reality Man, friends, x) (2)

Software(x) Runs(x, N64 games) Emulator(x) (3)

Programmer(Reality Man) (4)People(friends) (5)

Software(U64) (6)

Use(friends, U64) (7)

• Add:• FORWARD-CHAIN(Runs(U64, N64 games))

Page 44: Inference in First-Order Logic

CS 561, Session 16-18 44

Forward Chaining

Programmer(x) Emulator(y) People(z) Provide(x,z,y) Criminal(x)(1)

Use(friends, x) Runs(x, N64 games) Provide(Reality Man, friends, x)(2)

Software(x) Runs(x, N64 games) Emulator(x)(3)

Programmer(Reality Man) (4)People(friends) (5)

Software(U64) (6)Use(friends, U64) (7)

Runs(U64, N64 games) (8)

• This new premise unifies with (2) and (3).

Page 45: Inference in First-Order Logic

CS 561, Session 16-18 45

Forward Chaining

Programmer(x) Emulator(y) People(z) Provide(x,z,y) Criminal(x)(1)

Use(friends, x) Runs(x, N64 games) Provide(Reality Man, friends, x)(2)

Software(x) Runs(x, N64 games) Emulator(x)(3)

Programmer(Reality Man) (4)People(friends) (5)

Software(U64) (6)Use(friends, U64) (7)

Runs(U64, N64 games) (8)

• Premises (6), (7) and (8) satisfy the implications fully.

Page 46: Inference in First-Order Logic

CS 561, Session 16-18 46

Forward Chaining

Programmer(x) Emulator(y) People(z) Provide(x,z,y) Criminal(x) (1)

Use(friends, x) Runs(x, N64 games) Provide(Reality Man, friends, x) (2)

Software(x) Runs(x, N64 games) Emulator(x) (3)

Programmer(Reality Man) (4)People(friends) (5)

Software(U64) (6)Use(friends, U64) (7)

Runs(U64, N64 games) (8)

• So we can infer the consequents, which are now added to the knowledge base (this is done in two separate steps).

Page 47: Inference in First-Order Logic

CS 561, Session 16-18 47

Forward Chaining

Programmer(x) Emulator(y) People(z) Provide(x,z,y) Criminal(x) (1)

Use(friends, x) Runs(x, N64 games) Provide(Reality Man, friends, x) (2)

Software(x) Runs(x, N64 games) Emulator(x) (3)

Programmer(Reality Man) (4)People(friends) (5)

Software(U64) (6)Use(friends, U64) (7)

Runs(U64, N64 games) (8)Provide(Reality Man, friends, U64) (9)

Emulator(U64) (10)

• Addition of these new facts triggers further forward chaining.

Page 48: Inference in First-Order Logic

CS 561, Session 16-18 48

Forward Chaining

Programmer(x) Emulator(y) People(z) Provide(x,z,y) Criminal(x) (1)

Use(friends, x) Runs(x, N64 games) Provide(Reality Man, friends, x) (2)

Software(x) Runs(x, N64 games) Emulator(x) (3)

Programmer(Reality Man) (4)

People(friends) (5)

Software(U64) (6)

Use(friends, U64) (7)

Runs(U64, N64 games) (8)Provide(Reality Man, friends, U64) (9)

Emulator(U64) (10)

Criminal(Reality Man) (11)

• Which results in the final conclusion: Criminal(Reality Man)

Page 49: Inference in First-Order Logic

CS 561, Session 16-18 49

Forward Chaining

• Forward Chaining acts like a breadth-first search at the top level, with depth-first sub-searches.

• Since the search space spans the entire KB, a large KB must be organized in an intelligent manner in order to enable efficient searches in reasonable time.

Page 50: Inference in First-Order Logic

CS 561, Session 16-18 50

Backward Chaining

• Current knowledge:• hurts(x, head)

• What implications can lead to this fact?• kicked(x, head)• fell_on(x, head)• brain_tumor(x)• hangover(x)

• What facts do we need in order to prove these?

Page 51: Inference in First-Order Logic

CS 561, Session 16-18 51

Backward Chaining

• The algorithm (available in detail in Fig. 9.2 on page 275 of the text):• a knowledge base KB

• a desired conclusion c or question q

• finds all sentences that are answers to q in KB or proves c• if q is directly provable by premises in KB, infer q and

remember how q was inferred (building a list of answers).

• find all implications that have q as a consequent.

• for each of these implications, find out whether all of its premises are now in the KB, in which case infer the consequent and add it to the KB, remembering how it was inferred. If necessary, attempt to prove the implication also via backward chaining

• premises that are conjuncts are processed one conjunct at a time

Page 52: Inference in First-Order Logic

CS 561, Session 16-18 52

Backward Chaining

• Question: Has Reality Man done anything criminal?

• Criminal(Reality Man)

• Possible answers:

• Steal(x, y) Criminal(x)

• Kill(x, y) Criminal(x)

• Grow(x, y) Illegal(y) Criminal(x)

• HaveSillyName(x) Criminal(x)

• Programmer(x) Emulator(y) People(z) Provide(x,z,y) Criminal(x)

Page 53: Inference in First-Order Logic

CS 561, Session 16-18 53

Backward Chaining

• Question: Has Reality Man done anything criminal?

Criminal(x)

Page 54: Inference in First-Order Logic

CS 561, Session 16-18 54

Backward Chaining

• Question: Has Reality Man done anything criminal?

• We will use the same knowledge as in our forward-chaining version of this example:

Programmer(x) Emulator(y) People(z) Provide(x,z,y) Criminal(x)

Use(friends, x) Runs(x, N64 games) Provide(Reality Man, friends, x)

Software(x) Runs(x, N64 games) Emulator(x)

Programmer(Reality Man)

People(friends)

Software(U64)

Use(friends, U64)

Runs(U64, N64 games)

Page 55: Inference in First-Order Logic

CS 561, Session 16-18 55

Backward Chaining

• Question: Has Reality Man done anything criminal?

• Issue here: what would it take for someone to be a criminal?

Criminal(x)

Steal(x,y)

Page 56: Inference in First-Order Logic

CS 561, Session 16-18 56

Backward Chaining

• Question: Has Reality Man done anything criminal?

FAIL

Criminal(x)

Steal(x,y)

Page 57: Inference in First-Order Logic

CS 561, Session 16-18 57

Backward Chaining

• Question: Has Reality Man done anything criminal?

FAIL

Criminal(x)

Kill(x,y)Steal(x,y)

Page 58: Inference in First-Order Logic

CS 561, Session 16-18 58

Backward Chaining

• Question: Has Reality Man done anything criminal?

FAIL FAIL

Criminal(x)

Kill(x,y)Steal(x,y)

Page 59: Inference in First-Order Logic

CS 561, Session 16-18 59

Backward Chaining

• Question: Has Reality Man done anything criminal?

FAIL FAIL

Criminal(x)

Kill(x,y)Steal(x,y) grows(x,y) Illegal(y)

Page 60: Inference in First-Order Logic

CS 561, Session 16-18 60

Backward Chaining

• Question: Has Reality Man done anything criminal?

FAIL FAIL FAIL FAIL

Criminal(x)

Kill(x,y)Steal(x,y) grows(x,y) Illegal(y)

Page 61: Inference in First-Order Logic

CS 561, Session 16-18 61

Backward Chaining

• Question: Has Reality Man done anything criminal?

FAIL FAIL FAIL FAIL

• Backward Chaining is a depth-first search: in any knowledge base of realistic size, many search paths will result in failure.

Criminal(x)

Kill(x,y)Steal(x,y) grows(x,y) Illegal(y)

Page 62: Inference in First-Order Logic

CS 561, Session 16-18 62

Backward Chaining

• Question: Has Reality Man done anything criminal?

Criminal(Reality Man)

Page 63: Inference in First-Order Logic

CS 561, Session 16-18 63

Backward Chaining

• Question: Has Reality Man done anything criminal?

Yes, {x/Reality Man}

Programmer(x)

Criminal(Reality Man)

Page 64: Inference in First-Order Logic

CS 561, Session 16-18 64

Backward Chaining

• Question: Has Reality Man done anything criminal?

Yes, {x/Reality Man} Yes, {z/friends}

People(Z)Programmer(x)

Criminal(Reality Man)

Page 65: Inference in First-Order Logic

CS 561, Session 16-18 65

Backward Chaining

• Question: Has Reality Man done anything criminal?

Yes, {x/Reality Man} Yes, {z/friends}

People(Z)Programmer(x) Emulator(y)

Criminal(Reality Man)

Page 66: Inference in First-Order Logic

CS 561, Session 16-18 66

Backward Chaining

• Question: Has Reality Man done anything criminal?

Yes, {x/Reality Man} Yes, {z/friends}

Yes, {y/U64}

People(Z)Programmer(x) Emulator(y)

Software(U64)

Criminal(Reality Man)

Page 67: Inference in First-Order Logic

CS 561, Session 16-18 67

Backward Chaining

• Question: Has Reality Man done anything criminal?

Yes, {x/Reality Man} Yes, {z/friends}

Yes, {y/U64} yes, {}

People(Z)Programmer(x) Emulator(y)

Software(U64)

Runs(U64, N64 games)

Criminal(Reality Man)

Page 68: Inference in First-Order Logic

CS 561, Session 16-18 68

Backward Chaining

• Question: Has Reality Man done anything criminal?

Yes, {x/Reality Man} Yes, {z/friends}

Yes, {y/U64} yes, {}

People(Z)Programmer(x) Emulator(y)

Software(U64)

Runs(U64, N64 games)

Provide(reality man,

U64,friends)

Criminal(Reality Man)

Page 69: Inference in First-Order Logic

CS 561, Session 16-18 69

Backward Chaining

• Question: Has Reality Man done anything criminal?

Yes, {x/Reality Man} Yes, {z/friends}

Yes, {y/U64}

yes, {}

People(Z)Programmer(x) Emulator(y)

Software(U64)

Runs(U64, N64 games)

Provide(reality man,

U64,friends)

Use(friends, U64)

Criminal(Reality Man)

Page 70: Inference in First-Order Logic

CS 561, Session 16-18 70

Backward Chaining

• Backward Chaining benefits from the fact that it is directed toward proving one statement or answering one question.

• In a focused, specific knowledge base, this greatly decreases the amount of superfluous work that needs to be done in searches.

• However, in broad knowledge bases with extensive information and numerous implications, many search paths may be irrelevant to the desired conclusion.

• Unlike forward chaining, where all possible inferences are made, a strictly backward chaining system makes inferences only when called upon to answer a query.

Page 71: Inference in First-Order Logic

CS 561, Session 16-18 71

Completeness

• As explained earlier, Generalized Modus Ponens requires sentences to be in Horn form:• atomic, or

• an implication with a conjunction of atomic sentences as the antecedent and an atom as the consequent.

• However, some sentences cannot be expressed in Horn form.• e.g.: x bored_of_this_lecture (x)

• Cannot be expressed in Horn form due to presence of negation.

Page 72: Inference in First-Order Logic

CS 561, Session 16-18 72

Completeness

• A significant problem since Modus Ponens cannot operate on such a sentence, and thus cannot use it in inference.

• Knowledge exists but cannot be used.

• Thus inference using Modus Ponens is incomplete.

Page 73: Inference in First-Order Logic

CS 561, Session 16-18 73

Completeness

• However, Kurt Gödel in 1930-31 developed the completeness theorem, which shows that it is possible to find complete inference rules.

• The theorem states:• any sentence entailed by a set of sentences can be

proven from that set.

=> Resolution Algorithm which is a complete inference method.

Page 74: Inference in First-Order Logic

CS 561, Session 16-18 74

Completeness

• The completeness theorem says that a sentence can be proved if it is entailed by another set of sentences.

• This is a big deal, since arbitrarily deeply nested functions combined with universal quantification make a potentially infinite search space.

• But entailment in first-order logic is only semi-decidable, meaning that if a sentence is not entailed by another set of sentences, it cannot necessarily be proven.

Page 75: Inference in First-Order Logic

CS 561, Session 16-18 75

Completeness in FOL

Page 76: Inference in First-Order Logic

CS 561, Session 16-18 76

Historical note

Page 77: Inference in First-Order Logic

CS 561, Session 16-18 77

Kinship Example

KB:

(1) father (art, jon) (2) father (bob, kim) (3) father (X, Y) parent (X, Y)

Goal: parent (art, jon)?

Page 78: Inference in First-Order Logic

CS 561, Session 16-18 78

Refutation Proof/Graph

¬parent(art,jon) ¬ father(X, Y) \/ parent(X, Y) \ /

¬ father (art, jon) father (art, jon) \ / []

Page 79: Inference in First-Order Logic

CS 561, Session 16-18 79

Resolution

Page 80: Inference in First-Order Logic

CS 561, Session 16-18 80

Resolution inference rule

Page 81: Inference in First-Order Logic

CS 561, Session 16-18 81

Remember: normal forms

“sum of products of simple variables ornegated simple variables”

“product of sums of simple variables ornegated simple variables”

Page 82: Inference in First-Order Logic

CS 561, Session 16-18 82

Conjunctive normal form

Page 83: Inference in First-Order Logic

CS 561, Session 16-18 83

Skolemization

Page 84: Inference in First-Order Logic

CS 561, Session 16-18 84

Examples: Converting FOL sentences to clause form…

Convert the sentence

1. (x)(P(x) => ((y)(P(y) => P(f(x,y))) ^ ¬(y)(Q(x,y) => P(y))))

(like A => B ^ C)

2. Eliminate => (x)(¬P(x) ((y)(¬P(y) P(f(x,y))) ^ ¬(y)(¬Q(x,y) P(y))))

3. Reduce scope of negation(x)(¬P(x) ((y)(¬P(y) P(f(x,y))) ^ (y)(Q(x,y) ^ ¬P(y))))

4. Standardize variables(x)(¬P(x) ((y)(¬P(y) P(f(x,y))) ^ (z)(Q(x,z) ^ ¬P(z))))

Page 85: Inference in First-Order Logic

CS 561, Session 16-18 85

Examples: Converting FOL sentences to clause form…

5. Eliminate existential quantification(x)(¬P(x) ((y)(¬P(y) P(f(x,y))) ^ (Q(x,g(x)) ^

¬P(g(x)))))

6. Drop universal quantification symbols(¬P(x) ((¬P(y) P(f(x,y))) ^ (Q(x,g(x)) ^

¬P(g(x)))))

7. Convert to conjunction of disjunctions(¬P(x) ¬P(y) P(f(x,y))) ^ (¬P(x) Q(x,g(x)))

^(¬P(x) ¬P(g(x)))

Page 86: Inference in First-Order Logic

CS 561, Session 16-18 86

Examples: Converting FOL sentences to clause form…

8. Create separate clauses¬P(x) ¬P(y) P(f(x,y)) ¬P(x) Q(x,g(x)) ¬P(x) ¬P(g(x))

9. Standardize variables¬P(x) ¬P(y) P(f(x,y)) ¬P(z) Q(z,g(z)) ¬P(w) ¬P(g(w))

Page 87: Inference in First-Order Logic

CS 561, Session 16-18 87

Resolution proof

Page 88: Inference in First-Order Logic

CS 561, Session 16-18 88

Resolution proof

Page 89: Inference in First-Order Logic

CS 561, Session 16-18 89

Inference in First-Order Logic

• Canonical forms for resolution

Conjunctive Normal Form (CNF) Implicative Normal Form (INF)

)()( wQwP )()( xRxP )()( ySyQ )()( zSzR

)()( wQwP )()( xRxPTrue

)()( ySyQ )()( zSzR

Page 90: Inference in First-Order Logic

CS 561, Session 16-18 90

Reference in First-Order Logic

• Resolution Proofs In a forward- or backward-chaining algorithm, just as Modus

Ponens.

)()( wQwP )()( ySyQ

)()( wSwP )()( xRxPTrue

)()( xRxSTrue )()( zSzR

)(ASTrue

{y/w}

{w/x}

{x/A,z/A}

Page 91: Inference in First-Order Logic

CS 561, Session 16-18 91

Inference in First-Order Logic

• Refutation

)()( wQwP )()( ySyQ

)()( wSwP )()( xRxPTrue

)()( xRxSTrue )()( zSzR

)(ASTrue

{y/w}

{w/x}

{z/x}

FalseAS )(

FalseTrue

{x/A}

)()( PKBFalsePKB

Page 92: Inference in First-Order Logic

CS 561, Session 16-18 92

Example of Refutation Proof(in conjunctive normal form)

(1) Cats like fish(2) Cats eat everything they

like(3) Josephine is a cat.(4) Prove: Josephine eats

fish.

cat (x) likes (x,fish)cat (y) likes (y,z) eats (y,z)cat (jo) eats (jo,fish)

Page 93: Inference in First-Order Logic

CS 561, Session 16-18 93

Backward ChainingNegation of goal wff: eats(jo, fish)

eats(jo, fish) cat(y) likes(y, z) eats(y, z)

= {y/jo, z/fish}

cat(jo) likes(jo, fish) cat(jo)

=

cat(x) likes(x, fish) likes(jo, fish)

= {x/jo}

cat(jo) cat(jo)

(contradiction)

Page 94: Inference in First-Order Logic

CS 561, Session 16-18 94

Forward chaining

cat (jo) cat (X) likes (X,fish) \ / likes (jo,fish) cat (Y) likes (Y,Z) eats (Y,Z)

\ / cat (jo) eats (jo,fish) cat (jo)

\ /eats (jo,fish) eats (jo,fish)

\ / [] []

Page 95: Inference in First-Order Logic

CS 561, Session 16-18 95

Question:

• When would you use forward chaining? What about backward chaining?

• A: • FC: If expert needs to gather information

before any inferencing• BC: If expert has a hypothetical solution