# Reflexive, Symmetric and Transitive Relations in Prolog

## A Note About Storing Data

Typically when we store some relationship in Prolog the relationship is the functor:

```
temperature(sun, hot).
colour(sun, yellow).
```

But when we need to reason about the relationship we need to reify it (turn it into a thing). This has the happy side-effect of working nicely with the Prolog execution model and prevents infinite loops too. To reify the above examples we could store them in a number of ways:

```
triple(sun, temperature, hot).
triple(sun, colour, yellow).
frame_with_pairs(sun, [temperature-hot, colour-yellow]).
frame_with_dict(sun, slots{temperature: hot, colour: yellow}).
```

For this post we'll use triples so that we don't need any intermediary predicates to read our facts.

## Reflexive

`∀x∈X:xRx.`

For all x in a set X, x is R related to itself, then R is a reflexive property.

The typical example is "for all numbers in the set of real numbers, each number is equal to itself", so "equal" is a reflexive property. A slightly more unusual example is from mereology (the study of the part-hood relation), where everything is considered to be part of itself, let's use that one for our example.

?-

If we've been successful you should see that a car has itself as a part. Personally you may or may not find this odd, but this is a foundation axiom of a whole calculus of mereology where the `hasProperPart`

relation is not reflexive.

## Symmetric

`∀a,b∈X (aRb⇔bRa).`

For all a and b in a set X, a is R related to b implies and is implied by b is R related to a.

A symmetric relationship is one that if it holds in one direction, also holds in the other. The typical examples here are from the family domain with the relations "sibling" and "married". We'll use a similar example of neighbour.

?-

## Transitive

`∀a,b,c∈X: (aRb ∧ bRc) ⇒ aRc.`

If a R related to b and b R related to c then a R related to c.

A transitive relation is best explained through example. Considering the cars previously, hasPart is also transitive, so if the car has a part that is the engine, and the engine has a part that is the battery, then the car has a part that is the battery: `car hasPart engine ∧ engine hasPart battery ⇒ car hasPart battery.`

In Prolog you'll typically first encounter this kind of relationship when trying to write an ancestor predicate for a family tree. We'll take a look at an example using nested locations.

?-

The query should return true first, indicating that Piccadilly is in the UK, followed by false indicating that no more solutions could be found. You can change the query to include a variable to find all the places located within or without the other.

## Using A Generic Query Predicate

To take advantage of the reification of the relation and to save us from writing a lot of code, we can describe the properties of relations and use a generic query predicate.

?-

## Conclusion

Hopefully this will give you a bit of a head-start next time you're needing to encode these properties of relations into your knowledge base. By far the best option is to reify your relations and use a generic query predicate, this will save you lots of development time, especially when writing unit tests. Recommended next step is to run the generic example locally so you can view it with `trace`

or `gtrace`

if you've got SWI-Prolog.