<?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">Koala-UI: An Interactive User Interface for Tabular Data Linking</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Roberto</forename><surname>Avogadro</surname></persName>
							<email>roberto.avogadro@sintef.no</email>
							<affiliation key="aff0">
								<orgName type="institution">SINTEF AS</orgName>
								<address>
									<addrLine>POB 124, Blindern</addrLine>
									<postCode>0314</postCode>
									<settlement>Oslo</settlement>
									<country key="NO">Norway</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Iroshani</forename><surname>Jayawardene</surname></persName>
							<email>iroshani.jayawardene@sintef.no</email>
							<affiliation key="aff0">
								<orgName type="institution">SINTEF AS</orgName>
								<address>
									<addrLine>POB 124, Blindern</addrLine>
									<postCode>0314</postCode>
									<settlement>Oslo</settlement>
									<country key="NO">Norway</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Xiang</forename><surname>Ma</surname></persName>
							<email>xiang.ma@sintef.no</email>
							<affiliation key="aff0">
								<orgName type="institution">SINTEF AS</orgName>
								<address>
									<addrLine>POB 124, Blindern</addrLine>
									<postCode>0314</postCode>
									<settlement>Oslo</settlement>
									<country key="NO">Norway</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Ahmet</forename><surname>Soylu</surname></persName>
							<email>ahmet.soylu@kristiania.no</email>
							<affiliation key="aff1">
								<orgName type="institution">Kristiania University College</orgName>
								<address>
									<settlement>Oslo</settlement>
									<country key="NO">Norway</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Dumitru</forename><surname>Roman</surname></persName>
							<email>dumitru.roman@sintef.nod.roman</email>
							<affiliation key="aff0">
								<orgName type="institution">SINTEF AS</orgName>
								<address>
									<addrLine>POB 124, Blindern</addrLine>
									<postCode>0314</postCode>
									<settlement>Oslo</settlement>
									<country key="NO">Norway</country>
								</address>
							</affiliation>
							<affiliation key="aff2">
								<orgName type="institution">OsloMet-Oslo Metropolitan University</orgName>
								<address>
									<settlement>Oslo</settlement>
									<country key="NO">Norway</country>
								</address>
							</affiliation>
						</author>
						<author>
							<affiliation key="aff3">
								<address>
									<settlement>Bucharest</settlement>
									<country key="RO">Romania</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Koala-UI: An Interactive User Interface for Tabular Data Linking</title>
					</analytic>
					<monogr>
						<idno type="ISSN">1613-0073</idno>
					</monogr>
					<idno type="MD5">25FE95901B385568B97669E9443B1729</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2025-04-23T18:27+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>Entity Linking</term>
					<term>Data Enrichment</term>
					<term>Data Pipelines</term>
					<term>User Interfaces</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>This paper introduces Koala-UI -a user interface system aimed at simplifying the entity linking process within data enrichment pipelines. Koala-UI provides an intuitive mechanism for linking entities across datasets, combining automation with human feedback to ensure accurate and consistent data. Koala-UI was successfully applied in use cases such as public procurement, where it enabled enrichment of a tenders dataset by linking entities to external knowledge graphs. Future developments will focus on expanding its backend to support additional models and enhance its human-in-the-loop capabilities.</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>In today´s rapidly evolving data-driven world, organizations are increasingly relying on large and complex datasets, particularly in tabular form, to make strategic decisions. A critical step in effectively leveraging such data is tabular data linking, where entities in different tables are identified and connected to their corresponding records in external reference knowledge bases. This process is essential for ensuring consistency, accuracy, and completeness of enriched datasets, which, in turn, supports tasks such as analytics, compliance monitoring, and artificial intelligence-driven applications <ref type="bibr" target="#b0">[1,</ref><ref type="bibr" target="#b1">2,</ref><ref type="bibr" target="#b2">3,</ref><ref type="bibr" target="#b3">4,</ref><ref type="bibr" target="#b4">5]</ref>.</p><p>Tabular data linking presents several challenges, particularly when dealing with large-scale or heterogeneous tables. Inconsistent naming conventions, ambiguous references, and evolving organizational structures can make it difficult to reconcile entities accurately <ref type="bibr" target="#b5">[6,</ref><ref type="bibr" target="#b6">7,</ref><ref type="bibr" target="#b7">8]</ref>. Traditional methods, which often rely on rule-based systems or manual intervention, are inefficient and do not scale well to modern big data environments. Therefore, there is a growing demand for intuitive, user-friendly tools that allow both technical and non-technical users to perform complex data linking tasks with minimal effort while maintaining control over the results. This is where Koala-UI becomes a valuable asset.</p><p>Koala-UI is an interactive user interface designed specifically to address the complexities of tabular data linking in large datasets. It provides a streamlined, intuitive interface that simplifies the process of linking entities across tables, while integrating human feedback to ensure high accuracy. By leveraging automation and offering real-time feedback, Koala-UI helps organizations efficiently manage large volumes of tabular data, ensuring that the enriched data is well-prepared for further analysis or downstream applications.</p><p>This paper presents the design, implementation, and real-world application of Koala-UI. It explores how this tool enables scalable and efficient tabular data linking and highlights its key features, including human-in-the-loop verification, automated entity linking, and robust data handling capabilities for large datasets. The role of Koala-UI within a broader data enrichment ecosystem is also discussed, showcasing its value in real-world use cases such as public procurement, where it was utilized to reconcile and enrich tender data.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.">Related Work</head><p>Entity linking plays an important role in data enrichment, enabling the association of entities in a dataset with their corresponding counterparts in external knowledge bases. Several techniques and associated tools were developed to streamline this process, offering varying levels of functionality, user interface design, and integration with external services.</p><p>SemTUI<ref type="foot" target="#foot_0">1</ref> is a modular framework aimed at enhancing the semantic enrichment of tabular data <ref type="bibr" target="#b8">[9]</ref>. It provides a flexible interface for instance-level and schema-level annotations by integrating with multiple external services, including reconciliation and extension systems. The tool's modular design allows for easy customization, making it adaptable to a wide range of data enrichment needs, particularly in more complex scenarios <ref type="bibr" target="#b9">[10,</ref><ref type="bibr" target="#b10">11]</ref>.</p><p>OpenRefine <ref type="foot" target="#foot_1">2</ref> is another popular open-source tool, well-known for its data cleaning and transformation capabilities. It includes features for linking datasets to external databases such as Wikidata. While primarily focused on data cleaning <ref type="bibr" target="#b11">[12]</ref>, OpenRefine also offers reconciliation services for entity linking <ref type="bibr" target="#b12">[13]</ref>, though its specialization in this area is more limited compared to tools that are designed specifically for entity linking tasks.</p><p>DataGraft<ref type="foot" target="#foot_2">3</ref> offers an accessible platform for managing, transforming, and linking data. It supports linking entities to external knowledge graphs and provides a variety of data transformation tools, similar to OpenRefine <ref type="bibr" target="#b13">[14]</ref>. DataGraft's user interface is designed to accommodate both technical and non-technical users, making it a versatile option for data linking tasks <ref type="bibr" target="#b14">[15]</ref>. Its emphasis on user experience and ease of integration across diverse data sources positions it as a notable option in the field.</p><p>Despite the versatility and functionalities offered by such tools, they still present limitations when handling large-scale datasets or providing detailed interaction options for users. Koala-UI addresses these gaps by offering a user-friendly interface that is simple to use while capable of managing large tables efficiently, thanks to its paginated results feature. The tool further enhances the user experience by providing instruments to explore and refine entity linking results, such as candidate scores, sorting by confidence, and filtering by types. Additionally, it enables users to manually search for potential matches by typing strings, allowing for greater flexibility. Another advantage of Koala-UI is its ability to integrate with various backends, as long as they follow a consistent API response format, making it adaptable to a wide range of entity linking services.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">Koala-UI Overview</head><p>Koala-UI <ref type="foot" target="#foot_3">4</ref> is an interactive web interface designed to simplify the entity linking process, enabling the integration of data from diverse sources into enriched datasets. A demo video of Koala-UI is available on YouTube<ref type="foot" target="#foot_4">5</ref> , which showcases its core functionalities and user interface. Its primary goal is to make complex entity linking tasks accessible to users without extensive technical expertise, improving the quality and consistency of data for downstream applications such as analytics and decision-making.</p><p>Koala-UI was developed to support scalable and efficient data enrichment workflows. The design focuses on user-friendliness, automation, and flexibility, ensuring the platform can be applied in various scenarios and domains.</p><p>The following subsections introduce Koala-UI's design principles and core features, including usability, scalability, and human-in-the-loop verification, highlighting how these elements enable efficient entity linking for large datasets.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.1.">Design Principles</head><p>The design of Koala-UI is guided by the following principles:</p><p>• Usability: The interface was built with a user-first approach, ensuring that users with varying technical expertise can interact with the tool efficiently. Koala-UI's interface simplifies complex entity linking tasks by providing intuitive UI components, visual cues, and real-time feedback, making the process as straightforward as possible. • Scalability: Koala-UI was designed to handle large-scale datasets efficiently. The architecture ensures that performance remains high even when processing thousands of records, making it suitable for applications involving large volumes of data across diverse domains. • Flexibility: Koala-UI was built with extensibility in mind. Future versions aim to support additional models and algorithms that can be easily plugged in, allowing users to adapt the tool to various entity linking scenarios and data enrichment needs. • Human-Centric Interaction: The design emphasizes the role of human users in verifying and improving entity linking accuracy. The system is structured to allow users to provide feedback at critical points in the entity matching process, improving overall data quality.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.2.">Core Features</head><p>Koala-UI offers a range of features to streamline and improve the entity linking process:</p><p>• Interactive Visualization: Users are provided with real-time visual feedback on the entity linking process, including visual indicators for matches, confidence scores, and unresolved entities. This enables users to make informed decisions about entity verification and ensures data quality is maintained. • Automated Entity Linking: The system uses advanced algorithms to automate much of the entity linking workflow, significantly reducing the need for manual intervention. The system provides confidence scores for each link, helping users focus on matches that need human validation. • Human-in-the-Loop Verification: Koala-UI balances automation with human expertise by incorporating a verification mechanism. Users can review suggested entity links and correct or confirm matches, ensuring that the system learns and improves from user feedback. • Data Management for Large Datasets: Koala-UI is optimized for large datasets, employing techniques such as lazy loading and efficient memory management. This ensures that users can manage and enrich large tables with minimal performance bottlenecks, making it suitable for industrial-scale applications.</p><p>Figure <ref type="figure" target="#fig_0">1</ref> presents the splash screen of Koala-UI. Figure <ref type="figure" target="#fig_1">2</ref> illustrates the entity matches along with their respective confidence scores, and Figure <ref type="figure" target="#fig_2">3</ref> highlights the type details extracted from a specific column.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.">Implementation</head><p>Koala-UI was implemented using a combination of frontend and backend technologies designed to ensure scalability, efficiency, and ease of use. While the backend manages user-specific data, the core data enrichment tasks, such as entity linking, are handled through external APIs integrated directly into the frontend.  The frontend of Koala-UI was built using React<ref type="foot" target="#foot_5">6</ref> toensure a responsive and user-friendly interface. The design allows users to interact with the tool seamlessly across different platforms. Visual feedback, such as confidence scores and entity match suggestions, helps users efficiently assess and verify the quality of the entity linking process.</p><p>Koala-UI integrates two key external services within the frontend:</p><p>• Alligator <ref type="bibr" target="#b15">[16]</ref>, used for entity linking, accessed via its paginated API <ref type="foot" target="#foot_6">7</ref> . The API returns annotated tables as output, and data is processed incrementally using MongoDB. The paginated system allows Koala-UI to handle large datasets over time by breaking down responses into manageable parts, which can be processed one page at a time. • LAMAPI <ref type="bibr" target="#b16">[17]</ref> provides functionality for manually looking up entities by typing a string. This feature enables users to search for potential matches, offering greater flexibility when automated suggestions are insufficient.</p><p>Both services are called directly from the Koala-UI frontend, allowing it to handle entity linking and lookups without needing to process the data in its own backend.</p><p>The backend of Koala-UI is limited to managing user data. It supports the login system and stores data regarding different users, ensuring that user-specific settings and history are preserved across sessions.</p><p>The virtual machine (VM) running Alligator, which handles the bulk of the entity linking workload, was configured as follows:</p><p>• Memory: 30 GiB (16 GiB + 14 GiB DIMMs) { "data": { "datasetName": "Spend Network", "tableName": "SN", "header": [ "buyer", "aug_buyer_name", "aug_url", "aug_postal_town", "aug_administrative_area_level_2", "aug_administrative_area_level_1", "aug_country" ], "rows": [ { "idRow": 26, "data": [...] }, ... ] }, "pagination": { "currentPage": 1, "perPage": 10, "totalPages": 9, "totalItems": 86 } }</p><p>The response provides the table's header, row data, and the pagination information. The pagination object specifies the current page (currentPage), the number of rows per page (perPage), the total number of pages (totalPages), and the total number of items in the dataset (totalItems). This structure allows Koala-UI to load and process the dataset in chunks, ensuring efficient handling of large datasets.</p><p>In addition to pagination, Koala-UI uses frontend techniques such as lazy loading and caching. These techniques ensure that the interface remains responsive, even when processing substantial volumes of information. The system's ability to handle large-scale data processing is largely driven by MongoDB's incremental processing model, which is leveraged through Alligator.</p><p>By combining a responsive frontend, a user management backend, and integration with external APIs such as Alligator and LAMAPI, Koala-UI is able to manage both user-specific data and large datasets effectively.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.">Use Case: Koala-UI applied on tenders data</head><p>Koala-UI was applied in a use case involving the organization Spend Network<ref type="foot" target="#foot_7">8</ref> . The objective of this use case was to create a European register of public entities, consolidating public sector entities from across Europe. This register is intended to serve as a canonical index for both public and private sector stakeholders, supporting applications such as compliance monitoring, Know Your Customer (KYC) processes, and facilitating cross-departmental collaborations.</p><p>Spend Network collects tender and contract data from over 700 sources globally, standardizing this data to the Open Contracting Data Standard (OCDS). The goal is to create a detailed European register of public entities. A major challenge was reconciling and validating inconsistent, incomplete, or ambiguous entity data. For instance, different names or abbreviations might refer to the same organization (e.g., "CHU Rennes" and "Centre Hospitalier Universitaire de Rennes"). Additionally, organizations evolve over time, with entities merging, splitting or changing names, which complicates the entity reconciliation process.</p><p>Previously, Spend Network relied on manual, rule-based processes to manage this data, which limited the scalability and efficiency of the system. Expanding this register across Europe required a more automated approach, which Koala-UI provided through its entity linking capabilities. Koala-UI was used to reconcile entity names from tender data with external knowledge graphs such as Wikidata, helping to unify the various representations of the same entities. Its human-in-the-loop functionality allowed users to verify, review and adjust matches where necessary, ensuring a highe level of accuracy and consistency.</p><p>Using Koala-UI, Spend Network was able to:</p><p>• Reconcile entities like buyer names and URLs with knowledge graphs such as Wikidata.</p><p>• Enrich tender data with additional metadata sourced from knowledge graphs, such as geographic locations, administrative divisions, and other relevant data available in the external sources. • Process large datasets efficiently, handling thousands of tenders from different countries.</p><p>• Leverage human-in-the-loop features to allow users to manually verify and adjust automated suggestions.</p><p>The application of Koala-UI improved the accuracy and scalability of the entity linking process, making the register more comprehensive and reliable for use in analytics and decision-making. Figure <ref type="figure" target="#fig_3">4</ref> shows an annotated table that comes from the Spend Network use case.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="6.">Summary and Outlook</head><p>Koala-UI was developed with the vision of evolving into a modern tool for tabular data linking, with a focus on simplicity, ease of use, and the ability to efficiently manage large datasets. The primary design goals were to create a user-friendly interface that simplifies complex tasks, making it accessible to a wide range of users while ensuring it can handle the demands of large-scale tabular data.</p><p>Currently, Koala-UI relies on the Alligator API for handling scalability and large datasets. However, looking ahead, the next phase of Koala-UI's development will involve transitioning from Alligator to a dedicated Python library. This library will be designed to handle big data directly, allowing for more flexibility and control over the data linking process. Once this Python library is developed, it will be integrated into a backend, providing its functionalities via a unified API.</p><p>The modular approach envisioned for the future will support the integration of multiple Python libraries, each representing different algorithms. This will allow users to select from traditional entity linking methods or more advanced algorithms, such as those based on large language models (LLMs). By wrapping these libraries into a single backend, Koala-UI will offer a versatile solution capable of adapting to various data linking needs and evolving technologies.</p><p>Additionally, improvements to the pagination system are planned. Currently, pagination relies on MongoDB's skip operator, which slows down when processing large tables. Future updates will address this by restricting navigation to one page at a time, enhancing performance with large datasets. New search functionalities will also be introduced, allowing users to match specific keywords across entire tables, thus enabling more efficient data exploration.</p><p>A critical objective for the future is to implement a complete data enrichment lifecycle within Koala-UI that incorporates human feedback at various stages. This iterative approach will enable continuous improvements in entity linking and data processing, ensuring that Koala-UI evolves in response to new challenges and opportunities in the field of data enrichment.</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: Koala-UI splash screen.</figDesc><graphic coords="4,72.00,65.60,451.28,253.90" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Figure 2 :</head><label>2</label><figDesc>Figure 2: Koala-UI candidates details.</figDesc><graphic coords="4,72.00,358.79,451.28,237.75" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_2"><head>Figure 3 :</head><label>3</label><figDesc>Figure 3: Koala-UI types details.</figDesc><graphic coords="5,72.00,65.60,451.28,237.75" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_3"><head>Figure 4 :</head><label>4</label><figDesc>Figure 4: Koala-UI interface for entity linking in the spend network dataset.</figDesc><graphic coords="7,72.00,65.61,451.27,250.70" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_0"><head></head><label></label><figDesc>To handle large datasets efficiently, Alligator employs a paginated API system. This allows Koala-UI to request data incrementally, retrieving only a subset of the data per request. The following is an example of how paginated data for a table is retrieved via Alligator's API:In this request, data from the table SN of the Spend Network dataset is retrieved, with pagination parameters set to display 10 rows per page. The API responds with the table's data, including pagination details:</figDesc><table><row><cell>• CPU: AMD EPYC-Milan Processor, 8 cores, 2 GHz, 64-bit architecture</cell></row><row><cell>• Firmware: SeaBIOS, version 1.16.1-1.el9, 96KiB</cell></row><row><cell>• Vendor: KubeVirt (RHEL-9.2.0 PC)</cell></row><row><cell>• Disk: 944 GiB storage (EXT4 filesystem)</cell></row><row><cell>curl -X 'GET' 'https://alligator.hel.sintef.cloud/dataset/Spend%20Network/table/SN?page=1&amp;per_page=10&amp;token</cell></row><row><cell>=alligator_demo_2023' \</cell></row><row><cell>-H 'accept: application/json'</cell></row></table></figure>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="1" xml:id="foot_0">https://i2tunimib.github.io/I2T-docs</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="2" xml:id="foot_1">https://openrefine.org</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="3" xml:id="foot_2">https://www.eubusinessgraph.eu/datagraft</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="4" xml:id="foot_3">https://github.com/enRichMyData/koala_ui</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="5" xml:id="foot_4">https://www.youtube.com/watch?v=4Nc8bMBQpyE</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="6" xml:id="foot_5">https://react.dev</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="7" xml:id="foot_6">https://github.com/unimib-datAI/alligator</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="8" xml:id="foot_7">https://www.spendnetwork.com</note>
		</body>
		<back>

			<div type="acknowledgement">
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Acknowledgments</head><p>The work in this paper received partial funding from the projects enRichMyData (HE 101070284), Graph-Massivizer (HE 101093202) and UPCAST (HE 101093216).</p></div>
			</div>

			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">Enhancing security in cloud computing using artificial intelligence (ai)</title>
		<author>
			<persName><forename type="first">D</forename><surname>Stutz</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">T</forename><surname>De Assis</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">A</forename><surname>Laghari</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">A</forename><surname>Khan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Andreopoulos</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Terziev</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Deshpande</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Kulkarni</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><forename type="middle">G</forename><surname>Grata</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Applying Artificial Intelligence in Cybersecurity Analytics and Cyber Threat Detection</title>
		<imprint>
			<biblScope unit="page" from="179" to="220" />
			<date type="published" when="2024">2024</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">Artificial intelligence, cyber-threats and industry 4.0: Challenges and opportunities</title>
		<author>
			<persName><forename type="first">A</forename><surname>Bécue</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename><surname>Praça</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Gama</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Artificial Intelligence Review</title>
		<imprint>
			<biblScope unit="volume">54</biblScope>
			<biblScope unit="page" from="3849" to="3886" />
			<date type="published" when="2021">2021</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">Artificial intelligence-driven real-world battery diagnostics</title>
		<author>
			<persName><forename type="first">J</forename><surname>Zhao</surname></persName>
		</author>
		<author>
			<persName><forename type="first">X</forename><surname>Qu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Wu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Fowler</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">F</forename><surname>Burke</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Energy and AI</title>
		<imprint>
			<biblScope unit="volume">18</biblScope>
			<biblScope unit="page">100419</biblScope>
			<date type="published" when="2024">2024</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<title level="a" type="main">Transforming financial reporting with ai: Enhancing accuracy and timeliness</title>
		<author>
			<persName><forename type="first">B</forename><forename type="middle">O</forename><surname>Antwi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><forename type="middle">O</forename><surname>Adelakun</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">O</forename><surname>Eziefule</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">International Journal of Advanced Economics</title>
		<imprint>
			<biblScope unit="volume">6</biblScope>
			<biblScope unit="page" from="205" to="223" />
			<date type="published" when="2024">2024</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">Wiki-based prompts for enhancing relation extraction using language models</title>
		<author>
			<persName><forename type="first">A</forename><surname>Layegh</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">H</forename><surname>Payberah</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Soylu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Roman</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Matskin</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 39th ACM/SIGAPP Symposium on Applied Computing</title>
				<meeting>the 39th ACM/SIGAPP Symposium on Applied Computing</meeting>
		<imprint>
			<date type="published" when="2024">2024</date>
			<biblScope unit="page" from="731" to="740" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">Large-scale semantic integration of linked data: A survey</title>
		<author>
			<persName><forename type="first">M</forename><surname>Mountantonakis</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Tzitzikas</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">ACM Computing Surveys (CSUR)</title>
		<imprint>
			<biblScope unit="volume">52</biblScope>
			<biblScope unit="page" from="1" to="40" />
			<date type="published" when="2019">2019</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">Data integration for heterogenous datasets</title>
		<author>
			<persName><forename type="first">J</forename><surname>Hendler</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Big data</title>
		<imprint>
			<biblScope unit="volume">2</biblScope>
			<biblScope unit="page" from="205" to="215" />
			<date type="published" when="2014">2014</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">Heterogeneous data and big data analytics</title>
		<author>
			<persName><forename type="first">L</forename><surname>Wang</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Automatic Control and Information Sciences</title>
		<imprint>
			<biblScope unit="volume">3</biblScope>
			<biblScope unit="page" from="8" to="15" />
			<date type="published" when="2017">2017</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<monogr>
		<author>
			<persName><forename type="first">M</forename><surname>Ripamonti</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>De Paoli</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Palmonari</surname></persName>
		</author>
		<idno type="arXiv">arXiv:2203.09521</idno>
		<title level="m">Semtui: a framework for the interactive semantic enrichment of tabular data</title>
				<imprint>
			<date type="published" when="2022">2022</date>
		</imprint>
	</monogr>
	<note type="report_type">arXiv preprint</note>
