<?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">Entity Alignment for Knowledge Graphs in the Context of Supply Chain Risk Management</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Rebeka</forename><surname>Gadzo</surname></persName>
							<email>gadzo.rebeka@gmail.com</email>
							<affiliation key="aff0">
								<orgName type="institution">Humboldt University</orgName>
								<address>
									<addrLine>Unter den Linden 6</addrLine>
									<postCode>10117</postCode>
									<settlement>Berlin</settlement>
									<country key="DE">Germany</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Yushan</forename><surname>Liu</surname></persName>
							<email>yushan.liu@siemens.com</email>
							<affiliation key="aff1">
								<orgName type="institution">Siemens AG</orgName>
								<address>
									<addrLine>Otto-Hahn-Ring 6</addrLine>
									<postCode>81739</postCode>
									<settlement>Munich</settlement>
									<country key="DE">Germany</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Entity Alignment for Knowledge Graphs in the Context of Supply Chain Risk Management</title>
					</analytic>
					<monogr>
						<idno type="ISSN">1613-0073</idno>
					</monogr>
					<idno type="MD5">8F227CAE39D195FCFCB55F2BB1625585</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2025-04-23T17:30+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>Knowledge Graph</term>
					<term>Entity Alignment</term>
					<term>Deep Learning</term>
					<term>Supply Chain Risk Management</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>Supply chain risk management has become increasingly important during challenging times characterized by various economic, health, and political crises. To address risk mitigation issues, it is required to lay the groundwork for future risk prediction algorithms. This paper focuses on utilizing knowledge graphs, given their effectiveness in capturing and organizing complex supply chain information. The main objective is to investigate methodologies for aligning two separate knowledge graphs, where one represents supply chain data and the other external macroeconomic data. Expansion of the supply chain graph with pertinent macroeconomic information enables a better assessment and prediction of risks. The main outcome of this research work is to develop a framework based on a real-world scenario applicable to different use cases.</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>Supply chain risk management (SCRM) addresses strategies and their implementation for managing various risks along the supply chain based on their continuous assessment. Ensuring the highest possible extent of continuity of a supply chain and reducing its vulnerability are two of SCRM's primary goals <ref type="bibr" target="#b0">[1]</ref>.</p><p>Exogenous supply chain risks occur outside the ecosystems of companies and suppliers. They can, therefore, only be influenced by these ecosystems to a limited extent <ref type="bibr" target="#b1">[2]</ref>. Recent notable examples are the pandemic-related effects of COVID-19 and the political and military conflict in the Ukraine. In addition, this risk type also includes legal risks, environmental and natural disasters, as well as market risks in individual regions. Exogenous risks could thus be identified through macroeconomic data such as economic facts, trends, and cause-effect relationships. The identification of these risks becomes more effective through the integration of macroeconomic knowledge into a company's supply chain data. Entity alignment between different data sources can facilitate this integration. Knowledge graphs (KGs) have gained significant importance in recent years by enabling integration, management, and value extraction from diverse sources of data at large scale <ref type="bibr" target="#b2">[3]</ref>. Additionally, they have been proven as a suitable data source for the purposes of entity alignment <ref type="bibr" target="#b3">[4]</ref> and therefore adequate for the given problem statement.</p><p>This paper utilizes the three following techniques for entity aligning between two knowledge graphs: Dedupe <ref type="bibr" target="#b4">[5]</ref>, Ditto <ref type="bibr" target="#b5">[6]</ref>, and GPT-3 <ref type="bibr" target="#b6">[7]</ref>. A case study on a Siemens supply chain management (SCM) KG is performed. The overall objective is to devise a general framework that can extend the Siemens SCM KG by linking it to an external macroeconomic KG. This research conducts an in-depth examination of supply chain and macroeconomic data, aiming to identify shared attributes that facilitate the dataset merging process, and assesses the performance of the three graph integration approaches.</p><p>In the introduction, the significance of entity alignment for mitigating supply chain risks is emphasized, setting the stage for the research theme. Section 2 provides an overview of existing literature in the field of entity alignment between KGs and the importance of KGs in the context of SCRM. It encompasses previous research efforts and their motivations. Section 3 describes three algorithms utilized for entity alignment between KGs, outlining their functionalities and methodologies. Section 4 focuses on the two primary data sources: the CoyPu KG <ref type="foot" target="#foot_0">1</ref> and Siemens' supply chain data, with an emphasis on suppliers from Germany, the USA, and China, and compares the schemas of both graphs. Section 5 details the experimental process, including the steps involved in entity alignment, and presents the research results. The conclusion summarizes the findings, discusses implications for SCRM, and outlines potential future research in the field of entity alignment between KGs in the context of SCRM.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.">Related Work</head><p>While research on entity alignment across KGs exists, there is a noticeable gap in studies specifically addressing entity alignment between KGs within SCM and SCRM contexts.</p><p>Liu et al. <ref type="bibr" target="#b7">[8]</ref> utilized a KG to represent supply chain information from Siemens. By employing advanced KG completion techniques, the authors predicted missing connections within the graph and computed importance scores for suppliers through graph analysis algorithms. Brockmann et al. <ref type="bibr" target="#b8">[9]</ref> focused on augmenting a supply chain KG by available web data using graph neural network models for predicting possible missing links in the created graph. Karam et al. <ref type="bibr" target="#b9">[10]</ref> implemented Bayesian networks to propose their approach called Resilience of Supply Chain Analyzer (ReSCA), which should enable an early identification of bottlenecks in supply chains and a timely prediction of the consequences. Li et al. <ref type="bibr" target="#b10">[11]</ref> presented the construction of a supply chain KG by performing data cleaning, desensitization, categorization, and storage of information obtained from various data sources related to the rail transportation industry's supply chain. CoyPu 2 , a knowledge graph project within the resilience domain, operates as a semantic data platform for crisis management and supply chain data exploration. It enables users to analyze complex data, make informed decisions, and contribute to economic resilience by integrating, structuring, and evaluating heterogeneous data from various sources <ref type="bibr" target="#b11">[12]</ref>.</p><p>Entity alignment is an active research area with a wide range of techniques proposed in the literature. Similarity-based methods <ref type="bibr" target="#b12">[13]</ref>, machine learning techniques <ref type="bibr" target="#b13">[14]</ref>, and deep learning models <ref type="bibr" target="#b5">[6]</ref> have been applied to tackle entity alignment-related challenges. In recent years, the utilization of deep learning models in entity alignment tasks has become increasingly popular due to their capability to learn complex representations from data <ref type="bibr" target="#b14">[15]</ref>. Convolutional neural networks (CNNs) <ref type="bibr" target="#b15">[16]</ref>, recurrent neural networks (RNNs) <ref type="bibr" target="#b16">[17]</ref>, and transformer-based models, such as BERT <ref type="bibr" target="#b17">[18]</ref> and GPT-3 <ref type="bibr" target="#b18">[19]</ref>, have been employed for entity alignment tasks to capture intricate patterns in entity attributes. Ditto <ref type="bibr" target="#b5">[6]</ref> is also considered a powerful and flexible framework for entity alignment that can be used in a wide range of applications, according to Barlaug and Gulla <ref type="bibr" target="#b19">[20]</ref>. These deep learning models have demonstrated promising outcomes in achieving high alignment performance and robustness to noisy or incomplete data <ref type="bibr" target="#b20">[21]</ref>. Further research is needed to develop more robust and scalable entity alignment methods to enable accurate and efficient data integration in various domains <ref type="bibr" target="#b21">[22]</ref>.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">Algorithms</head><p>In this section, we will describe the three selected algorithms applied for the entity alignment purpose: Dedupe <ref type="bibr" target="#b4">[5]</ref> as an unsupervised method, Ditto <ref type="bibr" target="#b5">[6]</ref> for leveraging pre-trained language models, and GPT-3 <ref type="bibr" target="#b6">[7]</ref> as a representative of large language models. This selection enhanced our research approach with each algorithm's distinctive strengths.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.1.">Dedupe</head><p>The Dedupe algorithm <ref type="bibr" target="#b4">[5]</ref> employs a range of distinctive comparison methodologies. The primary technique involves utilizing the affine gap string metric to assess the similarity between diverse records. Additionally, Dedupe employs both the Levenshtein text distance and the term frequency-inverse document frequency (TF-IDF) tokens. To accurately determine field importance, the algorithm adopts regularized logistic regression. The field importance ranking process is enhanced through active learning, wherein manual input is used to improve the weight settings.</p><p>Blocking refers to the process of narrowing down candidate matches. In the case of Dedupe, it encompasses predicate blocking, which employs specific predicates, and index blocking, leveraging an inverted index for efficiency.</p><p>For grouping duplicate records, Dedupe relies on hierarchical clustering with centroid linkage. Random samples are compared against expected precision and recall metrics to set a similarity threshold for the linking process.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.2.">Ditto -Deep Entity Matching with Pre-Trained Language Models</head><p>Ditto <ref type="bibr" target="#b5">[6]</ref> is a deep entity matching framework that leverages pre-trained language models to perform entity alignment of large datasets. The framework is built on top of PyTorch 3 and the Hugging Face transformers library <ref type="foot" target="#foot_3">4</ref> . It supports both exact matching and fuzzy matching using a variety of pre-trained language models, such as BERT, RoBERTa, and DistilBERT.</p><p>Ditto uses a pre-trained language model to encode the input records into fixed-length vector representations. These vectors capture the semantic and contextual information. Consequently, the vectors are compared using a similarity function to compute a similarity score. The similarity function is based on various metrics, such as the cosine similarity. The similarity score is then thresholded to determine whether the input records are matches.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.3.">GPT-3 -Third-Generation Generative Pre-Trained Transformer</head><p>The davinci variant of the autoregressive language model GPT-3 <ref type="bibr" target="#b6">[7]</ref> includes 175 billion parameters and demonstrates exceptional performance across various natural language processing (NLP) tasks, even competing with state-of-the-art fine-tuned systems. Notably, the model excels at tasks such as content generation, code writing, and translation, showcasing its potential for solving arbitrarily defined tasks and thereby establishing its utility in various NLP applications. While the architecture of the model remains similar to that of GPT-2 <ref type="bibr" target="#b22">[23]</ref>, the transformer layers display unique patterns, with the most advanced GPT-2 model having a comparatively low 1.5 billion parameters <ref type="bibr" target="#b23">[24]</ref>. The GPT-3 model was primarily trained on English data (93%), with additional mixed-language training data. The quality of input prompts directly affects GPT-3 performance <ref type="bibr" target="#b24">[25]</ref>. Notably, the GPT-3 model can provide a rather high confidence in its generated answers and a verbalized explanation for decision uncertainties <ref type="bibr" target="#b25">[26]</ref>.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.">Knowledge Graph Datasets</head><p>In this section, we will represent the two knowledge graph datasets used for the performed case study analysis.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.1.">Supply Chain Data</head><p>We use supply chain data from Siemens, which is stored in the form of a labeled property graph (LPG). Table <ref type="table" target="#tab_0">1</ref> depicts some of the graph metadata, including the number of node types, relationship types, and the graph's size. This graph incorporates data pertaining to Siemens' suppliers, branches, and business scopes and represents a snapshot of Siemens's supply chain graph from July 2023. This KG additionally encompasses comprehensive product information, including products details, together with manufacturing and smelter information.</p><p>Siemens' supply chain boasts 61.234 suppliers in total with the most represented ones being located in Germany (6.83%), the USA (6.24%), and China (5.51%). Notably, the three mentioned countries account for approximately one fifth of the overall number of suppliers. The subsequent analysis will concentrate exclusively on the mentioned countries to facilitate more targeted model training.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.2.">Macroeconomic Data</head><p>CoyPu<ref type="foot" target="#foot_4">5</ref> (Cognitive Economy Intelligence Platform for the Resilience of Economic Ecosystems) is a project that aims to create a macroeconomic model of the global economy in the form of a KG. It encompasses countries, industrial sectors, critical infrastructure, recent events, and further associated entities <ref type="foot" target="#foot_5">6</ref> . This macroeconomic data is stored as a Resource Description Framework (RDF) graph, and it is a product of several combined ontologies and data sources. The ontology can be obtained from the CoyPu project's website <ref type="foot" target="#foot_6">7</ref> . Table <ref type="table" target="#tab_0">1</ref> shows some of the key facts about this KG. Among other relevant knowledge in this graph, we will emphasize the most important data such as disaster events and company properties. Alongside, there is information about natural disasters, political disasters, strikes, violence, attacks, and demonstrations. These disaster events mostly have a risk score assigned along with an alert score, which reflects the degree of their influence on a supply chain. Moreover, detailed company information can also be extracted from the KG, including company names, locations, branches, company size, and products. The KG also incorporates geographical and infrastructure information, including details such as continent, country, or city along with coordinates and the nearest ports, airports, and rivers.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.">Methodology</head><p>Entity alignment in the context of knowledge graphs entails the process of matching equivalent entities across different graphs to establish connections and integrate information effectively. This section covers the entity alignment approach between the two given data sources (see Section 4).</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.1.">Schema Comparison</head><p>The crucial information for entity alignment between KGs revolves around identifying identical real-world objects across two data sources. Between the macroeconomic and the supply chain data, there is a limited overlap. The chosen approach for aligning the two provided graphs involves consolidating their respective company entities. The suppliers associated with Siemens ought to be aligned with their corresponding counterparts in the CoyPu graph, thus incorporating macroeconomic details concerning these entities, including their geographical locations and potential risk associations. The country information in both graphs includes the same ISO code format, serving as an unique identifier for country matching. On the other side, some industry-related entities exhibit varying granularity levels despite representing identical information, rendering these features hardly comparable.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.2.">Framework for KGs Entity Alignment</head><p>For the purpose of entity alignment of the two data sources, three different algorithms have been applied and evaluated. Figure <ref type="figure" target="#fig_0">1</ref> shows the solution framework and each of the process steps. The extracted supplier lists are the starting point and serve as input data for the three selected algorithms. The results are analyzed to identify the best approach and to finally perform the envisioned entity alignment between the KGs. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.3.">Data Preparation</head><p>For supplier matching, only the essential information describing suppliers was extracted from the initial graphs. This information, including company names, country locations, and, if available, city locations, was organized into a tabular format to facilitate the linkage process using the selected algorithms. The given data was divided into smaller units by each country to avoid memory issues, allow for country-specific data preparation and evaluation, and accelerate the speed of algorithm execution. This also resulted in a significant reduction of possible false-positive matches.</p><p>To enable the linking process, several pre-processing techniques were applied to simplify and standardize the data. Data properties were parsed, cleaned, and translated if necessary, especially to handle language or character differences. Since Chinese company names in CoyPu are in Chinese language, while SCM companies from China are already in English, the Google Translate API 8 was employed to overcome language barriers. Notably, the company's legal form was determined based on common descriptors in company names, streamlining the alignment process by removing these descriptors from the names. Lastly, the geolocation was extracted through the external Nominatim API<ref type="foot" target="#foot_8">9</ref> using city names to identify the geographical location of a majority of the listed companies. Figure <ref type="figure" target="#fig_1">2</ref> shows the input and output of data preparation for an exemplary Chinese company. For entity alignment purposes, anything enclosed within brackets, aside from company names, legal forms, and locations, is regarded as irregular. Geographical entities not enclosed within brackets are also identified as irregularities (see Figure <ref type="figure" target="#fig_1">2</ref>). The training process of the Ditto model requires labeled training data. The number of possible matches between the two datasets is relatively low compared to the total number of candidate pairs. Possible matches account for the number of SCM suppliers as a smaller dataset with an approximate count of 11.000 out of more than 5 billion possible candidate pairs. Manually creating viable training sets was infeasible due to the large number of possible matches. Therefore, we used the output of Dedupe to create labeled datasets for training. The proposed matches from this matching approach were additionally manually labeled.</p><p>Additionally, we have omitted the legal form from the input data of GPT-3, as previous tests have shown improved results through this approach.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.4.">Entity Alignment Implementation</head><p>The source code repository is available on Github <ref type="foot" target="#foot_9">10</ref> . It was necessary to start with the execution of the unsupervised approach Dedupe to find positive matches for data labeling. Negative matches were generated randomly and additionally labeled manually. This data has been used to provide the training set for the supervised method Ditto.</p><p>The Ditto algorithm was applied next. For each of the three countries, a corresponding model has been trained. The initial step was to generate the blocking data for matching purposes, which was done using the pre-trained model distilbert-base-uncased-finetuned-sst-2-english for US and Chinese companies, which were previously translated to English. In the case of German companies, bert-based-german-cased was used. These pre-trained models have been utilised from the Hugging Face transformers library. The blocking process was performed separately for each country.</p><p>The gpt-3.5-turbo API provided by OpenAI 11 , in the following referred to as GPT-3, has also been applied for the company alignment. System messages are used to configure GPT-3 to function as a company matching service, while user messages have been utilized to send candidates pairs. The model returns a binary match value, indicating whether the two companies are a match. Alongside, the match confidence is indicated by a decimal value ranging from 0 to 1, with 1 representing full confidence in the model's decision. The model is capable of matching with or without specified company's coordinates. It uses a single model for all countries, which is distinct from the other two solutions.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="6.">Results</head><p>This section encompasses results' discussion based on different evaluation metrics along with the final entity alignment of the given data sets.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="6.1.">Results Evaluation</head><p>The test set contains 750 entries across the countries, having 231 German companies, 252 Chinese companies, and 267 US companies. It is based on a random sample of positive matches from Dedupe's outputs, which are manually labeled for the purpose of evaluation. Negative matches were generated using random pairs from the datasets which are manually labeled. The models exhibited varying degrees of performance regarding false-positive and falsenegative values across all three countries (see Table <ref type="table" target="#tab_3">4</ref>). We hypothesize that the inflated number of false-positives overall in Table <ref type="table" target="#tab_1">2</ref> was due to the company name convention irregularities observed in China (see Figure <ref type="figure" target="#fig_1">2</ref> and Table <ref type="table" target="#tab_3">4</ref>). Specifically, the Ditto model matching results contained an increased number of false-positive matches, whereas the remaining two models have faced challenges with false-negative matches. This is evident from the contrasting differences in precision and recall scores of these models (see Table <ref type="table" target="#tab_1">2</ref>). The GPT-3 model exhibited consistent performance across all countries as measured by the F1-score. Its application was found to have superior performance, but due to its high usage expenses, it is impractical for the application. As a result, the Dedupe method emerged as the most suitable for aligning the two given graphs based on its favorable balance between recall and accuracy scores. Table <ref type="table" target="#tab_2">3</ref> shows the number and percentage of supplier matches found in total and per country by Dedupe, which we selected as the most suitable method. The most matches originate from Germany, while Chinese suppliers were the least likely to be matched.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="6.2.">Knowledge Graph Entity Alignment</head><p>The KG entity alignment includes two steps: the suppliers' property expansion and risk events addition (see Figure <ref type="figure" target="#fig_2">3</ref>). We have introduced four properties to the SCM KG: CoyPu link as ID reference of the respective company in the CoyPu KG, legal entity identifier (LEI), city name of the company's location, and latitude and longitude of the company's location.</p><p>It should be noted that although the CoyPu ontology includes many company properties, many values are still missing. These additional properties could be easily introduced to the SCM graph as the CoyPu graph completion progresses, based on the newly introduced CoyPu link. We have also established relations in the graph between events and companies that are geographically close based on leveraged coordinate information from both companies and events.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="7.">Conclusion</head><p>Siemens and CoyPu supplier entity alignment was conducted utilizing a set of three distinct methods. A KG entity alignment framework was developed and applied. The initial identification of matches was accomplished through the application of Dedupe, which was crucial for providing training data that could not have been feasibly generated manually.</p><p>Although GPT-3 was the most reliable method, its API cost rendered it impractical for the given problem statement. However, as large language models advance, this concern may diminish. Dedupe exhibited commendable matching capabilities with the second-best performance, demonstrating a balanced performance and practicality. Notably, the success rate of the models varied across different countries, with China posing the most problematic alignment scenario.</p><p>The outcome of the entity alignment process resulted in the Siemens supply chain graph not only containing references to the corresponding companies within the CoyPu graph but also incorporating relevant risk events associated with these companies. Future expansions may incorporate additional CoyPu graph data to enhance supply chain reliability. Our framework can be further applied to other graphs and extended by the application of risk prediction algorithms.</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: KGs Entity Alignment Framework</figDesc><graphic coords="6,105.27,356.11,384.75,72.00" 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: Initial and Parsed Company Name</figDesc></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: New Supplier's Properties</figDesc><graphic coords="9,140.08,509.58,315.12,140.40" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_0"><head>Table 1</head><label>1</label><figDesc>Key SCM and CoyPu Graph Parameters</figDesc><table><row><cell>Information</cell><cell>SCM</cell><cell>CoyPu</cell></row><row><cell>Graph Type</cell><cell>LPG</cell><cell>RDF</cell></row><row><cell>Nodes</cell><cell>65.568</cell><cell>140.128.633</cell></row><row><cell>Relationships</cell><cell cols="2">1.317.133 345.097.679</cell></row><row><cell>Node Types</cell><cell>11</cell><cell>83</cell></row><row><cell>Relationship Types</cell><cell>11</cell><cell>115</cell></row><row><cell>Datatype Properties</cell><cell>40</cell><cell>20</cell></row><row><cell>Companies</cell><cell>61.234</cell><cell>33.365.883</cell></row><row><cell>Graph Size</cell><cell>171 MB</cell><cell>110 GB</cell></row></table></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_1"><head>Table 2</head><label>2</label><figDesc>Results across all CountriesTrue Pos. False Neg. True Neg. False Pos. Acc.% Prec.% Recall% F1%</figDesc><table><row><cell>Dedupe</cell><cell>219</cell><cell>54</cell><cell>433</cell><cell>44</cell><cell>86.93</cell><cell>83.27</cell><cell>80.22</cell><cell>81.72</cell></row><row><cell>Ditto</cell><cell>260</cell><cell>13</cell><cell>361</cell><cell>116</cell><cell>82.80</cell><cell>69.15</cell><cell>95.24</cell><cell>80.12</cell></row><row><cell>GPT-3</cell><cell>227</cell><cell>46</cell><cell>450</cell><cell>27</cell><cell>90.27</cell><cell>89.37</cell><cell>83.15</cell><cell>86.15</cell></row><row><cell></cell><cell>Pos.=273</cell><cell></cell><cell></cell><cell>Neg.=477</cell><cell cols="2">Total=750</cell><cell></cell><cell></cell></row></table></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_2"><head>Table 3</head><label>3</label><figDesc></figDesc><table><row><cell>Dedupe's Matches per Country</cell><cell></cell><cell></cell><cell></cell></row><row><cell></cell><cell cols="3">SCM Suppliers Matches Percent</cell></row><row><cell>Germany</cell><cell>4184</cell><cell>2341</cell><cell>55.95%</cell></row><row><cell>US</cell><cell>3819</cell><cell>452</cell><cell>11.84%</cell></row><row><cell>China</cell><cell>3374</cell><cell>224</cell><cell>6.64%</cell></row><row><cell>Total</cell><cell>11377</cell><cell>3017</cell><cell>26.52%</cell></row></table></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_3"><head>Table 4</head><label>4</label><figDesc>Results per Country</figDesc><table><row><cell>GER</cell><cell cols="8">True Pos. False Neg. True Neg. False Pos. Acc.% Prec.% Recall% F1%</cell></row><row><cell>Dedupe</cell><cell>71</cell><cell>25</cell><cell>131</cell><cell>4</cell><cell>87.45</cell><cell>94.67</cell><cell>73.96</cell><cell>83.04</cell></row><row><cell>Ditto</cell><cell>93</cell><cell>3</cell><cell>104</cell><cell>31</cell><cell>85.28</cell><cell>75.00</cell><cell>96.88</cell><cell>84.55</cell></row><row><cell>GPT-3</cell><cell>88</cell><cell>8</cell><cell>121</cell><cell>14</cell><cell>90.48</cell><cell>86.27</cell><cell>91.67</cell><cell>88.89</cell></row><row><cell></cell><cell>Pos.=96</cell><cell></cell><cell>Neg.=135</cell><cell></cell><cell cols="2">Total=231</cell><cell></cell><cell></cell></row><row><cell>USA</cell><cell cols="8">True Pos. False Neg. True Neg. False Pos. Acc.% Prec.% Recall% F1%</cell></row><row><cell>Dedupe</cell><cell>100</cell><cell>16</cell><cell>149</cell><cell>2</cell><cell>93.26</cell><cell>98.04</cell><cell>86.21</cell><cell>91.74</cell></row><row><cell>Ditto</cell><cell>111</cell><cell>5</cell><cell>145</cell><cell>6</cell><cell>95.88</cell><cell>94.87</cell><cell>95.69</cell><cell>95.28</cell></row><row><cell>GPT-3</cell><cell>93</cell><cell>23</cell><cell>142</cell><cell>9</cell><cell>88.01</cell><cell>91.18</cell><cell>80.17</cell><cell>85.32</cell></row><row><cell></cell><cell>Pos.=116</cell><cell></cell><cell>Neg.=151</cell><cell></cell><cell cols="2">Total=267</cell><cell></cell><cell></cell></row><row><cell>CHN</cell><cell cols="8">True Pos. False Neg. True Neg. False Pos. Acc.% Prec.% Recall% F1%</cell></row><row><cell>Dedupe</cell><cell>48</cell><cell>13</cell><cell>153</cell><cell>38</cell><cell>79.76</cell><cell>55.81</cell><cell>78.69</cell><cell>65.31</cell></row><row><cell>Ditto</cell><cell>56</cell><cell>5</cell><cell>112</cell><cell>79</cell><cell>66.67</cell><cell>41.48</cell><cell>91.80</cell><cell>57.14</cell></row><row><cell>GPT-3</cell><cell>46</cell><cell>15</cell><cell>187</cell><cell>4</cell><cell>92.46</cell><cell>92.00</cell><cell>75.41</cell><cell>82.88</cell></row><row><cell></cell><cell>Pos.=61</cell><cell></cell><cell>Neg.=191</cell><cell></cell><cell cols="2">Total=252</cell><cell></cell><cell></cell></row></table></figure>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="1" xml:id="foot_0">https://coypu.org/ergebnisse/knowledge-graph</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="2" xml:id="foot_1">https://coypu.org</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="3" xml:id="foot_2">https://pytorch.org/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="4" xml:id="foot_3">https://huggingface.co</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="5" xml:id="foot_4">https://coypu.org</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="6" xml:id="foot_5">https://docs.coypu.org</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="7" xml:id="foot_6">https://schema.coypu.org/global/2.3</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="8" xml:id="foot_7">https://cloud.google.com/translate/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="9" xml:id="foot_8">https://nominatim.org/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="10" xml:id="foot_9">https://github.com/RebekaGadzo/graph_alignment</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="11" xml:id="foot_10">https://openai.com/</note>
		</body>
		<back>

			<div type="acknowledgement">
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Acknowledgements</head><p>This work has been supported by the German Federal Ministry for Economic Affairs and Climate Action (BMWK) as part of the project CoyPu under grant number 01MK21007K.</p></div>
			</div>

			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">Supply chain risk identification using a HAZOPbased approach</title>
		<author>
			<persName><forename type="first">A</forename><surname>Adhitya</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Srinivasan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename><forename type="middle">A</forename><surname>Karimi</surname></persName>
		</author>
		<idno type="DOI">10.1002/aic.11764</idno>
	</analytic>
	<monogr>
		<title level="j">AIChE Journal</title>
		<imprint>
			<biblScope unit="volume">55</biblScope>
			<biblScope unit="page" from="1447" to="1463" />
			<date type="published" when="2009">2009</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">Understanding risk management for intentional supply chain disruptions: Risk detection, risk mitigation, and risk recovery</title>
		<author>
			<persName><forename type="first">S</forename><surname>Duhadway</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Carnovale</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Hazen</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Annals of Operations Research</title>
		<imprint>
			<biblScope unit="volume">283</biblScope>
			<biblScope unit="page" from="179" to="198" />
			<date type="published" when="2019">2019</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">Knowledge graphs</title>
		<author>
			<persName><forename type="first">A</forename><surname>Hogan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Blomqvist</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Cochez</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Amato</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><forename type="middle">D</forename><surname>Melo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Gutierrez</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Kirrane</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">E L</forename><surname>Gayo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Navigli</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Neumaier</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">ACM Computing Surveys (CSUR)</title>
		<imprint>
			<biblScope unit="volume">54</biblScope>
			<biblScope unit="page" from="1" to="37" />
			<date type="published" when="2021">2021</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<monogr>
		<author>
			<persName><forename type="first">R</forename><surname>Zhang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><forename type="middle">D</forename><surname>Trisedy</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Li</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Jiang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Qi</surname></persName>
		</author>
		<idno type="arXiv">arXiv:2103.15059</idno>
		<title level="m">A benchmark and comprehensive survey on knowledge graph entity alignment via representation learning</title>
				<imprint>
			<date type="published" when="2022">2022</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<monogr>
		<author>
			<persName><forename type="first">F</forename><surname>Gregg</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Eder</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Cushman</surname></persName>
		</author>
		<title level="m">Entity resolution with machine learning: Dedupe.io&apos;s scalable foundation for data quality</title>
				<imprint>
			<date type="published" when="2018">2018</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<monogr>
		<author>
			<persName><forename type="first">Y</forename><surname>Li</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Li</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Suhara</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Doan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">W.-C</forename><surname>Tan</surname></persName>
		</author>
		<idno type="arXiv">arXiv:2004.00584</idno>
		<title level="m">Deep entity matching with pre-trained language models</title>
				<imprint>
			<date type="published" when="2020">2020</date>
		</imprint>
	</monogr>
	<note type="report_type">arXiv preprint</note>
