<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">Reasoning over Knowledge Graphs in an Intuitionistic Description Logic</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Bernardo</forename><surname>Alkmim</surname></persName>
							<email>bpalkmim@gmail.com</email>
							<affiliation key="aff0">
								<orgName type="department">Departamento de Informática</orgName>
								<orgName type="institution">Pontifícia Universidade Católica do Rio de Janeiro</orgName>
								<address>
									<country key="BR">Brazil</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Edward</forename><surname>Haeusler</surname></persName>
							<affiliation key="aff0">
								<orgName type="department">Departamento de Informática</orgName>
								<orgName type="institution">Pontifícia Universidade Católica do Rio de Janeiro</orgName>
								<address>
									<country key="BR">Brazil</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Daniel</forename><surname>Schwabe</surname></persName>
							<email>dschwabe@inf.puc-rio.br</email>
							<affiliation key="aff0">
								<orgName type="department">Departamento de Informática</orgName>
								<orgName type="institution">Pontifícia Universidade Católica do Rio de Janeiro</orgName>
								<address>
									<country key="BR">Brazil</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Reasoning over Knowledge Graphs in an Intuitionistic Description Logic</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">BDBAD8D27B5D0593BE8602EB6209D33F</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-24T09:18+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<textClass>
				<keywords>
					<term>Description Logic</term>
					<term>Intuitionistic Logic</term>
					<term>iALC</term>
					<term>Knowledge Graphs</term>
					<term>Natural Deduction</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>In this work we present a way to model and reason over Knowledge Graphs via an Intuitionistic Description Logic called iALC. We also introduce a Natural Deduction System for iALC to reason over our modelling of the information of the Knowledge Graphs. Furthermore, we apply this modelling to some examples in a context that aims to support the concepts of Trust, Privacy, and Transparency.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1">Introduction</head><p>Throughout the years there have been several different ways to represent knowledge, either by trying to mimic human cognitive behaviour or by other approaches. Knowledge Base Systems (KBSs) <ref type="bibr" target="#b12">[13]</ref> are one of such methods, derived from Expert Systems, explained in <ref type="bibr" target="#b4">[5]</ref> and <ref type="bibr" target="#b9">[10]</ref>.</p><p>One way to represent KBSs is via Knowledge Graphs (KGs), which can be seen in <ref type="bibr" target="#b14">[15]</ref> and <ref type="bibr" target="#b17">[18]</ref>. With their graph-like structure, KGs offer a versatile way to represent data that postpones the necessity for a schema, which adapts well to different domains. The fact that they are graphs is, as well, another positive point, since this mathematical structure has extensive literature and theory <ref type="bibr" target="#b3">[4]</ref> behind it. This is especially useful when one utilises Machine Learning, since KGs can connect it to Knowledge Representation thus imbuing it with tools to solve certain questions in the data, such as Data Insufficiency or Zero-shot Learning.</p><p>One other way to represent knowledge is via the usage of Description Logics (DL) <ref type="bibr" target="#b1">[2]</ref>. DLs consist in the representation of entities called concepts, roles, and individuals, as well as their relationships, based around axioms. This type of Logic comes in different flavours, depending on which properties one wishes to utilise. One of the attractive points of DLs is the possibility to make syntactic reasoning (due to being a Logic) over the associated KB, via whichever deduction system is more adequate.</p><p>There is, as well, especially for the domain of Law, the option of utilising Deontic Logic, but it is criticised (as in <ref type="bibr" target="#b18">[19]</ref>, for instance) for not making explicit the models and theories for the making of legal KBSs, among other reasons. By choosing Description Logic, one may utilise a calculus for deductions, similarly to Deontic Logic, but without facing the same modelling issues.</p><p>We then end up with two means to represent data: KGs, which are versatile and can represent data more accurately, and DLs, over which one can reason while extracting more direct meaning from the reasoning itself at the same time. Due to their equivalence in representation, we are able to reap the good parts of both these methods over the same KBS.</p><p>In this article, we present our efforts in translating a representation of a KBS that focuses on the concepts of Trust, Privacy, and Transparency of information from a KG to a DL, namely, iALC, in order to reason over it.</p><p>iALC is a Logic that has been used to represent and reason over the domain of Law, and its structure is based on Kelsenian Jurisprudence. Thus, legal individuals can be seen as Valid Legal Statements (VLSs) in iALC, and the notion of precedence between Laws (as per Theory of Legal Order in <ref type="bibr" target="#b2">[3]</ref>) can be directly represented in it as a relation between worlds in a Kripke Model. The choice to utilise a Description Logic instead of a type of the more usual Deontic Logic comes from the existence of certain conceptual problems of Deontic Logic, especially when one considers the notion of validity of a normative sentence.</p><p>In section 2, we introduce the concept of KGs and the framework which allows them to better deal with concepts of Trust, Privacy, and Transparency of information.</p><p>In section 3, we explain the main concepts of the DL we choose to reason with, iALC, and explain why it was chosen to do so.</p><p>In section 4, we contextualise the KBS and give some examples of formalizations in iALC and the reasonings made, as well as discuss our decision making throughout this process.</p><p>In section 5, we conclude the article and point to future directions of this work.</p><p>In the appendix A, we present the Natural Deduction system rules created for iALC to make the deduction itself.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2">Knowledge Graphs</head><p>There are multiple different definitions for KGs in the literature and varied implementations of them (all discussed thoroughly in <ref type="bibr" target="#b11">[12]</ref>), but they all share a central idea: they utilise graphs to represent data and knowledge. The concept comes from the 70s <ref type="bibr" target="#b15">[16]</ref>, but the term itself has been popularised by Google in 2012, <ref type="foot" target="#foot_0">1</ref> when they implemented the concept to create a system to support moving from search to question answering.</p><p>In general, the nodes in a KG represent entities of the real world and the edges, relations between them. This is, however, a rather simplistic approach that is not much different from a labelled graph. In order to talk about knowledge, it is necessary to have a supplementary ontology, or a set of rules of the domain to be represented. One may use quantification of variables, as well as separate one big KG into smaller ones, in order to isolate semantically certain parts of the original graph.</p><p>In <ref type="bibr" target="#b16">[17]</ref>, the authors present a framework called KG Usage, which allows KGs to support Trust, Transparency, and Privacy concerns in its modelling. This allows for usage in applications for whom decisions based on security or disclosure of information of knowledge is important.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3">iALC</head><p>Description Logics (DL) were already proposed for semantic analysis of natural language utterances in <ref type="bibr" target="#b5">[6]</ref>. In <ref type="bibr" target="#b6">[7]</ref> the DL iALC <ref type="bibr" target="#b8">[9]</ref> was used as the basis of a solver/reasoner for the questions in the exam. iALC is based on the canonical ALC, and was by definition made to deal with law systems. In it, valid legal statements (VLS) are not propositions, but individuals in a legal ontology, i. e. one law cannot be true or false, it just either exists or not in a concept. The propositions we consider are some of the concepts of the ontology (i. e. concepts of the form a : C or C D, for a nominal and C, D concepts), which represent the legal systems that can hold different kinds of laws. They also have a precedence relationship, derived by the hierarchy of individual laws of Kelsenian Jurisprudence <ref type="bibr" target="#b13">[14]</ref>. As an example, one can imagine Brazilian Law or other similar system. It has the Constitution, comprised of some general principles that must precede every other (usually more specific) law that is based on or created after it. With this notion, one can create different tiers of laws in order to not generate legal antinomies with the laws of higher tiers, and those higher laws must precede the lower ones.</p><p>In <ref type="bibr" target="#b0">[1]</ref> iALC is utilised to model and solve questions from the OAB Exam. <ref type="foot" target="#foot_1">2</ref> In this article, the characteristics of this logic are more thoroughly explained, especially in how they make it well suited to deal with normative sentences, especially laws.</p><p>In general, in iALC, legal individuals are specific combinations of laws that represent an artificial legal being, which can validate or not certain concepts. They do not, however, represent fully individuals outside of the legal expressiveness of the logic; they are mere legal projections of real-life concepts. For example, john : Attorney states that the legal individual john, which represents a legal document that proves that John is an attorney, is part of the concept Attorney, which represents the set of laws relating to attorneys. In general, to simplify, individuals like john are assumed to always be, from the start, in a nominal. <ref type="foot" target="#foot_2">3</ref> Notice that everything in this example is in the ontology on laws.</p><p>iALC is also an intuitionistic logic. Intuitionistic logic is constructive by nature <ref type="bibr" target="#b10">[11]</ref>. Intuitionistically, ¬A being true can be understood as there being no way to construct a proof of A (or that, by assuming A to be true, one is led to a contradiction). With this, we have, for instance, that ¬¬A being true does not imply in A being true, which is a valid implication in classical logic. In fact, intuitionistic logic is weaker than classical logic (see <ref type="bibr" target="#b10">[11]</ref>), but it allows for non-conflicting existence of otherwise thought-tobe contradictory logical formulas in Description Logic, particularly. In the domain of law, this allows, for instance, the existence of a model representing two distinct legal systems, one in which the death penalty is not allowed, and the other in which it is not. In a regular (i.e. Classical) DL, this cannot be represented directly when modelling, since a Kripke model for a Classical Logic collapses all worlds (the legal individuals) to the same one, causing a contradiction by allowing and prohibiting the death penalty at the same time. This would force us to find a more conflated way to insert Legal Individuals into the logic, at the risk of losing legibility, and, even worse, soundness.</p><p>This non-conflicting existence of different sets of rules relates directly to the existence of different KGs in section 4, each with their own set of rules, which may contradict those of other KGs. iALC not only allows for those to coexist, but it also has means to solve those apparent contradictions.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4">Some Examples</head><p>The examples utilised here are from <ref type="bibr" target="#b16">[17]</ref>, further explained in the third section of that article. To summarise, in a fictional context a disaster occurs and a person, Ed, wishes to donate to a foundation in order to give aid to the people affected by it. He, however, wants to be sure that his money will be well spent, so he needs to trust the organisation to which he intends to give his money. There is another person, George, who is an officer in a non-governmental organisation (NGO) called ReliefOrg, whom Ed does not trust. Assuming that there is a law that requires NGOs to disclose publicly (transparency) their officers, Ed must have access to this information from ReliefOrg. Even so, George may not want to disclose his personal information to others (right to privacy), creating a conflict that must be resolved. In this case, since it is in the law that this kind of information must be disclosed, the transparency law has priority.</p><p>The approach there postulates the existence of a trusted graph containing all the statements an agent will rely upon to decide to take some action. Rules define when a statement should be included in this graph (trust), as well as when some action should be allowed (transparency) or denied (privacy). In the example, there are also other scenarios in this same context that relate the concepts of Trust, Privacy, and Transparency in similar ways.</p><p>It is worth noting that this hierarchy of normative sentences, i.e. rules, laws, was the starting point to formalise this information in iALC, since the logic was created to deal with laws from the cradle.</p><p>We will now show a modelling of basic information and some examples of rules of this scenario, based on the same rules from the original article, that modelled them in a KG divided in several Knowledge Items, each one being a nanopublication <ref type="bibr" target="#b7">[8]</ref>.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.1">Base knowledge</head><p>Part of the information is shared by all agents, and is the base knowledge for the scenario, namely: ReliefOrg is a non-profit organisation, AuditInc is a certification agency, George is an officer of ReliefOrg and of AuditInc.</p><p>For the base graph knowledge, we have the following formulas: relie f : NonPro f it L audit : CertAgency L NonPro f it Organisation L CertAgency Organisation L george o f f icerInOrg relie f george o f f icerInOrg audit In the formulas above, we can see that the individuals are represented by nominals in iALC, as would be expected. We utilise a concept to represent a category or set. In the first formula, we have that the individual relie f , an individual representing Re-liefOrg, is part of the concept NonPro f it, a concept for non-profit organisations. One concept can be a subset of another, as in the third formula, which states that non-profit organisations are a subset of organisations in general. When a relation between two individuals in established, it is translated into a role. In the fifth formula, for example, the role o f f icerInOrg relates the individuals george and relie f .</p><p>To model the rules in iALC, we needed to make them somewhat general to be able to chain formulas with one another. So, we used generic labels when modelling e.g. relie f : NonPro f it L , where L is any list of labels for the concept NonPro f it.</p><p>To make the actual reasoning, we developed a Natural Deduction (ND) <ref type="foot" target="#foot_3">4</ref> system for iALC (whose rules are all in appendix A), which has labels to facilitate the chaining of existential restrictions. Our ND system needs these chainings in order to connect in the same reasoning individuals that are related indirectly (via transitivity) in a fully TBOX-esque fashion. For instance, when an agent intends to do an action to an organisation that has a certain o f f icer, we need to encapsulate all these different relations between distinct agents in one single formula in order to make more direct and structurally simple reasonings without losing meaning. Luckily, it is possible in DLs via applying restrictions sequentially on concepts. The labels on concepts also aid this chaining by giving the context at all times, thus maintaining the soundness of the system. This chaining of formulas is explained more concretely in section 4.2.</p><p>The rules utilised in this document are, mostly, ∃ − intro, ∃ − elim, −elim, and − intro. If applicable, the versions of the rules are the ones that have nominals.</p><p>The rules used have to do with our modelling choices: most of the modelling involved existential restrictions (∃), subjunctions of concepts ( ), and conjunctions of concepts ( ). Also, since the cases are always instantiated, all the rules involved nominals, to reflect the information as faithfully as possible.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.2">Rule Ed1 (TRUST)</head><p>We begin with the first rule of knowledge graph for the agent Ed: Ed wants to donate to a certified not-for-profit organisation. More precisely, if an organisation org has (some) officer o f , financial record f in, f in is audited by organisation aud, aud is certified by organisation cert, cert is a Certification Agency and the provenance graph for cert includes the fact that it is an accredited agency, then Ed's trusted graph includes the fact that org is a non-profit organisation. Some of those sentences can be represented with role assertions, creating the related roles:</p><p>f in auditedBy aud aud certi f iedBy cert org hasFinRecord f in o f o f f icerInOrg org These formulas, however, do not fit well into our Natural Deduction system, since they involve information pertinent to the ABOX (assertion) part of iALC, and the ND system reasons over the TBOX (terminological) part of it. Luckily, they are equivalent to a more TBOX-friendly format, in the form of Restrictions of Concepts (in our case, existential restrictions). <ref type="foot" target="#foot_4">5</ref> We have not yet seen the case in which a universal restriction was necessary, but their modelling would be similar and would chain just as naturally as the existential ones (and iALC supports it if needed). This results in:</p><p>f in : ∃auditedBy.Organisation L aud : ∃certi f iedBy.CertAgency L org : ∃hasFinantialRecord.FinRecord L o f : ∃o f f icerInOrg.Organisation L The formulas are given generic labels (namely L, representing a list of labels) in order to give them flexibility when used in proofs, because, in those, they need to be able to represent any context in which they appear. Once context is given, L is substituted by an adequate list of labels. This generic list of labels can be interpreted as the formula being valid regardless of the context in which it is inserted. The supposition that financial record f in is audited by an organisation, i.e. ∃auditedBy.Organisation, can be used in the situation presented, or in any other. If we use fixed labels for this context, the isolated sentence may lose meaning in a different context (maybe one without a certification agency involved, for instance). After the proof, these concrete contexts will be explained more clearly. By chaining some of those in order to relate these different individuals we have:</p><p>f in : ∃auditedBy.∃certi f iedBy.CertAgency L The formula above represents a refinement in f in : ∃auditedBy.Organisation L via aud : ∃certi f iedBy.CertAgency L , which is an existential restriction on CertAgency, a subconcept of Organisation. org : ∃hasFinRecord.∃auditedBy.∃certi f iedBy.Organisation L This last formula can be read as org has a (certain) financial record which is audited by an organisation certified by a certification agency, which is itself an organisation. Representing the entire rule, we have: ∃hasFinRecord.∃auditedBy.∃certi f iedBy.Organisation NonPro f it L Showing that, for Ed's graph, a company that fits into these criteria must be a nonprofit organisation. So, here is the proof for the first rule in our ND system (names were shortened to fit the page): In this proof, the generic label L is substituted by the concrete labels, giving the context needed to the formulas. For instance, f in : ∃a.∃c.O ∃h has the label ∃h, indicating that the restricted concept ∃a.∃c.O can be even further restricted via the role h (hasFinantialRecord), which connects f in to another individual, namely, org. Whereas org : ∃h.∃a.∃c.O has no labels, because they are not necessary. In the case of this formula, everything is explicit in the restrictions themselves.</p><p>It is worth noting that, in our situation, o f can be replaced by george, org by relie f , and cert, by audit, showing that ed is aware that relie f is a non-profit organisation.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.3">Rule Ed2 (Ed does not trust George)</head><p>To capture the fact that Ed does not trust George (in the sense of donating to an organisation where George is an officer), we include the following rule. If Ed's trusted graph includes the fact that org is a non-profit organisation, George is officer of org, and Ed intends to take action a of type Donate to org, then a is Denied.</p><p>We can set the formulas to: george : ∃o f f icerInOrg.Org L org : NonPro f it L act : Donate L act : ∃directedTo.Org L ed : ∃intends.Donate L (alternatively) ed : ∃intends.∃directedTo.Org L We want to get to act : Denied L . However, before going on to the proof, we need a formalisation of the fact that Ed does not trust George as an officer in an organisation, and that it nullifies his action: ed notTrust george, which becomes ed : ∃notTrust.Person L , and, after another transformation:</p><p>ed : ∃notTrust.∃o f f icerInOrg.Org L We have just inserted a new concept, Person, not necessarily present in the context, which was necessary in order to categorise of what concept george is a part. An analogous concept would be O f f icer, but the name would be solely to give semantic information to the reader. To the situation itself the semantics of the concepts are given extensionally.</p><p>We also need to account for the fact that the action is directed towards a non-profit organisation:</p><p>(∃intends.∃directedTo.NonPro f it ∃noTrust.∃o f f icerIn.Org) ∃intendsTo.Denied L Then, we have the following proof: Now, let us focus on the graph of George, the officer, who has a rule that does not allow divulging (reading) any information about him, including his association with an organisation. This rule, which represents his right to privacy, and rule 4.5, which represents the transparency of a non-profit organisation are apparently in conflict. In the next sections we explain how this conflict is solved. The proofs for the rules of his graph will be similar to those in the graph of Ed. To contextualise, org is the organisation relie f , and the agent who intends to read information on ReliefOrg, ag, is ed.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.5">Rule Transp (TRANSPARENCY)</head><p>The rule for the Transparency ruling over our agent George's privacy rule is: if an organisation org is of type NonPro f it and has officer o f , action a is of type read and an agent ag intends a, then A is Allowed.</p><p>There are also two additional pieces of information to the graph: the primary source to the transparency rule is Non-profit Act, and Non-profit Act is a Law.</p><p>org : NonPro f it L o f f o f f icerIn org, which becomes o f f : ∃o f f icerIn.NonPro f it L act : Read L act directedTo org, which becomes act : ∃directedTo.NonPro f it L ag intends act, which becomes ag : ∃intends.Read L , and later ag : ∃intends.∃directedTo.NonPro f it L By transparency, (∃intends.∃directedTo.∃o f f icerIn.NonP ∃intends.Read) ∃intends.Allowed. We also may represent l : NonPro f itAct as the legal individual for the Non-profit Act. With that, we should have act : Allowed L . This will not be used in the proof, but it is interesting to state the disjunction between the concepts Denied and Allowed: Denied ¬Allowed. The bigger premise taking to the conclusion tells us that, since a concept is valid for an individual who is preceded by another, the one who precedes (in our case, l) must also validate such concept, due to the intuitionistic nature of the logic, that requires the construction of the validity of a concept to be passed through (in this case, to have been passed through) to following individuals hierarchically.</p><p>At this point, we still need to relate rules 4.4 and 4.5, which could pose a problem since they apparently contradict each other. The following rule, then, comes to the rescue.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.6">MetaRule1 (Precedence)</head><p>This rule simply states that Laws precede personal privacy rules from the graphs of agents, such as rule 4.4. This is simply solved by iALC with LegalRule PersonalPrivRule L . We can, then, conclude that rule 4.5 has precedence over rule 4.4, since the law ruling over the transparency of non-profit organisations has precedence over George's right to privacy (at least when regarding his work at such an organisation).</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5">Final Remarks</head><p>In this article, we presented the concepts of KGs and showed how they can be used in contexts that involve the concepts of Trust, Privacy, and Transparency, as well as an alternate formalisation for them in iALC, an Intuitionistic Description Logic, to show one way one can reason over them. This modelling and reasoning was proven successful on the context shown and conveyed how we can translate the complexities of KGs via the intuitionistic notion of truth that iALC has.</p><p>For future work, we intend to extend this representation in iALC in this context of Trust, Privacy, and Transparency, specially since a lot of the decision making in terms of reasoning comes from the relations between laws that seem conflicting at first glance, but that are solved by mechanisms iALC is equipped to model.</p><p>In regards to the more theoretical side of the work, we aim to give a more formal introduction to the Natural Deduction system for iALC, via showing its properties of soundness and completeness, for instance, which are out of the scope of this article, and possibly implement an automated reasoner to it for it to be used in a larger scale.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>A Natural Deduction System for iALC</head><p>Let α and β concepts, x and y nominals, δ formula, and R a role. L represents a list of labels (possibly empty). Labels represent either negations of concepts, or universal or existential restrictions on concepts, made implicit. They indicate a sort of context to the concept they are attached to. L ∀ is a list that restricts all labels in itself to ∀R of some kind, and L ∃ restricts all to ∃R. Rules that utilise nominals and involve x and y assume that there is a role connecting them, i.e. xRy. Please note that only the rules related to iALC operators utilised in this article are shown. The n in the names of some rules indicate that those are the versions which utilise nominals. </p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head></head><label></label><figDesc>org : NP ∃i,∃d act : ∃d.NP ∃i ∃ − i ed : ∃i.∃d.NP ∃ − i ed : ∃nT.∃o.O ed : (∃i.∃d.NP ∃nT.∃o.O) − i (∃i.∃d.NP ∃nT.∃o.O) ∃i.D L ed : ∃i.D −e act : D ∃i ∃ − e 4.4 Rule George1 (PRIVACY)</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head></head><label></label><figDesc>org : NP ∃in,∃diTo,∃o f In o f r : ∃o f In.NP ∃in,∃diTo ∃ − i a : ∃diTo.∃o f In.NP ∃in ∃ − i ag : ∃in.∃diTo.∃o f In.NP ∃ − i a : R ∃in ag : ∃in.R ∃ − i ag : (∃in.∃diTo.∃o f In.NP ∃in.R) − i (∃in.∃diTo.∃o f In.NP ∃in.R) ∃in.A ag : ∃int.A −e a : A ∃int ∃ − e Also, we have a secondary proof to show that the transparency rule (represented by the individual rtr) is preceded by the law l. rtr : (∃in.∃diTo.∃o f In.NP ∃in.R) ∃in.A l rtr l : (∃in.∃diTo.∃o f In.NP ∃in.R) ∃in.A −elim This Natural Deduction rule, −elim, is a way to introduce the mechanism of precedence between individual laws directly into the Natural Deduction system. The smaller premise, l rtr, indicates the precedence among the individuals concerned.</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_2"><head>y</head><label></label><figDesc>: α ∃R,L x : (∃R.α) L ∃ − intro x : (∃R.α) L y : α ∃R,L ∃ − elim x : α L1 . . . . x : β L2 x : (α L1 β L2 ) −intro − n x : α L1 x : (α L1 β L2 ) x : β L2 −elim − n x : α L . . . . x : ⊥ x : (¬α) ¬L ¬ − intro − n x : α L x : (¬α) ¬L x : ⊥ ⊥ − intro − n x : α L ∀ x : β L ∀ x : (α β ) L ∀ − intro − n x : (α β ) L ∀ x : α L ∀ − elim 1 − n x : α L y x y : α L −elim x : (α β ) L ∀ x : β L ∀ − elim 2 − n</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_1"><head></head><label></label><figDesc>If george is an officer of organisation org, action a is of type read, and Agent ag intends a Then a is Denied. org : Org L george o f f icerIn org, aka george : ∃o f In.Org L a : Read L ag intends a, aka ag : ∃intends.Read L a directedTo george, aka a : ∃directedTo.∃o f f icerIn.Org L We also have, by the privacy rule, that (∃intends.∃directedTo.∃o f f icerIn.Org ∃intends.Read) ∃intends.Denied.We want to arrive at a : Denied L . The proof is as follows:</figDesc><table><row><cell>org : O ∃in,∃diTo,∃o f In g : ∃o f In.O ∃in,∃diTo ∃ − i a : ∃diTo.∃o f In.O ∃in ∃ − i ag : ∃in.∃diTo.∃o f In.O ∃ − i ag : (∃in.∃diTo.∃o f In.O ∃in.R) a : R ∃in ag : ∃in.R ag : ∃int.D ∃ − i − i (∃in.∃diTo.∃o f In.O ∃in.R) ∃in.D a : D ∃int ∃ − e</cell><cell>−e</cell></row></table></figure>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="1" xml:id="foot_0">https://www.blog.google/products/search/introducing-knowledge-graph-things-not/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="2" xml:id="foot_1">The Brazilian Bar Exam, which candidates have to pass in order to be able to practice law.</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="3" xml:id="foot_2">A nominal is a concept defined extensionally, consisting of only one individual, by which it is referenced. A nominal for john is { john}. Throughout this article we will omit this notation, referring to the nominals without the brackets.</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="4" xml:id="foot_3">ND is a deduction system that has many similarities to the way a person makes an actual deduction, which relates closely to a previous usage of iALC: answering questions to a Bar Exam. It is, in a way, a more readable Sequent Calculus. Another reason in its favour is the lack of support in general of inferential tools to Intuitionistic Logics.</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="5" xml:id="foot_4">The choice here is between universal and existential restrictions, but universal restrictions would imply that, for instance, the organisation org would have every financial record (in the world) related to it, which is very rarely the case.</note>
		</body>
		<back>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">Utilizing ialc to formalize the brazilian oab exam</title>
		<author>
			<persName><forename type="first">Bernardo</forename><surname>Alkmim</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Edward</forename><surname>Hermann Haeusler</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Alexandre</forename><surname>Rademaker</surname></persName>
		</author>
		<ptr target="http://ceur-ws.org/Vol-2381/" />
	</analytic>
	<monogr>
		<title level="m">Proceedings from the EXplainable AI in Law Workshop (XAILA)</title>
				<meeting>from the EXplainable AI in Law Workshop (XAILA)</meeting>
		<imprint>
			<publisher>CEUR-WS</publisher>
			<date type="published" when="2018">2018</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<monogr>
		<title level="m" type="main">The Description Logic Handbook: Theory, Implementation, and Applications</title>
		<author>
			<persName><forename type="first">Franz</forename><surname>Baader</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Diego</forename><surname>Calvanese</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Deborah</forename><surname>Mcguinness</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Daniele</forename><surname>Nardi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Peter</forename><surname>Patel-Schneider</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2007">2007</date>
			<publisher>Cambridge University Press</publisher>
			<biblScope unit="page">1</biblScope>
		</imprint>
	</monogr>
	<note>2nd Edition</note>
