One of the main benefits of working with OWL is the availability of powerful automated reasoners. Reasoning involves two steps: logical validation (described in detail below) and automatic classification. Automatic classification involves asserting all inferred superclasses.
There are several reasoners available, and each has different capabilities and characteristics. For this example we’ll be using ELK, a very fast reasoner that supports the EL subset of OWL 2.
robot reason --reasoner ELK \ --input ribosome.owl \ --output results/reasoned.owl
It’s also possible to place the new inferences in their own ontology with
robot reason --reasoner ELK \ --create-new-ontology true \ --input ribosome.owl \ --output results/new_axioms.owl
--create-new-ontology-with-annotations true will place the inferences in their own ontology, along with their annotations (e.g. labels, definitions, etc.).
Sometimes it is important to know which axioms were inferred (designated by an axiom annotation “is_inferred true”):
robot reason --reasoner ELK \ --annotate-inferred-axioms true \ --input ribosome.owl \ --output results/reasoned.owl
reason includes two more options to help clean the reasoned output (by default, these are
--exclude-duplicate-axioms: if set to true, the axioms will not be added to the output if they exist in an import.
--remove-redundant-subclass-axioms: if set to true, any redundant axioms (those that have been asserted and were also inferred) will be removed from the output.
--reasoner is provided, ROBOT will default to ELK. The following other reasoner options are supported:
emr- Expression Materializing Reasoner
structural- Structural Reasoner
ROBOT will always perform a logical validation check prior to automatic classification. Formally, this is known as testing for incoherency, i.e. the presence of either a logical inconsistency or unsatisfiable classes. If either of these hold true, the reason operation will fail and robot will exit with a non-zero code, after reporting the problematic classes.
You can perform detailed debugging using an environment like Protege - load the ontology, switch on the reasoner and use the explain feature. For example, if you have unsatisfiable classes, find one of them (they should show up red) and click on the
? where it says
If you are working on a large complex ontology with multiple imports and you encounter unsatisfiable classes during the release, you can make a minimal ontology for debugging purposes using the
--dump-unsatisfiable) option folled by an output file path. This will find all unsatisfiable classes and use the extract operation to create a debug module.
robot reason --reasoner ELK \ --input incoherent-tbox.owl \ -D results/debug.owl
If the input module contains at least one import, axioms in the debug module will be tagged with the source ontology, to assist in debugging.
You must select between
-n). Both cannot be passed in as
true to one reason command, as they have opposite results.