Skip to main content

Mutual Exclusive
Mutual Exclusive

When creating concept instances in knowledge maps, you may need to denote two instances as being "mutually exclusive". In Rainbird Studio, you can easily mark this using the "mutually exclusive" switch. This section explains how (and when) to use it. It also gives you two example knowledge maps to explore the switch in use inside Rainbird Studio.

In logic and probability theory, two ‘things’ are referred to as ‘mutually exclusive’ if they cannot both be true. In the example below, Rainbird uses mutually exclusive concepts to check whether a customer has an account with a bank or not.

If the end-user is asked a question such as “Does the Customer have account status existing?” and the user answers “no”, Rainbird automatically infers the result as ‘not’ as the two instances are mutually exclusive.

If the behaviour was not set to mutually-exclusive, Rainbird would also ask the opposite question “Does the Customer have account status not?”, which is a redundant question as the end-user has already provided the answer by answering ‘no‘ to the previous question.

Click on a subtopic below for more information:

  1. Mutual Exclusive - Build Example
  2. Mutual Exclusive - Downloadable Model
0 followers
0 questions
0 posts

You will need to register to be able to post or comment on a topic.  

Mutual Exclusive - Build Example

Build string concepts

Two concepts are created: the subject, “Customer”, and the object “Account”. The two concepts are linked with the relationship “has status”.

Build instances

The concept “Account” has two instances, which will be defined as mutually exclusive... (More)

Mutual Exclusive - Downloadable Model - Map

Please run the query on the ‘result based on status’ relationship for an example of a query that uses mutually exclusive instances.

.menu.bell.icon {color: #1c083b;}