<?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">Matching Pharmacogenomic Knowledge: Particularities, Results, and Perspectives</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Pierre</forename><surname>Monnin</surname></persName>
							<email>pierre.monnin@orange.com</email>
							<affiliation key="aff0">
								<address>
									<settlement>Orange, Belfort</settlement>
									<country key="FR">France</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Adrien</forename><surname>Coulet</surname></persName>
							<email>adrien.coulet@inria.fr</email>
							<affiliation key="aff1">
								<orgName type="institution">Inria Paris</orgName>
								<address>
									<settlement>Paris</settlement>
									<country key="FR">France</country>
								</address>
							</affiliation>
							<affiliation key="aff2">
								<orgName type="department">Centre de Recherche des Cordeliers</orgName>
								<orgName type="institution" key="instit1">Inserm</orgName>
								<orgName type="institution" key="instit2">Université Paris Cité</orgName>
								<orgName type="institution" key="instit3">Sorbonne Université</orgName>
								<address>
									<settlement>Paris</settlement>
									<country key="FR">France</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Matching Pharmacogenomic Knowledge: Particularities, Results, and Perspectives</title>
					</analytic>
					<monogr>
						<idno type="ISSN">1613-0073</idno>
					</monogr>
					<idno type="MD5">750B0B6CFB6E5D9B6BE2C07EBDF05719</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-23T21:05+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>Instance Matching</term>
					<term>𝑛-ary Tuple</term>
					<term>Preorder</term>
					<term>Graph Embedding</term>
					<term>Pharmacogenomics</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>Knowledge in pharmacogenomics (PGx) is scattered across several resources, e.g., reference databases and the biomedical literature. Matching their content would thus lead to a consolidated view of the available PGx knowledge that could, in turn, support multiple downstream applications, including knowledge curation and precision medicine. However, matching atomic units of PGx knowledge is challenging due to their peculiarities: they are of 𝑛-ary nature, represented with heterogeneous vocabularies, and with various levels of granularity. In this paper, we frame the matching of PGx knowledge units of various provenance as an instance matching problem. We summarize our work to represent such units within a knowledge graph named PGxLOD, and to match them with a rule-based and a graph embedding-based matching approaches. We then particularly discuss the remaining challenges and how our research artifacts opened to the community could foster new benchmarks and methods for structure-based instance matching.</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>The increasing adoption of Linked Open Data (LOD) principles as well as Semantic Web standards and technologies leads to an ever-growing number of resources being published online. Consequently, the knowledge of a domain can be scattered across several complementary, potentially overlapping, resources. That is to say, both similar and complementary knowledge units may be represented across different resources. The aforementioned standards and technologies also allow the concurrent edition of resources by human and software agents. This can lead to duplicates within the same resource. Thus, matching the content of such resources is a first and necessary step towards offering a consolidated view of the available knowledge of a domain. However, matching similar knowledge units within and across resources requires to face issues such as difference of vocabularies or levels of granularity in the representation of knowledge units.</p><p>This general observation is also valid in pharmacogenomics (PGx), a domain that studies the influence of genetic factors on drug response phenotypes. Indeed, state-of-the-art knowledge in PGx is mainly scattered across specialized databases such as PharmGKB, and the biomedical literature, i.e., PubMed. Electronic Health Records (EHRs) can also be mined to extract PGx knowledge. Additionally to this scattering, PGx knowledge also suffers from heterogeneous levels of validation. Indeed, some PGx knowledge units have been extensively studied, validated, and are implemented in clinical practice. On the contrary, others have only been observed on reduced cohorts of patients and remain to be further studied and confirmed. Consequently, matching PGx knowledge across resources would, first, offer a consolidated view of the available knowledge of the domain; and second, should ease knowledge curation. Indeed, PharmGKB is manually fed by human curators who continuously review the literature. Connecting similar PGx knowledge units across articles would ease their work by guiding them to sets of relevant articles to consider jointly and confront. This would facilitate the validation, or moderation, of state-of-the-art knowledge.</p><p>In this paper, we specify the problem of matching PGx knowledge units of various provenance and its challenges (Section 2). Then, we summarize our research results consisting of a knowledge graph (KG) named PGxLOD, and two matching approaches (Section 3). Finally, we outline new research directions, and advocate for the community reuse of our produced research artifacts (Section 4).</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.">Problem Setting</head><p>Matching PGx knowledge requires to tackle several specific issues. Indeed, PGx knowledge units are 𝑛-ary relationships whose arguments are sets of individuals, e.g., the sets of involved drugs, the sets of involved genetic factors, and the sets of involved phenotypes (Figure <ref type="figure">1a</ref>). Such a relationship states that a patient being treated with the specified drugs while having the specified genetic factors will likely experiment the specified phenotypes. To illustrate, Figure <ref type="figure">1b</ref> depicts a state-of-the-art PGx relationship. It should be noted that, on the application side, such knowledge units are named pharmacogenomic relationships. However, in a mathematical formalism or Semantic Web standards, such units are actually relation instances or relation tuples.</p><p>To avoid any ambiguity, we will only refer to PGx knowledge units as PGx tuples.</p><p>We choose to represent PGx tuples in a KG that follows Semantic Web formalisms to interconnect with ontologies and additional LOD about drugs, genetic factors, and phenotypes. Such interconnections provide additional knowledge that we leverage during the matching process. In such formalisms, only binary predicates exist. Consequently, PGx tuples are reified: tuples become individuals that are linked to their components with binary predicates. For example, in Figure <ref type="figure">1c</ref>, the tuple pgt 1 is an individual linked to its components with the causes predicate. In such a view, the matching of PGx tuples comes down to an instance matching task. Due to the reification of tuples, this process will solely rely on a comparison of neighbors of tuples in the graph, which corresponds to a structure-based matching approach.</p><p>Beside their arity, matching PGx tuples requires to face their incomplete and heterogeneous representations (Figure <ref type="figure">2</ref>). These issues inherently lead to various types of alignments between tuples, which is somehow unusual in instance matching. For example, tuples can be identical, e.g., PGx tuples. The phenotype is unknown (denoted ??) for one tuple, coumaphène and hémorragie are the French words for warfarin and hemorrhage, which in turn is a synonym of bleeding. CYP2C9*2 is a gene variant that is more specific than the gene CYP2C9 itself, bleeding is more specific than vascular disorder according to an ontology, and vascular disorders is related somehow to warfarin adverse reaction.</p><p>tuples on the bottom left. Identical alignments may need to rely on translations and synonyms. Some tuples may be more specific than others, e.g., tuples on the right. Matching such granularity differences may rely on domain-specific orderings such as ontology hierarchies. In addition, a specified argument is more specific than an unknown argument, e.g., vascular disorders is more specific than ??. Tuples may also be related when their arguments are comparable w.r.t. some orderings but not all ordered in the same way (e.g., tuples at the bottom). This type of alignments can also connect tuples whose arguments are somehow related without being strictly comparable.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">Representing and Matching PGx Knowledge</head><p>We developed our own ontology, PGxO, and our own KG, PGxLOD<ref type="foot" target="#foot_0">1</ref>  <ref type="bibr" target="#b0">[1]</ref>, to represent PGx tuples of various provenance. PGxO provides a reduced set of classes and predicates to represent reified PGx tuples. We populated PGxO to create PGxLOD by extracting 50,425 PGx tuples from three main resources: structured data of PharmGKB (3,650 tuples), semi-structured data (namely clinical annotations) of PharmGKB (10,240 tuples), and PubMed abstracts (36,535 tuples). PGxLOD also includes knowledge about drugs, genetic factors, and phenotypes by integrating several LOD graphs and ontologies (e.g., DisGeNET, DrugBank, MeSH). PGxLOD is publicly available and respects LOD and FAIR principles.</p><p>To align PGx tuples represented in PGxLOD, we first proposed a symbolic rule-based approach, named tcn3r<ref type="foot" target="#foot_1">2</ref>  <ref type="bibr" target="#b1">[2]</ref>. In this approach, we see PGx tuples in their mathematical form of 𝑛-ary tuples, where each argument is a set of individuals, e.g., from Figure <ref type="figure">1c</ref>, pgt 1 = ({warfarin} , {CYP2C9} , {bleeding}). In this view, matching two tuples comes down to comparing their arguments pairwise, before concluding on the relatedness of the two tuples. To this aim, we define two preorders ≼ p and ≼ 𝒪 that consider ontology statements, and thus enrich the comparison provided by set operators (i.e., =, ⊆). We propose in <ref type="bibr" target="#b1">[2]</ref> five matching rules that conclude on five relatedness levels between tuples. The many resulting alignments illustrate potentialities of our approach and provide insights on PGxLOD. Rule 5 that concludes on the weakest relatedness level generated the most inter-resource alignments, which emphasizes the importance of weaker relatedness levels to align resources and overcome their heterogeneity.</p><p>To cope with this need for flexibility, we considered KG embeddings models. Indeed, the continuous aspect of graph embeddings may provide the needed flexibility. We framed our task as a node clustering task performed on the embedding space 3 [3]. Consequently, we learn node embeddings using Graph Convolutional Networks and the Soft Nearest Neighbor Loss such that similar PGx tuples have low distances between their embeddings. Then, we apply a clustering algorithm on the node embeddings and consider nodes assigned to the same cluster as similar. To learn node embeddings, we constituted gold clusters that are based on the alignments output by our rule-based approach. We showed that integrating domain knowledge by adding inferences in the KG improves clustering performance. We also observed that distances in the embedding space are coherent with the "strength" of the different alignments (e.g., smaller distances for equivalences, larger for weak relations). This result corresponds somehow to a rediscovery of KG semantics in the embedding space.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.">Discussion &amp; Perspectives</head><p>PGxLOD only contains PGx tuples from the state of the art. Hence, one major perspective resides in developing an "observational" version with results of EHR mining or EHRs themselves. However, such an integration raises several issues related to text mining and data privacy (e.g., anonymization, access control). Beside biomedical research, we think PGxLOD is a useful resource for Computer Science researchers. Indeed, we illustrated with our matching approaches the various and challenging characteristics of PGxLOD: integration of several data sets (i.e., owl:sameAs links) and ontologies (i.e., hierarchies of classes and predicates, predicate inverses and symmetry), and a medium size (i.e., scalability issues). For these reasons, PGxLOD constitutes an interesting real-world KG to experiment matching approaches. That is why, we envision to propose its consideration in the Ontology Alignment Evaluation Initiative.</p><p>Both our matching approaches showed how domain knowledge and reasoning mechanisms can serve a structure-based matching. These approaches also present complementary strengths and could foster each other. Two perspectives now lie in (i) learning new rules from clusters output by our embedding-based approach and (ii) updating alignments between PGx tuples when new tuples are integrated. Other aspects of PGx knowledge and metadata are not currently considered but pave the way for future works. For example, PGxO allows to represent negation within PGx tuples (e.g., drugs not causing a tuple). Consequently, we could match contradictory tuples, which raises several questions such as the geometric representation of contradiction in the embedding space. We could also tackle the task of knowledge validation, i.e., confirming or moderating a knowledge unit based on similar or contradictory units existing in other resources. This would require to leverage alignments and heterogeneous quality metadata such as levels of evidence in PharmGKB, or odd ratios in biomedical articles. Such a knowledge validation approach would, in turn, realize our ultimate objective of offering a consolidated view of PGx knowledge to clinicians.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>{d 1 ,Figure 1 :Figure 2 :</head><label>112</label><figDesc>Figure1: Graphical representation of an abstract (1a), an example (1b), and a reified (1c) pharmacogenomic relationships. The example relationship states that patients having the "*4" version of the CYP2D6 gene will not experience the expected effect of codeine. gf stands for genetic factor, d for drug and p for phenotype.</figDesc></figure>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="1" xml:id="foot_0">https://pgxo.loria.fr -https://pgxlod.loria.fr</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="2" xml:id="foot_1">https://github.com/pmonnin/tcn3r</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="3" xml:id="foot_2">https://github.com/pmonnin/gcn-matching</note>
		</body>
		<back>

			<div type="acknowledgement">
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Acknowledgments</head><p>This work was supported by the French National Research Agency (ANR) through the Prac-tiKPharma project (ANR-15-CE23-0028 -http://practikpharma.loria.fr).</p></div>
			</div>

			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">PGxO and PGxLOD: a reconciliation of pharmacogenomic knowledge of various provenances, enabling further comparison</title>
		<author>
			<persName><forename type="first">P</forename><surname>Monnin</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">BMC Bioinformatics</title>
		<imprint>
			<biblScope unit="volume">20</biblScope>
			<biblScope unit="page">16</biblScope>
			<date type="published" when="2019">2019</date>
		</imprint>
	</monogr>
	<note>S</note>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">Knowledge-based matching of n-ary tuples</title>
		<author>
			<persName><forename type="first">P</forename><surname>Monnin</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Ontologies and Concepts in Mind and Machine -25th International Conference on Conceptual Structures, ICCS 2020</title>
				<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2020">2020</date>
			<biblScope unit="volume">12277</biblScope>
			<biblScope unit="page" from="48" to="56" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">Discovering alignment relations with Graph Convolutional Networks: A biomedical case study</title>
		<author>
			<persName><forename type="first">P</forename><surname>Monnin</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Semantic Web</title>
		<imprint>
			<biblScope unit="volume">13</biblScope>
			<biblScope unit="page" from="379" to="398" />
			<date type="published" when="2022">2022</date>
		</imprint>
	</monogr>
</biblStruct>

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