<?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 Building a Link Set Backed by Domain Experts using the Alignment Tool</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="department">Dept. Information and Knowledge Engineering</orgName>
								<orgName type="institution">University of Economics</orgName>
								<address>
									<settlement>Prague</settlement>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Sotirios</forename><surname>Karampatakis</surname></persName>
							<affiliation key="aff1">
								<orgName type="department">School of Mathematics</orgName>
								<orgName type="institution">Aristotle University of Thessaloniki</orgName>
							</affiliation>
							<affiliation key="aff2">
								<orgName type="department">Open Knowledge Greece</orgName>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Charalampos</forename><surname>Bratsas</surname></persName>
							<affiliation key="aff1">
								<orgName type="department">School of Mathematics</orgName>
								<orgName type="institution">Aristotle University of Thessaloniki</orgName>
							</affiliation>
							<affiliation key="aff2">
								<orgName type="department">Open Knowledge Greece</orgName>
							</affiliation>
						</author>
						<title level="a" type="main">Towards Building a Link Set Backed by Domain Experts using the Alignment Tool</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">1F53EED5DC0E7C2F1132952706D18305</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-24T09: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>
			<abstract/>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1">Introduction</head><p>Discovering semantic relations between entities (entity linking) is one of the most important activity for both semantic web and linked data areas. Either we need link sets of instances or concepts we can rely on automatic systems only to a certain extent. As a result, an automatic linking is accompanied with a user interaction which enables to increase the quality of resulted link sets. Often, in order to reach as much quality of link set as possible the user should be a domain expert for an area of linking task [1]. This user specifics should be considered by designers of interactive entity linking tools. This work presents an experience from an experiment of building a link set for two fiscal code lists where domain experts have been involved. The experiment has been done using the Alignment tool. <ref type="bibr">45</ref> </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2">The Alignment Tool</head><p>While the Alignment tool is now a general linking tool, it has originally been developed in order to facilitate linking heterogeneous fiscal code lists in the OpenBudgets project. It is a web application for online, collaborative, system aided manual entity linking. The tool can be used to manually create link sets between two knowledge graphs or to validate already existing link sets. It further offers a number of utilities to aid the linking such as a graph visualization as a tree, a search bar, an entity description and finally suggestions based on linking algorithms provided by Silk [2] or by other automated linking tools. Multiple users can work on the same linking project simultaneously, thus enabling crowdsourcing of a link set creation and reducing required time and effort.</p><p>The user can select a semantic meaning of the link by selecting from a number of predefined link types (e.g skos:related,<ref type="foot" target="#foot_2">6</ref> skos:broadMatch, owl:sameAs etc.) or provide a custom one. The tool can also be used to crowdsource a link validation using a voting system. You can upload links produced by an automated procedure or the tool itself and create polls to check eligibility. Finally, link sets can be exported in various RDF formats and CSV.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3">Building a Link Set by Involving Domain Experts</head><p>European union countries often apply their own different categorization systems for funded projects. As a consequence, this hinders straightforward fiscal analyses. Since there is already integrated European categorization system for funded projects, one of possible solutions to enhance fiscal analyses is to interlink categorization systems of individual EU countries to the European one. For improving this situation we started with building the one link set, the Czech code list (44 items) to the European one (142 items). <ref type="bibr" target="#b2">7</ref> In order to ensure the quality of the link set we involved two domain experts and we used the Alignment tool. Thus this work enabled us testing the Alignment tool in action and examining the task of interlinking code lists with domain experts.</p><p>Our two domain experts worked separately. They followed detail guidelines 8 where they were informed about the goal of correctly interlinking as many source items to target items as possible. The guidelines also includes a brief manual how to use the Alignment tool and the instruction that experts should prefer certain types of links more, i.e. there was the following preference skos:exactMatch, then skos:narrowMatch and skos:broadMatch and then the others.</p><p>Both experts interlinked 32 same items where expert 1 linked 84% (37) items from the source code list and expert 2 linked 82% (36) items from the source code list. While the expert 1 employed all skos link types (out of all 53 links) more or less uniformly (21 skos:narrowMatch, 11 skos:closeMatch, 9 skos:exactMatch, 8 skos:relatedMatch, 4 skos:broadMatch), the expert 2 created mainly skos:narrowMatch links (116), additionally 8 skos:exactMatch and 1 skos:broadMatch, out of all 125 links. Both experts managed 32 times to linked the same two entities in one link and, more importantly, they managed to create the very same link 23 times where there were 7 skos:exactMatch, 1 skos:broadMatch and 15 skos:narrowMatch. <ref type="bibr" target="#b3">9</ref> The resulted link set of 23 links represents the nucleus of the reference link set. Since there are many links created by only one expert (57% in the case of expert 1 and 82% in the case of expert 2) we further plan to let experts discuss those not agreed links to extend the current reference link set.</p><p>During the interlinking by experts we continually received a feedback in terms of bugs and improvement suggestions for the Alignment tool as also reflected via GitHub.</p></div>			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="4" xml:id="foot_0">http://alignment.okfn.gr/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="5" xml:id="foot_1">https://github.com/okgreece/Alignment/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="6" xml:id="foot_2">Skos prefix refers to http://www.w3.org/2004/02/skos/core# namespace.</note>
		</body>
		<back>

			<div type="acknowledgement">
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Acknowledgments</head><p>We thank to experts. The work has been supported by the H2020 project no. 645833.</p></div>
			</div>

			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">User validation in ontology alignment</title>
		<author>
			<persName><forename type="first">Z</forename><surname>Dragisic</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Ivanova</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Lambrix</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Faria</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Jimnez-Ruiz</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Pesquita</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">International Semantic Web Conference</title>
				<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2016">2016</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<monogr>
		<title level="m" type="main">Silk-A Link Discovery Framework for the Web of Data</title>
		<author>
			<persName><forename type="first">J</forename><surname>Volz</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Bizer</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Gaedke</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Kobilarov</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2009">2009</date>
			<publisher>LDOW</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<monogr>
		<title level="m" type="main">Both code lists are extracted from existing data sets</title>
		<imprint/>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<monogr>
		<ptr target="http://owl.vse.cz:8080/OM2017/" />
		<title level="m">The further information</title>
				<imprint/>
	</monogr>
</biblStruct>

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