</biblStruct>

<biblStruct xml:id="b6">
	<monogr>
		<title level="m" type="main">Language models are few-shot learners</title>
		<author>
			<persName><forename type="first">T</forename><forename type="middle">B</forename><surname>Brown</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Mann</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Ryder</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Subbiah</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Kaplan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Dhariwal</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Neelakantan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Shyam</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Sastry</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Askell</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Agarwal</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Herbert-Voss</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Krueger</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Henighan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Child</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Ramesh</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><forename type="middle">M</forename><surname>Ziegler</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Wu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Winter</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Hesse</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Chen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Sigler</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Litwin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Gray</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Chess</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Clark</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Berner</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Mccandlish</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Radford</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename><surname>Sutskever</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Amodei</surname></persName>
		</author>
		<idno type="arXiv">arXiv:2005.14165</idno>
		<imprint>
			<date type="published" when="2020">2020</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">A knowledge graph perspective on supply chain resilience</title>
		<author>
			<persName><forename type="first">Y</forename><surname>Liu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>He</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Hildebrandt</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Buchner</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Inzko</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Wernert</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Weigel</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Beyer</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Berbalk</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Tresp</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">The 2nd International Workshop on Linked Data-Driven Resilience Research, Extended Semantic Web Conference</title>
				<imprint>
			<date type="published" when="2023">2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">Supply chain link prediction on uncertain knowledge graph</title>
		<author>
			<persName><forename type="first">N</forename><surname>Brockmann</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><forename type="middle">Elson</forename><surname>Kosasih</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Brintrup</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">ACM SIGKDD Explorations Newsletter</title>
		<imprint>
			<biblScope unit="volume">24</biblScope>
			<biblScope unit="page" from="124" to="130" />
			<date type="published" when="2022">2022</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<analytic>
		<title level="a" type="main">A hybrid knowledge graph and bayesian network approach for analyzing supply chain resilience</title>
		<author>
			<persName><forename type="first">N</forename><surname>Karam</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Matini</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Laas</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Hoppe</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">European Semantic Web Conference</title>
				<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2023">2023</date>
			<biblScope unit="page" from="27" to="31" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<analytic>
		<title level="a" type="main">Building and using a supply chain knowledge graph applied to the rail transit industry</title>
		<author>
			<persName><forename type="first">S</forename><surname>Li</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Zhang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Huang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Wu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">W</forename><surname>Cai</surname></persName>
		</author>
		<idno type="DOI">10.1109/ACAIT53529.2021.9731237</idno>
	</analytic>
	<monogr>
		<title level="m">2021 5th Asian Conference on Artificial Intelligence Technology (ACAIT)</title>
				<imprint>
			<date type="published" when="2021">2021</date>
			<biblScope unit="page" from="742" to="746" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<monogr>
		<author>
			<persName><forename type="first">S</forename><surname>Bin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Stadler</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Radtke</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Junghanns</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Gründer-Fahrer</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Martin</surname></persName>
		</author>
		<title level="m">Base platform for knowledge graphs with free software</title>
				<imprint>
			<date type="published" when="2023">2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<analytic>
		<title level="a" type="main">Optimizing the retrieval of the vital status of cancer patients for health data warehouses by using open government data in france</title>
		<author>
			<persName><forename type="first">O</forename><surname>Lauzanne</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J.-S</forename><surname>Frenel</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Baziz</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Campone</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Raimbourg</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Bocquet</surname></persName>
		</author>
		<idno type="DOI">10.3390/ijerph19074272</idno>
	</analytic>
	<monogr>
		<title level="j">International Journal of Environmental Research and Public Health</title>
		<imprint>
			<biblScope unit="volume">19</biblScope>
			<date type="published" when="2022">2022</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b13">
	<analytic>
		<title level="a" type="main">Automated machine learning for entity matching tasks</title>
		<author>
			<persName><forename type="first">M</forename><surname>Paganelli</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><forename type="middle">D</forename><surname>Buono</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Pevarello</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Guerra</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Vincini</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">International Conference on Extending Database Technology</title>
				<imprint>
			<date type="published" when="2021">2021</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b14">
	<analytic>
		<title level="a" type="main">Deep model-based security-aware entity alignment method for edge-specific knowledge graphs</title>
		<author>
			<persName><forename type="first">J</forename><surname>Kim</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Kim</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Sohn</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Park</surname></persName>
		</author>
		<idno type="DOI">10.3390/su14148877</idno>
	</analytic>
	<monogr>
		<title level="j">Sustainability</title>
		<imprint>
			<biblScope unit="volume">14</biblScope>
			<date type="published" when="2022">2022</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b15">
	<analytic>
		<title level="a" type="main">Multi-order graph convolutional networks for knowledge graph alignment</title>
		<author>
			<persName><forename type="first">N</forename><forename type="middle">T</forename><surname>Tam</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><forename type="middle">T</forename><surname>Trung</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Yin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Vinh</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Sakong</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Zheng</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><forename type="middle">Q V</forename><surname>Hung</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">37th IEEE international conference on data engineering</title>
				<meeting><address><addrLine>Chania, Greece</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2021">2021</date>
			<biblScope unit="page" from="19" to="22" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b16">
	<monogr>
		<author>
			<persName><forename type="first">L</forename><surname>Guo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Z</forename><surname>Sun</surname></persName>
		</author>
		<author>
			<persName><forename type="first">W</forename><surname>Hu</surname></persName>
		</author>
		<idno type="arXiv">arXiv:1905.04914</idno>
		<title level="m">Learning to exploit long-term relational dependencies in knowledge graphs</title>
				<imprint>
			<date type="published" when="2019">2019</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b17">
	<analytic>
		<title level="a" type="main">Analyzing how BERT performs entity matching</title>
		<author>
			<persName><forename type="first">M</forename><surname>Paganelli</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><forename type="middle">D</forename><surname>Buono</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Baraldi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Guerra</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Proc. VLDB Endow</title>
		<imprint>
			<biblScope unit="volume">15</biblScope>
			<biblScope unit="page" from="1726" to="1738" />
			<date type="published" when="2022">2022</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b18">
	<analytic>
		<title level="a" type="main">Generic entity resolution models</title>
		<author>
			<persName><forename type="first">J</forename><surname>Tang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Zuo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Cao</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Madden</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">NeurIPS 2022 First Table Representation Workshop</title>
				<imprint>
			<date type="published" when="2022">2022</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b19">
	<analytic>
		<title level="a" type="main">Neural networks for entity matching: A survey</title>
		<author>
			<persName><forename type="first">N</forename><surname>Barlaug</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">A</forename><surname>Gulla</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">ACM Transactions on Knowledge Discovery from Data (TKDD)</title>
		<imprint>
			<biblScope unit="volume">15</biblScope>
			<biblScope unit="page" from="1" to="37" />
			<date type="published" when="2021">2021</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b20">
	<analytic>
		<title level="a" type="main">A comprehensive survey of entity alignment for knowledge graphs</title>
		<author>
			<persName><forename type="first">K</forename><surname>Zeng</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Li</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Hou</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Li</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Feng</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">AI Open</title>
		<imprint>
			<biblScope unit="volume">2</biblScope>
			<biblScope unit="page" from="1" to="13" />
			<date type="published" when="2021">2021</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b21">
	<analytic>
		<title level="a" type="main">Collective knowledge graph multi-type entity alignment</title>
		<author>
			<persName><forename type="first">Q</forename><surname>Zhu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Wei</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Sisman</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Zheng</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Faloutsos</surname></persName>
		</author>
		<author>
			<persName><forename type="first">X</forename><forename type="middle">L</forename><surname>Dong</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Han</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">The Web Conference</title>
				<imprint>
			<date type="published" when="2020">2020. 2020</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b22">
	<analytic>
		<title level="a" type="main">Language models are unsupervised multitask learners</title>
		<author>
			<persName><forename type="first">A</forename><surname>Radford</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Wu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Child</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Luan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Amodei</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename><surname>Sutskever</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">OpenAI Blog</title>
		<imprint>
			<date type="published" when="2019">2019</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b23">
	<monogr>
		<author>
			<persName><forename type="first">I</forename><surname>Solaiman</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Brundage</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Clark</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Askell</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Herbert-Voss</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Wu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Radford</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Krueger</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">W</forename><surname>Kim</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Kreps</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Mccain</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Newhouse</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Blazakis</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Mcguffie</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Wang</surname></persName>
		</author>
		<idno type="arXiv">arXiv:1908.09203</idno>
		<title level="m">Release strategies and the social impacts of language models</title>
				<imprint>
			<date type="published" when="2019">2019</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b24">
	<monogr>
		<title level="m" type="main">Efficient training of language models to fill in the middle</title>
		<author>
			<persName><forename type="first">M</forename><surname>Bavarian</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Jun</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Tezak</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Schulman</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Mcleavey</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Tworek</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Chen</surname></persName>
		</author>
		<idno type="arXiv">arXiv:2207.14255</idno>
		<imprint>
			<date type="published" when="2022">2022</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b25">
	<monogr>
		<author>
			<persName><forename type="first">S</forename><surname>Lin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Hilton</surname></persName>
		</author>
		<author>
			<persName><forename type="first">O</forename><surname>Evans</surname></persName>
		</author>
		<idno type="arXiv">arXiv:2205.14334</idno>
		<title level="m">Teaching models to express their uncertainty in words</title>
				<imprint>
			<date type="published" when="2022">2022</date>
		</imprint>
	</monogr>
</biblStruct>

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