</biblStruct>

<biblStruct xml:id="b2">
	<monogr>
		<title level="m" type="main">Theory of Legal Order</title>
		<author>
			<persName><forename type="first">N</forename><surname>Bobbio</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">C C L</forename><surname>Santos</surname></persName>
		</author>
		<imprint>
			<date type="published" when="1995">1995</date>
		</imprint>
		<respStmt>
			<orgName>Universidade de Brasília</orgName>
		</respStmt>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<monogr>
		<title level="m" type="main">Graph Theory</title>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">A</forename><surname>Bondy</surname></persName>
		</author>
		<author>
			<persName><forename type="first">U</forename><forename type="middle">S</forename><surname>Murty</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2008">2008</date>
			<publisher>Springer Publishing Company, Incorporated</publisher>
		</imprint>
	</monogr>
	<note>1st edition</note>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">Dendral and meta-dendral: Their applications dimension</title>
		<author>
			<persName><forename type="first">Bruce</forename><forename type="middle">G</forename><surname>Buchanan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Edward</forename><forename type="middle">A</forename><surname>Feigenbaum</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Artificial Intelligence</title>
		<imprint>
			<biblScope unit="volume">11</biblScope>
			<biblScope unit="issue">1</biblScope>
			<biblScope unit="page" from="5" to="24" />
			<date type="published" when="1978">1978</date>
		</imprint>
	</monogr>
	<note>Applications to the Sciences and Medicine</note>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">Entailment, intensionality and text understanding</title>
		<author>
			<persName><forename type="first">Cleo</forename><surname>Condoravdi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Dick</forename><surname>Crouch</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Valeria</forename><surname>De Paiva</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Reinhard</forename><surname>Stolle</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Daniel</forename><forename type="middle">G</forename><surname>Bobrow</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the HLT-NAACL 2003 Workshop on Text Meaning -Volume 9, HLT-NAACL-TEXTMEANING &apos;03</title>
				<meeting>the HLT-NAACL 2003 Workshop on Text Meaning -Volume 9, HLT-NAACL-TEXTMEANING &apos;03<address><addrLine>Stroudsburg, PA, USA</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2003">2003</date>
			<biblScope unit="page" from="38" to="45" />
		</imprint>
	</monogr>
	<note>Association for Computational Linguistics</note>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">Passing the brazilian oab exam: Data</title>
		<author>
			<persName><forename type="first">Pedro</forename><surname>Delfino</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Bruno</forename><surname>Cuconato</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Edward</forename><surname>Hermann Haeusler</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Alexandre</forename><surname>Rademaker</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Legal Knowledge and Information Systems</title>
		<imprint>
			<biblScope unit="page">89</biblScope>
			<date type="published" when="2017">2017</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">The anatomy of a nano-publication</title>
		<author>
			<persName><forename type="first">Paul</forename><surname>Groth</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Andrew</forename><surname>Gibson</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Johannes</forename><surname>Velterop</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Information Services and Use</title>
		<imprint>
			<biblScope unit="volume">30</biblScope>
			<biblScope unit="page" from="1" to="2010" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">On how kelsenian jurisprudence and intuitionistic logic help to avoid contrary-to-duty paradoxes in legal ontologies</title>
		<author>
			<persName><forename type="first">Edward</forename><surname>Hermann</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Haeusler</forename></persName>
		</author>
		<author>
			<persName><forename type="first">Alexandre</forename><surname>Rademaker</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Proc. Journal of Applied Non-Classical Logics</title>
		<imprint>
			<date type="published" when="2016">2016</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<monogr>
		<title level="m" type="main">Building Expert Systems</title>
		<author>
			<persName><forename type="first">Frederick</forename><surname>Hayes-Roth</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Donald</forename><forename type="middle">A</forename><surname>Waterman</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Douglas</forename><forename type="middle">B</forename><surname>Lenat</surname></persName>
		</author>
		<imprint>
			<date type="published" when="1983">1983</date>
			<publisher>Addison-Wesley Longman Publishing Co., Inc</publisher>
			<pubPlace>USA</pubPlace>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<monogr>
		<title level="m" type="main">Intuitionism: An Introduction</title>
		<author>
			<persName><forename type="first">A</forename><surname>Heyting</surname></persName>
		</author>
		<imprint>
			<date type="published" when="1956">1956</date>
			<publisher>North-Holland Publishing</publisher>
			<pubPlace>Amsterdam, Netherlands</pubPlace>
		</imprint>
	</monogr>
	<note>3rd edition</note>
