<?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">Towards Pattern-based Complex Ontology Matching using SPARQL and LLM</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author role="corresp">
							<persName><forename type="first">Ondřej</forename><surname>Zamazal</surname></persName>
							<email>ondrej.zamazal@vse.cz</email>
							<affiliation key="aff0">
								<orgName type="institution">Prague University of Economics and Business</orgName>
								<address>
									<country>Czechia</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Towards Pattern-based Complex Ontology Matching using SPARQL and LLM</title>
					</analytic>
					<monogr>
						<idno type="ISSN">1613-0073</idno>
					</monogr>
					<idno type="MD5">12642407739702403886D3A9FDD2ED9A</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2025-04-23T18:46+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>Ontology</term>
					<term>Ontology Matching</term>
					<term>Complex Ontology Matching</term>
					<term>Large Language Model</term>
					<term>Knowledge Graph</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>Complex ontology matching is a process to match complex structures in ontologies. While many matching tools tackle simple ontology matching, complex ontology matching is still rare. However, one entity in one ontology can be similar to a complex structure (1-to-n) or even complex structures can be on both sides (m-to-n). Therefore, the application, e.g., data integration, must consider complex correspondences within ontology alignment. Our poster paper presents a pattern-based approach where particular SPARQL queries correspond to a specific pattern, e.g., Class by Attribute Type (CAT), for its detection. SPARQL queries are anchored to entities from simple correspondences on input. Detected complex correspondence candidates are verbalized to be validated by the Large Language Model (LLM). Further, we provide a zero-shot prompting preliminary experiment and evaluation. The poster paper is equipped with the Jupyter notebook for automation of the pipeline and the full report of the experiment at: https://github.com/OndrejZamazal/ComplexOntologyMatching-SEMANTiCS2024</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>Sharing domain knowledge is often made via domain ontology <ref type="bibr" target="#b2">[3]</ref>. Since different agents see the domain differently, more ontologies for one domain are inevitable. To enable interoperability, Ontology Matching <ref type="bibr" target="#b1">[2]</ref> aims at discovering relationships (e.q., equivalence) between entities of ontologies (O1, O2) called correspondences (alignment). Correspondences involve a single entity from each ontology, e.g., O1:Document=O2:Manuscript. This correspondence can enable data interoperability between systems based on O1 and O2 resp. There are ample matching tools, such as LogMap <ref type="bibr" target="#b5">[6]</ref>, to discover such correspondences. However, correspondences targeting single entities can only solve some interoperability issues. E.g., O1 has an entity Reviewer which is not explicitly in the O2, but still, O2 contains the terminology to describe the Reviewer concept. Therefore, discovering complex correspondence would further support data and schema interoperability: e.g., partly in Manchester OWL syntax, O1:Reviewer is equal to the complex concept O2:Person and (O2:authorOf some O2:Review). Complex ontology matching aims at matching complex concepts/structures (e.g., using a logic constructor) on at least one side of an ontology matching pair <ref type="bibr" target="#b10">[11]</ref>. While ontology matching attracted ample ontology matching tools and evaluation efforts (e.g., OAEI 2023<ref type="foot" target="#foot_0">1</ref> had ten tracks targetting simple matching), only one OAEI 2023 track focused on complex matching; even without tool participation in 2023. There have been two complex alignment benchmarks in OAEI so far: the GeoLink complex alignment benchmark <ref type="bibr" target="#b13">[14]</ref> and the consensual dataset for complex ontology matching <ref type="bibr" target="#b11">[12]</ref> based on conference ontologies from the OntoFarm collection <ref type="bibr" target="#b12">[13]</ref>.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.">Related Work</head><p>Several approaches have dealt theoretically with complex ontology matching, mostly patternbased approaches <ref type="bibr" target="#b10">[11]</ref>. For example, <ref type="bibr" target="#b7">[8]</ref> detects complex correspondences using several structural and lexical matching conditions, such as hyponyms and head-nouns of labels and their relationship. Similarly, in <ref type="bibr" target="#b9">[10]</ref>, the detection of the naming aspect played a crucial role. Our approach relies on the pattern-based, structural aspect, but we do not use the lexical aspect for detection. While corresponding structural matching conditions are usually straightforward, designing and applying lexical matching conditions is often challenging. We avoid using the lexical aspects during the detection phase, but we use verbalization and Large Language Model (LLM) for the validation step.</p><p>LLMs have already been applied for simple ontology matching. Conference ontologies have been matched using Chat-GPT <ref type="bibr" target="#b6">[7]</ref>. While the OLaLa matching system <ref type="bibr" target="#b4">[5]</ref> addressed more tracks within OAEI, the approach <ref type="bibr" target="#b3">[4]</ref> targeted the Bio-ML track in OAEI. While there is still room for improvement, the initial results are promising. Recently, an approach of complex ontology alignment using LLMs has been proposed <ref type="bibr" target="#b0">[1]</ref>. It works on the GeoLink complex alignment benchmark where two ontologies are included: the GeoLink Base Ontology (GBO) and the GeoLink Modular Ontology (GMO). Their approach is based on chain-of-thought prompting. On input there is GMO ontology and specific complex structure from GBO ontology with a prompt to give related parts in the GMO to the given complex structure from GBO. The following prompt contains parts of related content from the GMO in text and the code (module information). It makes LLM's answer more proper. The paper primarily addresses the experiment with a very specific setting. We share a general idea that LLM could reduce the number of candidates that humans could finally validate. However, the approach <ref type="bibr" target="#b0">[1]</ref> heavily involves human intervention in each step. On contrary, we do not include humans for prompting and we include SPARQL for detection. Next, we do not restrict complex matching on manually selected complex structure instances of one ontology on input. Our approach is instead driven by an alignment pattern.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">Approach</head><p>We describe our pattern-based pipeline along with an example (in italics) targeting the alignment pattern Class by Attribute Type (CAT) <ref type="bibr" target="#b8">[9]</ref>. This pattern specifies equivalence between a class in O1 and a class in O2 restricted on its scope using existential restriction; in Manchester OWL syntax: O1:Class1 EquivalentTo O2:Class1 and (O2:property some O2:Class2).</p><p>Often, ontology matching techniques limit the search space. We use simple alignment and limit complex matching to entities in complex structures related to entities from simple alignment. We assume that potential matching complex structures involves entities from simple correspondences.</p><p>Input ontologies are conference ontologies: O1=cmt, O2=ekaw. For input alignment, we used the subset of the alignment from LogMap OAEI 2023 (O1:Paper=O2:Paper; O1:Person=O2:Person) to keep the experiment shorter. Any highly certain correspondences could be used.</p><p>Step 1. Detection is based on a structural aspect. We use a pair of SPARQL queries designed according to given alignment pattern for O1 and O2, resp. <ref type="foot" target="#foot_1">2</ref> One alignment pattern can lead to different structural aspects for detection (i.e., different SPARQL queries) in O1 or O2, resp. Some entities in SPARQL queries are anchored based on input alignment.  Step 2. Results from detecting both ontologies are joined according to the alignment pattern separately per each input correspondence.</p><p>In our example, there are 4 ×2=8 complex correspondence candidates for the Paper entity from input correspondence and 14 ×7=98 complex correspondence candidates for the Person entity from input correspondence. E.g., regarding the first input correspondence, O1:Person=O2:Person, O1:Reviewer is joined with O2:Person, O2:authorOf, and O2:Review.</p><p>Step 3. Pattern-based template-driven verbalization to natural language (English) is applied to complex correspondence candidates to enable their validation using LLM. We also apply several natural language preprocessing steps, such as tokenization and lowercasing. Similarly, we use a template for serialization into Manchester OWL syntax.</p><p>For CAT, we have the following verbalization pattern into English: "&lt;O1:class1&gt; is the same as &lt;O2:ent1&gt; which is<ref type="foot" target="#foot_2">3</ref> &lt;O2:property1&gt; of &lt;O2:class2&gt;". Example: Reviewer is the same as person which is author of review.</p><p>Step 4. Finally, LLM is used to validate whether verbalized complex correspondence candidates are (probably) positives/negatives.</p><p>We experimented with different LLMs. So far, the best results have been achieved using GPT-4o. <ref type="foot" target="#foot_3">4</ref></p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.">Preliminary Experiment and Evaluation</head><p>The experiment is related to step 4. LLM is used to validate whether verbalized complex correspondence candidates are (probably) positives/negatives. Our online supplementary material contains the full report (SPARQL queries, their results and their joints, verbalized complex correspondence candidates, the prompt for GPT-4o,<ref type="foot" target="#foot_4">5</ref> its results, evaluation, complex correspondences in EDOAL and Manchester OWL syntax). Of 106 candidates, 14 were labeled as negatives, 74 as probably negatives, ten as probably positives, and eight as positives. The supplementary material contains a detailed evaluation of all eight candidates labeled by LLM as positives. As a result of eight candidates' evaluations by human, there were one true positive, one partly true positive, and six partly false positives. For the sake of brevity, here we present three evaluation examples: 1. Reviewer is the same as person which is author of review.</p><p>Although it is debatable whether being an author of a review is enough to be a real reviewer, it is certainly close enough. It was evaluated as a true positive.</p><p>2. Meta-reviewer is the same as person which is author of review. Meta-reviewer is not only the author of the review but (s)he has a specific role within a reviewing process. A meta-reviewer is instead a subclass of person which is an author of review, i.e., Class ⊑ Class Expression. It was evaluated as a partly true positive example.</p><p>3. Author is the same as person which is author of abstract.</p><p>Since some conferences call for abstracts, being an author can be merely based on abstract authorship. However, the subsumption relation would be more fitting (i.e., Author subsumes person which is author of abstract). Since it leads to General Concept Inclusion (GCI) subsumption, i.e., Class ⊒ Class Expression, being not always allowed, it was evaluated as partly false positive.</p><p>Considering only equivalence, precision equals 1 8 = 0.125. However, subsumption is also important for interoperability, meaning relaxed precision (𝑃 𝑟 ) could be used. If GCI axioms (partly false positives) are not allowed, 𝑃 𝑟 = 2 8 = 0.25. If GCI axioms are allowed, <ref type="foot" target="#foot_5">6</ref> 𝑃 𝑟 = 1.0. Regarding recall, the preliminary evaluation (details in the online supplementary material) shows that all negatives are true. However, it needs further evaluation in terms of relaxed recall.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.">Conclusion and Future Work</head><p>We reported on our approach and preliminary experiments with pattern-based complex ontology matching using SPARQL for detection and verbalization before validation with LLM.</p><p>Similarly to <ref type="bibr" target="#b7">[8]</ref>, we focus on the structural aspect of detection. In contrast, we do not capture lexical aspects for detection while employing verbalization before validation by LLM. Similarly to <ref type="bibr" target="#b0">[1]</ref>, we employ LLM for complex ontology matching, but we only use it in the final step of the approach for validation. Contrary to <ref type="bibr" target="#b0">[1]</ref>, we do not involve humans in prompting, complete ontology, pre-selected complex structure instances to be matched, nor manually selected additional information for complex matching.</p><p>For now, we consider a 1-to-n relationship. However, it can be generalized to an m-to-n relationship. In our experiments, we use GPT-4o. However, we will experiment more with other LLMs (e.g., Llama 3, Mixtral). Further, while we employ direct question prompting, we will also experiment with contextual question prompting, where context will be gathered automatically. We aim to explore more alignment patterns, involve more ontologies, and conduct in-depth evaluations in future work. While the provided Jupyter notebook covers three steps, the fourth step, dealing with LLM, will be implemented after further experimentation with other LLMs.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Figure 1 :</head><label>1</label><figDesc>Figure 1: SPARQL queries for the CAT pattern.</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Figure 1</head><label>1</label><figDesc>Figure 1 consists of a visualization of SPARQL queries for O1 and O2 for CAT, and the correspondence from input alignment is depicted as a both-sided arrow. The detection is run for each correspondence from input alignment. In our case, 4 and 7 SPARQL results for O1 per input correspondence and 2 and 14 SPARQL results for O2 per input correspondence resp.; Example for O1 given Person (?ent1) from input correspondence: O1:Class1=Reviewer. Example for O2 given Person (?ent1) from input correspondence: O2:property1=authorOf, O2:class1=Document, O2:class2=Review.Step 2. Results from detecting both ontologies are joined according to the alignment pattern separately per each input correspondence.In our example, there are 4 ×2=8 complex correspondence candidates for the Paper entity from input correspondence and 14 ×7=98 complex correspondence candidates for the Person entity from input correspondence. E.g., regarding the first input correspondence, O1:Person=O2:Person, O1:Reviewer is joined with O2:Person, O2:authorOf, and O2:Review.Step 3. Pattern-based template-driven verbalization to natural language (English) is applied to complex correspondence candidates to enable their validation using LLM. We also apply several natural language preprocessing steps, such as tokenization and lowercasing. Similarly, we use a template for serialization into Manchester OWL syntax.For CAT, we have the following verbalization pattern into English: "&lt;O1:class1&gt; is the same as &lt;O2:ent1&gt; which is 3 &lt;O2:property1&gt; of &lt;O2:class2&gt;". Example: Reviewer is the same as person which is author of review.</figDesc><graphic coords="3,141.38,218.09,312.53,108.67" type="bitmap" /></figure>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="1" xml:id="foot_0">https://oaei.ontologymatching.org/2023/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="2" xml:id="foot_1">The approach is pattern-based in two ways: because it is driven by the alignment pattern and because the SPARQL query can also be considered as a pattern for detection.</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="3" xml:id="foot_2">If no "has" exists in property1, "is" is added.</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="4" xml:id="foot_3">via https://chatgpt.com/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="5" xml:id="foot_4">We ran the GPT-4o several times with minor changes in its reply; it is not substantial for the evaluation.</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="6" xml:id="foot_5">GCI subsumptions could also help with interoperability within some scenarios.</note>
		</body>
		<back>

			<div type="acknowledgement">
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Acknowledgments</head><p>This work has been supported by the EU's Horizon Europe grant no. 101058682 (Onto-DESIDE).</p></div>
			</div>

			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<monogr>
		<title level="m" type="main">Towards Complex Ontology Alignment using Large Language Models</title>
		<author>
			<persName><forename type="first">R</forename><surname>Amini</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><forename type="middle">S</forename><surname>Norouzi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Hitzler</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Amini</surname></persName>
		</author>
		<idno type="arXiv">arXiv:2404.10329.2024</idno>
		<imprint>
			<date type="published" when="2024">2024</date>
		</imprint>
	</monogr>
	<note type="report_type">arXiv preprint</note>