</biblStruct>

<biblStruct xml:id="b9">
	<analytic>
		<title level="a" type="main">Geospatial enrichment of urban data for advanced city planning: a pilot study</title>
		<author>
			<persName><forename type="first">I</forename><surname>Krasteva</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Petrova-Antonova</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>De Paoli</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Hristov</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Borukova</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Ciavotta</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Avogadro</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">IEEE International Conference on Big Data (BigData)</title>
				<imprint>
			<publisher>IEEE</publisher>
			<date type="published" when="2023">2023. 2023</date>
			<biblScope unit="page" from="3139" to="3143" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<analytic>
		<title level="a" type="main">An interactive approach to semantic enrichment with geospatial data</title>
		<author>
			<persName><forename type="first">F</forename><forename type="middle">De</forename><surname>Paoli</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Ciavotta</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Avogadro</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Hristov</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Borukova</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Petrova-Antonova</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename><surname>Krasteva</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Data &amp; Knowledge Engineering</title>
		<imprint>
			<biblScope unit="volume">153</biblScope>
			<biblScope unit="page">102341</biblScope>
			<date type="published" when="2024">2024</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<analytic>
		<title level="a" type="main">open-source tool for cleaning and transforming data</title>
		<author>
			<persName><forename type="first">K</forename><surname>Ham</surname></persName>
		</author>
		<ptr target="http://openrefine.org.free" />
	</analytic>
	<monogr>
		<title level="j">Journal of the Medical Library Association</title>
		<imprint>
			<biblScope unit="volume">101</biblScope>
			<biblScope unit="page">233</biblScope>
			<date type="published" when="2013">2013</date>
		</imprint>
	</monogr>
	<note>JMLA</note>
