[Pellet-users] KRSS - inconsistency-causing-statements

Ibach, Brandon L brandon.l.ibach at lmco.com
Wed Nov 28 15:46:02 UTC 2007


Bruno,

I'm not quite sure what you're after, as log messages you quote contain
the same information as the KRSS statements, just in a different syntax.

If you simply want to print out the responsible statements in KRSS, you
should be able to produce them from the information returned by
getExplanationSet.  There may be code to produce KRSS syntax from ATerms
somewhere out in the world, but if not, I imagine writing such code
would not be a terribly difficult task (famous last words, I
suppose...).

If you want to produce pointers to actual lines in your input ontology
or something to that effect, I'm not sure how you'd proceed, or even if
Pellet keeps enough of that sort of information around (I kind of doubt
it, but I could be wrong).

-Brandon :)
 

> -----Original Message-----
> From: pellet-users-bounces at lists.owldl.com 
> [mailto:pellet-users-bounces at lists.owldl.com] On Behalf Of 
> Bruno Fillipe
> Sent: Tuesday, November 27, 2007 2:09 PM
> To: pellet-users at lists.owldl.com
> Subject: [Pellet-users] KRSS - inconsistency-causing-statements
> 
> Hi Everybody,
> 
> My KRSS KnowledgeBase is as below :
> 
> ;;; Knowledge Base
> (define-primitive-role r)
> (related a b r)
> (instance a (some r D))
> (instance a (at-most 1 r TOP))
> (instance b (not D))
> 
>  This is inconsistent KB. Reason for inconsistency is obtained by
>  abox.getExplanationSet()      in pellet,  which is as shown below.
> 
> WARN [main] (KnowledgeBase.java:1575) - Inconsistent ontology. Reason:
> Individual b is forced to belong to class D and its complement
> WARN [main] (KnowledgeBase.java:1577) - ExplanationSet:
> [type(a,max(r,1,_TOP_)), type(a,some(r,D)), prop(r,a,b),
> type(b,not(D))]
> 
> But, I want to get all the original statements
> responsible for inconsistency .i.e.
> ExplanationSet: [(related a b r), (instance a (some r D)), (instance a
> (at-most 1 r TOP)), (instance b (not D))]
> 
> Can someone point to the function available in pellet for that, or
> can someone give hint how can I implement (modify) this functionality?
> 
> Thanks.
> regards, Bruno
> _______________________________________________
> Pellet-users mailing list
> Pellet-users at lists.owldl.com
> http://lists.owldl.com/mailman/listinfo/pellet-users
> _______________________________________________
> 
> Sponsored by Clark & Parsia, LLC http://clarkparsia.com/
> 


More information about the Pellet-users mailing list