CODEWITHSUNDEEP
reasoninggraphdb
Anuj Khanna
Anuj Khanna

Reputation: 51

GraphDB Non-monotonic Reasoning?

Does GraphDB offer configurability on materialization strategies to allow for non-monotonic entailment? I.e. adding new explicit statements to the graph might require retracting existing implicit statements that were already inferred based on previous assertions made to the graph.

Upvotes: 1

Views: 99

Answers (2)

Damyan Ognyanov
Damyan Ognyanov

Reputation: 786

The GraphDB inference engine (and it's rule language) do not support negation in any form, so a non-monotoning reasoning is not supported by it.

Upvotes: 1

Henriette Harmse
Henriette Harmse

Reputation: 4787

From the GraphDB documentation this does indeed seem possible to some extend:

GraphDB stores explicit and implicit statements, i.e., the statements inferred (materialised) from the explicit statements. So, when explicit statements are removed from the repository, any implicit statements that rely on the removed statement must also be removed.

I.e., if a new triple causes a previously implicit/explicit triple to be removed, any implicit triples related to this removed triple will also be removed.

You can read more on GraphDB reasoning strategies here.

Upvotes: 1

Related Questions