</biblStruct>

<biblStruct xml:id="b12">
	<analytic>
		<title level="a" type="main">Data profiling for data quality improvement with openrefine</title>
		<author>
			<persName><forename type="first">T</forename><forename type="middle">F</forename><surname>Kusumasari</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">2016 international conference on information technology systems and innovation (ICITSI), IEEE</title>
				<imprint>
			<date type="published" when="2016">2016</date>
			<biblScope unit="page" from="1" to="6" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b13">
	<analytic>
		<title level="a" type="main">Datagraft: Simplifying open data publishing</title>
		<author>
			<persName><forename type="first">D</forename><surname>Roman</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Dimitrov</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Nikolov</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Putlier</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Sukhobok</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Elvesaeter</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Berre</surname></persName>
		</author>
		<author>
			<persName><forename type="first">X</forename><surname>Ye</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Simov</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Petkov</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">The Semantic Web: ESWC 2016 Satellite Events</title>
				<meeting><address><addrLine>Heraklion, Crete, Greece</addrLine></address></meeting>
		<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2016-06-02">May 29-June 2, 2016. 2016</date>
			<biblScope unit="volume">13</biblScope>
			<biblScope unit="page" from="101" to="106" />
		</imprint>
	</monogr>
	<note>Revised Selected Papers</note>