</biblStruct>

<biblStruct xml:id="b1">
	<monogr>
		<title level="m" type="main">Ontology matching</title>
		<author>
			<persName><forename type="first">J</forename><surname>Euzenat</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Shvaiko</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2013">2013</date>
			<publisher>Springer</publisher>
			<biblScope unit="page" from="978" to="981" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">Toward principles for the design of ontologies used for knowledge sharing?</title>
		<author>
			<persName><forename type="first">T</forename><forename type="middle">R</forename><surname>Gruber</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">International journal of human-computer studies</title>
		<imprint>
			<biblScope unit="volume">43</biblScope>
			<biblScope unit="page" from="5" to="6" />
			<date type="published" when="1995">1995</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<title level="a" type="main">Exploring large language models for ontology alignment</title>
		<author>
			<persName><forename type="first">Y</forename><surname>He</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Chen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Dong</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename><surname>Horrocks</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">ISWC 2023 Posters, and Demos</title>
				<imprint>
			<date type="published" when="2023">2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">OLaLa: Ontology matching with large language models</title>
		<author>
			<persName><forename type="first">S</forename><surname>Hertling</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Paulheim</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proc. of the 12th Knowledge Capture Conference</title>
				<meeting>of the 12th Knowledge Capture Conference</meeting>
		<imprint>
			<date type="published" when="2023">2023. 2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">Logmap: Logic-based and scalable ontology matching</title>
		<author>
			<persName><forename type="first">E</forename><surname>Jiménez-Ruiz</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Cuenca Grau</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">International Semantic Web Conference</title>
				<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2011">2011</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">Conversational Ontology Alignment with ChatGPT</title>
		<author>
			<persName><forename type="first">S</forename><forename type="middle">S</forename><surname>Norouzi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">S</forename><surname>Mahdavinejad</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Hitzler</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proc. of the Ontology Matching workshop at ISWC</title>
				<meeting>of the Ontology Matching workshop at ISWC</meeting>
		<imprint>
			<date type="published" when="2023">2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">Linguistic analysis for complex ontology matching</title>
		<author>
			<persName><forename type="first">D</forename><surname>Ritze</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Völker</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Meilicke</surname></persName>
		</author>
		<author>
			<persName><forename type="first">O</forename><surname>Šváb-Zamazal</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proc. of the Ontology Matching workshop at ISWC</title>
				<meeting>of the Ontology Matching workshop at ISWC</meeting>
		<imprint>
			<date type="published" when="2010">2010</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<monogr>
		<title level="m" type="main">Correspondence patterns representation</title>
		<author>
			<persName><forename type="first">F</forename><surname>Scharffe</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2009">2009</date>
		</imprint>
		<respStmt>
			<orgName>Univ. of Innsbruck</orgName>
		</respStmt>
	</monogr>
	<note type="report_type">PhD thesis</note>
