text: If you examine the output carefully you may notice an issue. Customer4 only seems to have purchased 2 
  Pizzas. However, if you examine the data in the Individuals by class tab you will see that she purchased 3. 
  The reason that one of them doesn’t show up is that when the data was entered, I typically entered it on 
  the Customer instances. However, for one of Customer4’s Pizzas I entered the data on the Pizza 
  instead. I.e., I asserted on HotVeggiePizza2 that it was purchasedByCustomer Customer4. Since 
  purchasedPizza and purchasedByCustomer are inverses, the reasoner filled in the additional 
  information for me. However, SPARQL doesn’t pay attention to information asserted by the reasoner 
  only information asserted by the user. Note: this depends on the implementation of SPARQL. For 
  example, there is another SPARQL implementation available as a Protégé plugin called Snap SPARQL 
  that is aware of reasoner inferences. 
  
  However, in the default SPARQL tab that we are using, SPARQL ignores information asserted by the 
  reasoner. This is an issue for other plugins for Protégé as well such as the Individuals matrix. Luckily, 
  there is a simple work around for this issue where information asserted by the reasoner can be saved and 
  reloaded so that it is the same as user defined data. This workaround is described in my blog in the article: 
  https://www.michaeldebellis.com/post/export-inferred-axioms 