</biblStruct>

<biblStruct xml:id="b11">
	<monogr>
		<title level="m" type="main">Knowledge graphs</title>
		<author>
			<persName><forename type="first">Aidan</forename><surname>Hogan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Eva</forename><surname>Blomqvist</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Michael</forename><surname>Cochez</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Claudia</forename><surname>Amato</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Gerard</forename><surname>De Melo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Claudio</forename><surname>Gutierrez</surname></persName>
		</author>
		<author>
			<persName><forename type="first">José</forename><surname>Emilio Labra</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Sabrina</forename><surname>Gayo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Sebastian</forename><surname>Kirrane</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Axel</forename><surname>Neumaier</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Roberto</forename><surname>Polleres</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Axel-Cyrille Ngonga</forename><surname>Navigli</surname></persName>
		</author>
		<author>
			<persName><surname>Ngomo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Sabbir</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Anisa</forename><surname>Rashid</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Lukas</forename><surname>Rula</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Juan</forename><surname>Schmelzeisen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Steffen</forename><surname>Sequeda</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Antoine</forename><surname>Staab</surname></persName>
		</author>
		<author>
			<persName><surname>Zimmermann</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2020">2020</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<monogr>
		<author>
			<persName><forename type="first">Matthias</forename><surname>Jarke</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Bernd</forename><surname>Neumann</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Yannis</forename><surname>Vassiliou</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Wolfgang</forename><surname>Wahlster</surname></persName>
		</author>
		<title level="m">KBMS Requirements of Knowledge-Based Systems</title>
				<meeting><address><addrLine>Berlin, Heidelberg</addrLine></address></meeting>
		<imprint>
			<publisher>Springer-Verlag</publisher>
			<date type="published" when="1989">1989</date>
			<biblScope unit="page" from="381" to="394" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b13">
	<monogr>
		<author>
			<persName><forename type="first">H</forename><surname>Kelsen</surname></persName>
		</author>
		<title level="m">Pure Theory of Law</title>
				<imprint>
			<publisher>Lawbook Exchange</publisher>
			<date type="published" when="2005">2005</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b14">
	<analytic>
		<title level="a" type="main">A review of relational machine learning for knowledge graphs</title>
		<author>
			<persName><forename type="first">Maximilian</forename><surname>Nickel</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Kevin</forename><surname>Murphy</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Evgeniy</forename><surname>Volker Tresp</surname></persName>
		</author>
		<author>
			<persName><surname>Gabrilovich</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the IEEE</title>
				<meeting>the IEEE</meeting>
		<imprint>
			<biblScope unit="volume">104</biblScope>
			<biblScope unit="page" from="12" to="2015" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b15">
	<analytic>
		<title level="a" type="main">Human Resources Research Organization</title>
		<author>
			<persName><forename type="first">E</forename><forename type="middle">W</forename><surname>Schneider</surname></persName>
		</author>
		<author>
			<persName><surname>Va</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">The Interface System and Its Implications For Sequence Control and Data Analysis / E</title>
				<editor>
			<persName><forename type="first">W</forename><surname>Schneider</surname></persName>
		</editor>
		<meeting><address><addrLine>Alexandria; Washington, D.C.</addrLine></address></meeting>
		<imprint>
			<publisher>ERIC Clearinghouse</publisher>
			<date type="published" when="1973">1973</date>
		</imprint>
	</monogr>
	<note>Course Modularization Applied</note>