</biblStruct>

<biblStruct xml:id="b14">
	<analytic>
		<title level="a" type="main">Datagraft: One-stop-shop for open data management</title>
		<author>
			<persName><forename type="first">D</forename><surname>Roman</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Nikolov</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Putlier</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Sukhobok</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Elvesaeter</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Berre</surname></persName>
		</author>
		<author>
			<persName><forename type="first">X</forename><surname>Ye</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Dimitrov</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Simov</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Zarev</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Semantic Web</title>
		<imprint>
			<biblScope unit="volume">9</biblScope>
			<biblScope unit="page" from="393" to="411" />
			<date type="published" when="2018">2018</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b15">
	<analytic>
		<title level="a" type="main">Estimating link confidence for human-in-the-loop table annotation</title>
		<author>
			<persName><forename type="first">R</forename><surname>Avogadro</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Ciavotta</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>De Paoli</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Palmonari</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Roman</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">IEEE International Conference on Web Intelligence and Intelligent Agent Technology (WI-IAT)</title>
				<imprint>
			<publisher>IEEE</publisher>
			<date type="published" when="2023">2023. 2023</date>
			<biblScope unit="page" from="142" to="149" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b16">
	<analytic>
		<title level="a" type="main">Lamapi: a comprehensive tool for string-based entity retrieval with type-base filters</title>
		<author>
			<persName><forename type="first">R</forename><surname>Avogadro</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Cremaschi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>D'adda</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>De Paoli</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Palmonari</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">OM@ ISWC</title>
				<imprint>
			<date type="published" when="2022">2022</date>
			<biblScope unit="page" from="25" to="36" />
		</imprint>
	</monogr>
</biblStruct>

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