</biblStruct>

<biblStruct xml:id="b9">
	<analytic>
		<title level="a" type="main">Towards ontology matching via pattern-based detection of semantic structures in OWL ontologies</title>
		<author>
			<persName><forename type="first">O</forename><surname>Šváb-Zamazal</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Svátek</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proc. of the Znalosti conference</title>
				<meeting>of the Znalosti conference</meeting>
		<imprint>
			<date type="published" when="2009">2009</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<analytic>
		<title level="a" type="main">Survey on complex ontology matching</title>
		<author>
			<persName><forename type="first">E</forename><surname>Thiéblin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">O</forename><surname>Haemmerlé</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Hernandez</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Trojahn</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Semantic Web</title>
		<imprint>
			<biblScope unit="volume">11</biblScope>
			<biblScope unit="issue">4</biblScope>
			<date type="published" when="2020">2020</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<analytic>
		<title level="a" type="main">A consensual dataset for complex ontology matching evaluation</title>
		<author>
			<persName><forename type="first">E</forename><surname>Thiéblin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Cheatham</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Trojahn</surname></persName>
		</author>
		<author>
			<persName><forename type="first">O</forename><surname>Zamazal</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">The Knowledge Engineering Review</title>
		<imprint>
			<biblScope unit="volume">35</biblScope>
			<biblScope unit="page">e34</biblScope>
			<date type="published" when="2020">2020</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<analytic>
		<title level="a" type="main">The ten-year ontofarm and its fertilization within the onto-sphere</title>
		<author>
			<persName><forename type="first">O</forename><surname>Zamazal</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Svátek</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Journal of Web Semantics</title>
		<imprint>
			<biblScope unit="volume">43</biblScope>
			<date type="published" when="2017">2017</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b13">
	<analytic>
		<title level="a" type="main">Geolink data set: A complex alignment benchmark from real-world ontology</title>
		<author>
			<persName><forename type="first">L</forename><surname>Zhou</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Cheatham</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Krisnadhi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Hitzler</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Data Intelligence</title>
		<imprint>
			<biblScope unit="volume">2</biblScope>
			<biblScope unit="issue">3</biblScope>
			<date type="published" when="2020">2020</date>
		</imprint>
	</monogr>
</biblStruct>

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