</biblStruct>

<biblStruct xml:id="b16">
	<monogr>
		<title level="m" type="main">Trust and privacy in knowledge graphs</title>
		<author>
			<persName><forename type="first">Daniel</forename><surname>Schwabe</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Carlos</forename><surname>Laufer</surname></persName>
		</author>
		<idno>CoRR, abs/1903.07673</idno>
		<imprint>
			<date type="published" when="2019">2019</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b17">
	<analytic>
		<title level="a" type="main">Instant espresso: Interactive analysis of relationships in knowledge graphs</title>
		<author>
			<persName><forename type="first">Stephan</forename><surname>Seufert</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Patrick</forename><surname>Ernst</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Srikanta</forename><forename type="middle">J</forename><surname>Bedathur</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Sarath</forename><surname>Kumar Kondreddi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Klaus</forename><surname>Berberich</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Gerhard</forename><surname>Weikum</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 25th International Conference on World Wide Web, WWW 2016</title>
				<editor>
			<persName><forename type="first">Jacqueline</forename><surname>Bourdeau</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">Jim</forename><surname>Hendler</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">Roger</forename><surname>Nkambou</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">Ian</forename><surname>Horrocks</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">Ben</forename><forename type="middle">Y</forename><surname>Zhao</surname></persName>
		</editor>
		<meeting>the 25th International Conference on World Wide Web, WWW 2016<address><addrLine>Montreal, Canada</addrLine></address></meeting>
		<imprint>
			<publisher>ACM</publisher>
			<date type="published" when="2016">April 11-15, 2016. 2016</date>
			<biblScope unit="page" from="251" to="254" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b18">
	<analytic>
		<title level="a" type="main">A model-based approach to legal knowledge engineering</title>
		<author>
			<persName><forename type="first">Andre</forename><surname>Valente</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Joost</forename><surname>Breuker</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">JURIX</title>
		<imprint>
			<biblScope unit="page">1</biblScope>
			<date type="published" when="1992">1992. 1992</date>
		</imprint>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
