<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta>
      <issn pub-type="ppub">1613-0073</issn>
    </journal-meta>
    <article-meta>
      <title-group>
        <article-title>Knowledge Base Canonicalization: Techniques and Challenges</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Yang Yang</string-name>
          <email>yang.yang@insight-centre.org</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Edward Curry</string-name>
          <email>edward.curry@universityofgalway.ie</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="editor">
          <string-name>Knowledge Base, Knowledge Base Embedding, Clustering, Open Knowledge Base Canonicalization</string-name>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Insight SFI Research Centre for Data Analytics, University of Galway</institution>
        </aff>
      </contrib-group>
      <abstract>
        <p>Curated knowledge bases (CKBs) play a fundamental role in both academia and industry. They require significant human involvement to pre-define the ontology and cannot quickly adapt to new domains and new data. To solve this problem, open information extraction (OIE) methods are leveraged to automatically extract structure in the form of non-canonicalized triples &lt;noun phrase, relation phrase, noun phrase&gt; from unstructured text. OIE can be used to create large open knowledge bases (OKBs). However, noun phrases and relation phrases in such OKBs are not canonicalized, which results in scattered and redundant facts. In order to disambiguate and eliminate redundancy in such OKBs, the task of OKB canonicalization is proposed to cluster synonymous noun phrases and relation phrases into the same group and assign them unique identifiers. Nevertheless, this task is challenging due to the high sparsity and limited information of OKBs. In this paper, we provide an overview and analysis of the techniques used by the main frameworks and discuss the challenges in this topic.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>CEUR
ceur-ws.org</p>
    </sec>
    <sec id="sec-2">
      <title>1. Introduction</title>
      <p>
        Motivation. The exponential growth of web data has become an indispensable source of
knowledge for artificial intelligence. Mining and utilizing the knowledge of web data has been
one of the key tasks of artificial intelligence in the past two decades. Pragmatically constructed
from web resources, Curated Knowledge Bases (CKBs) like YAGO [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], Freebase [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], DBpedia
[
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], and Wikidata [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] have drawn significant attention from academia and industry [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. Due to
their efectiveness in storing and representing factual knowledge, they have been successfully
applied in many real knowledge-driven applications, including knowledge reasoning [
        <xref ref-type="bibr" rid="ref6 ref7 ref8 ref9">6, 7, 8, 9</xref>
        ],
question answering [
        <xref ref-type="bibr" rid="ref10 ref11 ref12 ref13">10, 11, 12, 13</xref>
        ], and recommendation systems [
        <xref ref-type="bibr" rid="ref14 ref15 ref16 ref17">14, 15, 16, 17</xref>
        ]. Early in the
study of this discipline, researchers were mostly focusing on ontology design and fact expansion
based on crowd-sourcing strategies. Large-scale CKBs, such as YAGO [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] and Wikidata [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ],
usually contain millions of entities and hundreds of millions of relational facts about them,
which are stored in the form of triples (i.e., &lt;head entity, relation, tail entity&gt;). For example, in the
triple &lt;Albert Einstein, lived in, Princeton&gt;, Albert Einstein and Princeton are real-world entities,
and lived in represents the relation between Albert Einstein and Princeton. CKB construction is
dificult to automate and therefore sufers from two inevitable defects: 1) human supervision,
the construction of CKBs usually requires significant human supervision to pre-define the
ontology; 2) weak adaptability, this construction manner makes it unable to quickly adapt to
new domains and new data generated by rapidly growing web data.
      </p>
      <p>
        In order to solve this problem, Open Information Extraction (OIE) techniques have been
utilized to improve the eficiency of knowledge base 1 construction without any pre-defined
ontology. Given an unstructured text corpus, OIE methods can be used to automatically extract
non-canonicalized triples in the form &lt;noun phrase, relation phrase, noun phrase&gt; requiring
neither a pre-defined ontology schema nor any human supervision. This makes them highly
adaptable to the knowledge from rapidly growing web data. Several prominent instances
include TextRunner [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ], Standford OIE [
        <xref ref-type="bibr" rid="ref19">19</xref>
        ], and MinIE [
        <xref ref-type="bibr" rid="ref20">20</xref>
        ]. Furthermore, the advent of the
OIE method directly promotes the development of large-scale Open Knowledge Bases (OKBs),
such as ReVerb [21], OLLIE [22, 23, 24], and OPIEC [25]. Without human supervision, this
automated OIE paradigm enables OKBs to easily grow to a very large scale, thus the coverage
and diversity of OKBs are much higher than CKBs.
      </p>
      <p>A major shortcoming of OKBs is that, unlike CKBs, Noun Phrases (NPs) and Relation Phrases
(RPs) in OKBs are not canonicalized and lack unique identifiers. Intuitively, this leads to two
issues in such OKBs: 1) two NPs (or RPs) that have diferent surface forms but refer to the
same entity (or relation) will be treated diferently; 2) two NPs (or RPs) with the same surface
form but referring to diferent entities (or relations) will be considered the same. Moreover,
this shortcoming results in the storage of scattered and redundant facts, which makes OKBs
extremely sparse and far from being directly used in downstream tasks.</p>
      <p>To address the crucial shortcoming, the task of OKB canonicalization [26] was proposed to
convert non-canonicalized triples in OKBs to their canonicalized form. In recent years, several
methods [26, 27, 28, 29, 30, 31, 32] have been proposed, by treating this problem as a clustering
task. More precisely, OKB canonicalization methods cluster synonymous NPs (or RPs) into
one group and then select one NP (or RP) to represent others in the group. This task helps
to disambiguate, eliminate redundancy, and integrate the highly diverse knowledge in OKBs,
which can benefit downstream applications.</p>
      <p>
        Focus and Contributions. Many comprehensive surveys have provided an overview of CKBs,
in particular their construction [33, 34, 35, 36] and representation [
        <xref ref-type="bibr" rid="ref5">5, 37, 38, 39, 40, 41</xref>
        ]. Other
surveys summarize methods for refinement [ 42, 43], completeness [44] and quality management
[45]. Unlike other surveys that only focus on CKBs, we present the first overview of OKB
canonicalization. Moreover, we also present practical resources and discuss future challenges.
Hence, our contributions include:
      </p>
      <p>• This is the first overview of OKB canonicalization, with an analysis of existing models and
their approaches.</p>
      <p>• Challenges of existing technologies in the area of OKB canonicalization are indicated as
directions for future works.</p>
      <p>Outline. We organize our overview as follows. Section 2 gives the background for OKB
canonicalization, including definitions and examples. In Section 3, the analysis of the diferent
OKB canonicalization techniques and challenges is discussed. Finally, the overview is concluded
in Section 4.
1Knowledge base (KB) and knowledge graph (KG) are alternative terms in this overview.</p>
    </sec>
    <sec id="sec-3">
      <title>2. Background</title>
      <p>In this section, we introduce some basic concepts and then define the task of OKB
canonicalization.</p>
      <p>
        Definition 1 (Curated Knowledge Base). A Curated Knowledge Base (CKB) is defined as a
ifnite set of triples that are generated by human efort following the pre-defined ontology.
Entities and relations in CKBs are well canonicalized and defined with unique identifiers. For
example, the entity Albert Einstein (German-born theoretical physicist; developer of the theory
of relativity) has unique identifiers “/m/0jcx” and “Q937” in Freebase [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] and Wikidata [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]
respectively.
      </p>
      <p>Definition 2 (Open Knowledge Base). An open knowledge base is a finite set of
noncanonicalized triples that are automatically extracted from unstructured text without any
predefined ontology via OIE methods.</p>
      <p>
        It is noted that the definition of open knowledge base in this paper is diferent from [ 33]. In [33],
they classify knowledge bases into open knowledge bases and enterprise knowledge bases, based
on the organization or community. Specifically, open knowledge bases in [ 33] are published
online and their content is accessible for the public good, such as YAGO [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] and Wikidata [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ].
In contrast, enterprise knowledge bases are typically internal to a company and applied for
commercial use-cases [46]. However, following our definitions of CKB and OKB, both open
knowledge bases and enterprise knowledge bases in [33] are under the concept of CKBs in
this paper, since they all require human efort to define the ontology but are not constructed
automatically from unstructured text. Following our definition, notable examples of OKBs
include ReVerb [21], OPIEC [25], and Open-CyKG [47].
      </p>
      <p>To be more specific, we use Figure 1 (a) as an example. If we search an NP Albert Einstein in
a question-answering system which is built on top of the open knowledge base in Figure 1 (a),
we can only obtain answers related to Albert Einstein but other information hid behind Albert
is missed, because it is unknown for machines that both Albert Einstein and Albert refer to the
same entity. Moreover, it can be seen that the two non-canonicalized triples &lt;Albert, was born
in, Ulm&gt; and &lt;Albert Einstein, was born at, Ulm&gt; are redundant facts, only one of which needs
to be stored in practice.</p>
      <p>Definition 3 (OKB Canonicalization). Given a set of non-canonicalized triples in an OKB,
the goal of OKB canonicalization is to cluster synonymous NPs referring to the same entity and
synonymous RPs having the same semantic meaning into a group, which converts these
noncanonicalized triples to their canonicalized forms. Then, one element is selected to represent all
others in the same group.</p>
      <p>As shown in Figure 1 (b), the OKB canonicalization task can be divided into two subtasks: NP
canonicalization (shown in blue at the top) and RP canonicalization (shown in green at the
bottom). For NP canonicalization, the model should recognize that Michael Jordan1 and Michael
Jordan2 do not refer to the same entity, and assign Michael Jordan1 and Michael Jefrey Jordan
to one cluster, and assign Michael Jordan2 to another cluster alone. Additionally, in each cluster,
one NP should be selected to represent others in this cluster, such as Michael Jefrey Jordan and
Michael Jordan2. Similarly, for RP canonicalization, the model needs to assign was born in and
was born at into one cluster and select one (was born in) as the representative.
Albert Einstein</p>
      <p>Albert
Michael Jordan2</p>
      <p>Ulm</p>
      <p>Dream Team
Brooklyn</p>
      <p>UCSD
Noun Phrases Canonicalization
lived in</p>
      <p>received his PhD from
was a member of</p>
      <p>Relation Phrases Canonicalization
(b) Open Knowledge Base Canonicalization
&lt; Albert, was born in, Ulm &gt;
&lt; Albert Einstein, lived in, Princeton &gt;
&lt; Albert Einstein, was born at, Ulm &gt;
&lt; Michael Jeffrey Jordan, was born in, Brooklyn &gt;
&lt; Michael Jordan1, was a member of, Dream Team &gt;
&lt; Michael Jordan2, received his PhD from, UCSD &gt;</p>
      <p>(a) Open Knowledge Base
&lt; Albert Einstein, was born in, Ulm &gt;
&lt; Albert Einstein, lived in, Princeton &gt;
&lt; Michael Jeffrey Jordan, was born in, Brooklyn &gt;
&lt; Michael Jeffrey Jordan, was a member of, Dream Team &gt;
&lt; Michael Jordan2, received his PhD from, UCSD &gt;
(c) Canonicalized Open Knowledge Base</p>
      <p>Princeton
Michael Jeffrey Jordan</p>
      <p>Michael Jordan1
was born in
was born at
In this study, the investigated OKB canonicalization models are divided into the following
diferent categories based on the techniques utilized: (i) Side Information [ 48] 2, (ii) Pre-trained
Word Embedding, (iii) Knowledge Base Embedding, (iv) Context Information, and (v) Supervised
Manner. This section consists of an analysis of the techniques in each framework, with a
discussion of their challenges. Table 1 summarizes OKB canonicalization models according to
our proposed taxonomy.</p>
      <sec id="sec-3-1">
        <title>3.1. Side Information</title>
        <p>NPs and RPs in OKBs often have relevant side information in the documents from which the
non-canonicalized triples were extracted or in other related CKBs, thus we need to use
thirdparty tools to mine and utilize it. Furthermore, side information can be divided into two types:
NP side information and RP side information.</p>
        <sec id="sec-3-1-1">
          <title>3.1.1. NP Side Information</title>
          <p>So far, previous studies have mined 14 tools to generate NP’s side information. Due to space
reasons, we focus here on the 3 most commonly used ones.</p>
          <p>• IDF Token Overlap. Proposed by [26], this side information is also commonly leveraged
by [28, 29, 49, 31, 30]. Inspired by the Inverse Document Frequency (IDF) algorithm, [26] believe
that if two NPs share a word, they are more likely to be similar, but not if many other mentions
2It is also known as Signals in [30] and Seed Pairs in [32].
share that word. Therefore, they introduce a weighted word overlap, in which a word is given
more importance if it appears in fewer mentions. It should be noted that IDF Token Overlap can
not only be used for NP canonicalization but is also often used for RP canonicalization [ 29, 30].</p>
          <p>• Entity Linking. [30] proves that OKB canonicalization and OKB linking are tightly coupled,
and one task can benefit significantly from the other. Therefore, entity linking is one of the
most commonly used tools for the OKB canonicalization task. For example, [26] uses FACC1
[50]; [28, 49, 31] utilize Stanford CoreNLP Entity Linker [51]; [29] leverage Wikidata Integrator
[52]; and [30, 32] use Entity Popularity [53].</p>
          <p>• PPDB. PPDB 2.0 [54] is a large collection of English paraphrases. All equivalent phrases
will be assigned to one cluster and each cluster will randomly select a representative. Therefore,
two NPs are considered equivalent if they have the same cluster representative according to the
index. Similar to IDF Token Overlap, PPDB is also used for both NP canonicalization and RP
canonicalization.</p>
        </sec>
        <sec id="sec-3-1-2">
          <title>3.1.2. RP Side Information</title>
          <p>RP side information is obtained from relation mining and relation matching tools to improve
RP canonicalization. Here, we introduce the most commonly used one, AMIE.</p>
          <p>• AMIE. AMIE algorithm [55] can determine whether two RPs represent the same semantics
by learning Horn rules. Previous studies [26, 28, 49, 31, 30, 32] usually take morphologically
normalized triples as input to AMIE, and the output of AMIE is a set of implication rules between
two RPs   and   (e.g.   ⇒   ) based on statistical rule mining. If both   ⇒   and   ⇐  
satisfy the support and confidence thresholds, it means that two RPs (i.e.,   and   ) have the
same semantics and should be grouped into one cluster.</p>
          <p>Challenge 1 (Side Information). One important challenge is to find more efective and
efifcient tools to boost the performance of this task. On the other hand, these third-party
tools are not perfect, and the accuracy of them is usually lower than 90%. Previous
methods [26, 28, 49, 31, 30, 32] usually leverage a combination of multiple side information to
improve their performance. This brings a new challenge: how to evaluate the confidence of
diferent third-party tools and use them in combination. More strategies to combine multiple
tools and improve their quality should be encouraged.</p>
        </sec>
      </sec>
      <sec id="sec-3-2">
        <title>3.2. Knowledge Base Embedding</title>
        <p>Knowledge base embedding (KBE) [37, 38] is an increasingly popular technique that aims to
represent entities and relations of knowledge bases into low-dimensional semantic spaces. To
capture the relational structural information of non-canonicalized triples in an OKB, the KBE
model is first exploited by CESI [ 28], and then it is widely used in this task. For example, HoIE
[57] is used by CESI [28] and CUVA [31], and TransE [58] is utilized by CMVC [32]. Additionally,
a Meta-Graph Neural Network is used in MGNN [49].</p>
        <p>Challenge 2 (Knowledge Base Embedding). The main challenge in leveraging KBE on
OKBs is the high sparsity of OKBs. This is because KBE can only work well on dense KBs but
OKBs are usually extremely sparse. Therefore, developing tools to alleviate the sparsity of OKB
and KBE methods specifically for sparse OKB could obtain improved performance. Furthermore,
developing a new architecture that learns OKB embeddings while canonicalizing OKB may also
Model</p>
        <p>KBE</p>
        <p>PWE</p>
        <p>NP RP
Attribute Overlap,
String Similarity,</p>
        <p>String Identity,
Galárraga et al. (CIKM2014)[26] IDF Token Overlap, AMIE - - - Semi-supervised
Word Overlap,
Entity Overlap,
Type Overlap</p>
        <p>Entity Linking,
CESI (WWW2018) [28] IDPFPDToBk,eWnoOrdveNrelat,p, AMIE, KBP HoIE GloVe - Semi-supervised</p>
        <p>Morph Normalization</p>
        <p>SIST (ICDE2019) [29] JarIoD-FEWnTitonitkkyelenLriOnSkivmienrigllaarpi,ty, IDF ToPkAeTnTOY,verlap - - Domain Vector Unsupervised
MULCE (WISE 2020) [56] - - - GloVe, BERT - Semi-supervised</p>
        <p>Entity Linking, PPDB,
MGNN (arXiv 2020) [49] WordNet, IDF Token Overlap, AMIE, KBP Meta-Graph NN GloVe, BERT - Semi-supervised
Morph Normalization</p>
        <p>Entity Linking, PPDB,
CUVA (EMNLP 2021) [31] IDF Token Overlap, AMIE, KBP HoIE GloVe - Semi-supervised</p>
        <p>Morph Normalization
JOCL (SIGMOD2021) [30] PPIDDFBt,oEknetnityovLeirnlakpin,g PIDRPeFDlaBtot,ikoAenMnLoIiEvn,ekKrilnBagpP,, - FastText - Semi-supervised
CMVC (KDD2022) [32] Entity Linking, Web Url AMIE, Web Url TransE FastText BERT Unsupervised
be a solution, so that high-quality embeddings could be learned during the gradual densification
of OKB.</p>
        <p>CI</p>
        <p>Supervised Manner</p>
      </sec>
      <sec id="sec-3-3">
        <title>3.3. Pre-trained Word Embedding</title>
        <p>Pre-trained word embeddings (PWE) have been shown to perform well in many tasks. CESI
[28] first introduces GloVe embeddings [ 59] into this task. Specifically, before training the
KBE model, all embeddings are initialized by GloVe embeddings. This is because the KBE
model can only capture structural knowledge but not semantic knowledge. However, PWE can
introduce semantic knowledge learned from a large corpus, thereby initializing semantically
similar NPs or RPs to similar positions in the low-dimensional embedding space. Following this
idea, knowledge base embeddings in CMVC [32] are initialized via FastText embeddings [60],
and MULCE [56] and MGNN [49] also leveraged BERT [61] for initialization.
Challenge 3 (Pre-trained Word Embedding). One significant challenge for static word
embeddings (such as GloVe and FastText) is the out-of-vocabulary (OOV) problem. The scale of a
static word embedding dictionary is limited, but the number of words in web data is infinite (and
growing all the time), thus utilizing PWE will always face the OOV problem. Besides, generating
higher-quality PWE can also become a challenge. On the other hand, without fine-tuning, the
performance of BERT embeddings is pretty limited but fine-tuning can be time-consuming in
this task.</p>
      </sec>
      <sec id="sec-3-4">
        <title>3.4. Context Information</title>
        <p>In OKBs, non-canonicalized triples can only carry limited structural knowledge which is not
enough to tackle the OKB canonicalization task, while valuable knowledge may be embedded in
the source context of these non-canonicalized triples. SIST [29] first leverages knowledge from
the original source text via generating domain vectors, to cluster NPs and RPs jointly using
an eficient clustering method. CMVC [ 32] proves that two views of knowledge (i.e., a fact
view based on the non-canonicalized triples and a context view based on the non-canonicalized
triple’s source context) provide complementary information that is vital to the task of OKB
canonicalization. Therefore, they exploit BERT [61] to convert source context into sentence
embeddings and combine them with the structural embeddings of the KBE model.
Challenge 4 (Context Information). The first challenge is to develop more eficient models
to capture the context information since only two frameworks (SIST [29] and CMVC [32]) so far
exploit context information. Another challenge is how to leverage more advanced NLP models
(such as generative large language models) to solve this problem.</p>
      </sec>
      <sec id="sec-3-5">
        <title>3.5. Supervised Manner</title>
        <p>For the task of OKB canonicalization, previous methods can be divided into two categories:
semisupervised methods [26, 27, 28, 30, 31] and unsupervised methods [29, 32]. Semi-supervised
methods require using the validation data set to search optimal parameters. In contrast,
unsupervised methods can automatically search parameters only based on the test data set without
the requirement of any manually annotated label.</p>
        <p>For example, as a clustering problem, the number of clusters (or clustering threshold) for
K-means (or Hierarchical Agglomerative Clustering) is an important parameter. Previous
semi-supervised methods [26, 27, 28, 30, 31] utilized the validation data set to find the optimal
clustering threshold. On the contrary, SIST [29] set the clustering threshold of diferent data
sets to the same fixed value in an unsupervised manner. To remedy this issue in a more flexible
and unsupervised manner, CMVC [32] proposed the Log-Jump algorithm to predict the number
of clusters, which only depends on the input embeddings of data without requiring any labels.
Challenge 5 (Supervised Manner). For this task, more unsupervised frameworks should be
developed in the future, because we cannot always find the validation data set in real-world
scenarios. In addition, for semi-supervised methods, there are diferences and imbalances in
probability distributions between the validation data set and the test data set. Identifying and
resolving these diferences and imbalances from them is also a problem. Finally, we should also
encourage the development of more efective algorithms for predicting cluster numbers.</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>4. Conclusion</title>
      <p>Open knowledge base canonicalization has become a critical topic for constructing open
knowledge base from unstructured text, and this issue has not yet been fully explored. For future
research, the three most important challenges can be summarized as follows: 1) How to mine
and utilize more types of knowledge, such as more side information tools, knowledge from
diferent views and modalities; 2) For frameworks that leverage knowledge base embedding
models, how to alleviate the high sparsity of OKBs; 3) How to develop eficient end-to-end
unsupervised frameworks.</p>
    </sec>
    <sec id="sec-5">
      <title>Acknowledgments</title>
      <p>This publication has emanated from research conducted with the financial support of Science
Foundation Ireland under Grant number SFI/12/RC/2289_P2.
extraction, in: EMNLP, 2017, pp. 2620–2630.
[21] A. Fader, S. Soderland, O. Etzioni, Identifying relations for open information extraction,
in: EMNLP, 2011, pp. 1535–1545.
[22] J. Christensen, S. Soderland, O. Etzioni, An analysis of open information extraction based
on semantic role labeling, in: K-CAP, 2011, pp. 113–120.
[23] M. Mausam, Open information extraction systems and downstream applications, in: IJCAI,
2016, pp. 4074–4077.
[24] S. Saha, H. Pal, Mausam, Bootstrapping for numerical open ie, in: ACL, 2017, pp. 317–323.
[25] K. Gashteovski, S. Wanner, S. Hertling, S. Broscheit, R. Gemulla, Opiec: an open information
extraction corpus, in: AKBC, 2019.
[26] L. Galárraga, G. Heitz, K. Murphy, F. M. Suchanek, Canonicalizing open knowledge bases,
in: CIKM, 2014, pp. 1679–1688.
[27] T.-H. Wu, Z. Wu, B. Kao, P. Yin, Towards practical open knowledge base canonicalization,
in: CIKM, 2018, pp. 883–892.
[28] S. Vashishth, P. Jain, P. Talukdar, Cesi: canonicalizing open knowledge bases using
embeddings and side information, in: WWW, 2018, pp. 1317–1327.
[29] X. Lin, L. Chen, Canonicalization of open knowledge bases with side information from
the source text, in: ICDE, 2019, pp. 950–961.
[30] Y. Liu, W. Shen, Y. Wang, J. Wang, Z. Yang, X. Yuan, Joint open knowledge base
canonicalization and linking, in: SIGMOD, 2021, pp. 2253–2261.
[31] S. Dash, G. Rossiello, N. Mihindukulasooriya, S. Bagchi, A. Gliozzo, Open knowledge
graphs canonicalization using variational autoencoders, in: EMNLP, 2021, pp. 10379–10394.
[32] W. Shen, Y. Yang, Y. Liu, Multi-view clustering for open knowledge base canonicalization,
in: KDD, 2022, pp. 1578–1588.
[33] A. Hogan, E. Blomqvist, M. Cochez, C. d’Amato, G. D. Melo, C. Gutierrez, S. Kirrane, J. E. L.</p>
      <p>Gayo, R. Navigli, S. Neumaier, et al., Knowledge graphs, ACM Computing Surveys 54
(2021) 1–37.
[34] G. Weikum, X. L. Dong, S. Razniewski, F. Suchanek, et al., Machine knowledge: Creation
and curation of comprehensive knowledge bases, Foundations and Trends® in Databases
10 (2021) 108–490.
[35] X. Chen, H. Xie, Z. Li, G. Cheng, Topic analysis and development in knowledge graph
research: A bibliometric review on three decades, Neurocomputing 461 (2021) 497–515.
[36] L. Zhong, J. Wu, Q. Li, H. Peng, X. Wu, A comprehensive survey on automatic knowledge
graph construction, arXiv preprint arXiv:2302.05019 (2023).
[37] J. Cao, J. Fang, Z. Meng, S. Liang, Knowledge graph embedding: A survey from the
perspective of representation spaces, arXiv preprint arXiv:2211.03536 (2022).
[38] G. A. Gesese, R. Biswas, H. Sack, A comprehensive survey of knowledge graph embeddings
with literals: Techniques and applications., DL4KG@ ESWC 2377 (2019) 31–40.
[39] G. A. Gesese, R. Biswas, M. Alam, H. Sack, A survey on knowledge graph embeddings
with literals: Which model links better literal-ly?, Semantic Web 12 (2021) 617–647.
[40] A. Rossi, D. Barbosa, D. Firmani, A. Matinata, P. Merialdo, Knowledge graph embedding
for link prediction: A comparative analysis, ACM Transactions on Knowledge Discovery
from Data 15 (2021) 1–49.
[41] Q. Wang, Z. Mao, B. Wang, L. Guo, Knowledge graph embedding: A survey of approaches
and applications, IEEE Transactions on Knowledge and Data Engineering 29 (2017)
2724–2743.
[42] H. Paulheim, Knowledge graph refinement: A survey of approaches and evaluation
methods, Semantic web 8 (2017) 489–508.
[43] B. Subagdja, Z. Wang, A.-H. Tan, Machine learning for refining knowledge graphs: A
survey, ACM Computing Surveys (2023).
[44] S. Razniewski, H. Arnaout, S. Ghosh, F. M. Suchanek, Completeness, recall, and negation
in open-world knowledge bases: A survey, ACM Computing Surveys (2024).
[45] B. Xue, L. Zou, Knowledge graph quality management: a comprehensive survey, IEEE</p>
      <p>Transactions on Knowledge and Data Engineering (2022).
[46] I. Nonaka, H. Takeuchi, The knowledge-creating company, Harvard business review 85
(2007) 162.
[47] I. Sarhan, M. Spruit, Open-cykg: An open cyber threat intelligence knowledge graph,</p>
      <p>Knowledge-Based Systems 233 (2021) 107524.
[48] C. C. Aggarwal, Y. Zhao, P. S. Yu, On the use of side information for mining text data,</p>
      <p>IEEE Transactions on Knowledge and Data Engineering 26 (2014) 1415–1429.
[49] T. Jiang, T. Zhao, B. Qin, T. Liu, N. V. Chawla, M. Jiang, Canonicalizing open knowledge
bases with multi-layered meta-graph neural network, arXiv preprint arXiv:2006.09610
(2020).
[50] E. Gabrilovich, M. Ringgaard, A. Subramanya, Facc1: Freebase annotation of clueweb
corpora, version 1 (release date 2013-06-26, format version 1, correction level 0) (2013).
[51] V. I. Spitkovsky, A. X. Chang, A cross-lingual dictionary for english wikipedia concepts,
in: LREC, 2012.
[52] SuLab, Wikidataintegrator, in: https://github.com/SuLab/WikidataIntegrator, 2017.
[53] W. Shen, J. Wang, P. Luo, M. Wang, Linden: linking named entities with knowledge base
via semantic knowledge, in: WWW, 2012, pp. 449–458.
[54] E. Pavlick, P. Rastogi, J. Ganitkevitch, B. Van Durme, C. Callison-Burch, Ppdb 2.0:
better paraphrase ranking, fine-grained entailment relations, word embeddings, and style
classification, in: ACL, 2015, pp. 425–430.
[55] L. A. Galárraga, C. Teflioudi, K. Hose, F. Suchanek, Amie: association rule mining under
incomplete evidence in ontological knowledge bases, in: WWW, 2013, pp. 413–422.
[56] T.-H. Wu, B. Kao, Z. Wu, X. Feng, Q. Song, C. Chen, Mulce: Multi-level canonicalization
with embeddings of open knowledge bases, in: WISE, Springer, 2020, pp. 315–327.
[57] M. Nickel, L. Rosasco, T. A. Poggio, Holographic embeddings of knowledge graphs, in:</p>
      <p>AAAI, 2016, pp. 1955–1961.
[58] A. Bordes, N. Usunier, A. Garcia-Durán, J. Weston, O. Yakhnenko, Translating embeddings
for modeling multi-relational data, in: NIPS, 2013, pp. 2787–2795.
[59] J. Pennington, R. Socher, C. D. Manning, Glove: Global vectors for word representation,
in: EMNLP, 2014, pp. 1532–1543.
[60] P. Bojanowski, E. Grave, A. Joulin, T. Mikolov, Enriching word vectors with subword
information, TACL 5 (2017) 135–146.
[61] J. D. M.-W. C. Kenton, L. K. Toutanova, Bert: pre-training of deep bidirectional transformers
for language understanding, in: NAACL-HLT, 2019, pp. 4171–4186.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>F. M.</given-names>
            <surname>Suchanek</surname>
          </string-name>
          , G. Kasneci, G. Weikum,
          <article-title>Yago: a core of semantic knowledge</article-title>
          ,
          <source>in: WWW</source>
          ,
          <year>2007</year>
          , pp.
          <fpage>697</fpage>
          -
          <lpage>706</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>K.</given-names>
            <surname>Bollacker</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Evans</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Paritosh</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Sturge</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Taylor</surname>
          </string-name>
          , Freebase:
          <article-title>a collaboratively created graph database for structuring human knowledge</article-title>
          ,
          <source>in: SIGMOD</source>
          ,
          <year>2008</year>
          , pp.
          <fpage>1247</fpage>
          -
          <lpage>1250</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>J.</given-names>
            <surname>Lehmann</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Isele</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Jakob</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Jentzsch</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Kontokostas</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Mendes</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Hellmann</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Morsey</surname>
          </string-name>
          , P. van Kleef,
          <string-name>
            <given-names>S.</given-names>
            <surname>Auer</surname>
          </string-name>
          , C. Bizer, DBpedia
          <article-title>- a large-scale, multilingual knowledge base extracted from wikipedia</article-title>
          ,
          <source>Semantic Web Journal</source>
          <volume>6</volume>
          (
          <year>2015</year>
          )
          <fpage>167</fpage>
          -
          <lpage>195</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>D.</given-names>
            <surname>Vrandečić</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Krötzsch</surname>
          </string-name>
          ,
          <article-title>Wikidata: a free collaborative knowledgebase</article-title>
          ,
          <source>Communications of the ACM</source>
          <volume>57</volume>
          (
          <year>2014</year>
          )
          <fpage>78</fpage>
          -
          <lpage>85</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>S.</given-names>
            <surname>Ji</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Pan</surname>
          </string-name>
          , E. Cambria,
          <string-name>
            <given-names>P.</given-names>
            <surname>Marttinen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S. Y.</given-names>
            <surname>Philip</surname>
          </string-name>
          ,
          <article-title>A survey on knowledge graphs: Representation, acquisition, and applications</article-title>
          ,
          <source>IEEE Transactions on Neural Networks and Learning Systems</source>
          <volume>33</volume>
          (
          <year>2021</year>
          )
          <fpage>494</fpage>
          -
          <lpage>514</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>X.</given-names>
            <surname>Chen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Jia</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Xiang</surname>
          </string-name>
          ,
          <article-title>A review: Knowledge reasoning over knowledge graph</article-title>
          ,
          <source>Expert Systems with Applications</source>
          <volume>141</volume>
          (
          <year>2020</year>
          )
          <fpage>112948</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>H.</given-names>
            <surname>Ji</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Ke</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Huang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Wei</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>Zhu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Huang</surname>
          </string-name>
          ,
          <article-title>Language generation with multi-hop reasoning on commonsense knowledge graph</article-title>
          ,
          <source>in: EMNLP</source>
          ,
          <year>2020</year>
          , pp.
          <fpage>725</fpage>
          -
          <lpage>736</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>L.</given-names>
            <surname>Liu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Du</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y. R.</given-names>
            <surname>Fung</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Ji</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Xu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Tong</surname>
          </string-name>
          ,
          <article-title>Kompare: a knowledge graph comparative reasoning system</article-title>
          ,
          <source>in: KDD</source>
          ,
          <year>2021</year>
          , pp.
          <fpage>3308</fpage>
          -
          <lpage>3318</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>Z.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>Jin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Guan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Guo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Shen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Wang</surname>
          </string-name>
          , X. Cheng,
          <article-title>Temporal knowledge graph reasoning based on evolutional representation learning</article-title>
          ,
          <source>in: SIGIR</source>
          ,
          <year>2021</year>
          , pp.
          <fpage>408</fpage>
          -
          <lpage>417</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>Z.</given-names>
            <surname>Dai</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Xu</surname>
          </string-name>
          ,
          <article-title>Cfo: Conditional focused neural question answering with large-scale knowledge bases</article-title>
          ,
          <source>in: ACL</source>
          ,
          <year>2016</year>
          , pp.
          <fpage>800</fpage>
          -
          <lpage>810</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>L.</given-names>
            <surname>Bauer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Wang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Bansal</surname>
          </string-name>
          ,
          <article-title>Commonsense for generative multi-hop question answering tasks</article-title>
          ,
          <source>in: EMNLP</source>
          ,
          <year>2018</year>
          , pp.
          <fpage>4220</fpage>
          -
          <lpage>4230</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>Y.</given-names>
            <surname>Zhang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Dai</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Z.</given-names>
            <surname>Kozareva</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Smola</surname>
          </string-name>
          , L. Song,
          <article-title>Variational reasoning for question answering with knowledge graph</article-title>
          ,
          <source>in: AAAI</source>
          , volume
          <volume>32</volume>
          ,
          <year>2018</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <given-names>Z.</given-names>
            <surname>Jia</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Pramanik</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R. Saha</given-names>
            <surname>Roy</surname>
          </string-name>
          , G. Weikum,
          <article-title>Complex temporal question answering on knowledge graphs</article-title>
          ,
          <source>in: CIKM</source>
          ,
          <year>2021</year>
          , pp.
          <fpage>792</fpage>
          -
          <lpage>802</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <given-names>F.</given-names>
            <surname>Zhang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N. J.</given-names>
            <surname>Yuan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Lian</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>Xie</surname>
          </string-name>
          , W.-Y. Ma,
          <article-title>Collaborative knowledge base embedding for recommender systems</article-title>
          , in: KDD,
          <year>2016</year>
          , pp.
          <fpage>353</fpage>
          -
          <lpage>362</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <given-names>X.</given-names>
            <surname>Wang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>He</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Cao</surname>
          </string-name>
          , M. Liu, T.-S. Chua,
          <article-title>Kgat: Knowledge graph attention network for recommendation</article-title>
          ,
          <source>in: KDD</source>
          ,
          <year>2019</year>
          , pp.
          <fpage>950</fpage>
          -
          <lpage>958</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <given-names>X.</given-names>
            <surname>Wang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Huang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Wang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Yuan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Z.</given-names>
            <surname>Liu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>He</surname>
          </string-name>
          , T.-S. Chua,
          <article-title>Learning intents behind interactions with knowledge graph for recommendation</article-title>
          ,
          <source>in: WWW</source>
          ,
          <year>2021</year>
          , pp.
          <fpage>878</fpage>
          -
          <lpage>887</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [17]
          <string-name>
            <given-names>Q.</given-names>
            <surname>Guo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Zhuang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Qin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Zhu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>Xie</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Xiong</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Q.</given-names>
            <surname>He</surname>
          </string-name>
          ,
          <article-title>A survey on knowledge graphbased recommender systems</article-title>
          ,
          <source>IEEE Transactions on Knowledge and Data Engineering</source>
          <volume>34</volume>
          (
          <year>2020</year>
          )
          <fpage>3549</fpage>
          -
          <lpage>3568</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          [18]
          <string-name>
            <given-names>M.</given-names>
            <surname>Banko</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. J.</given-names>
            <surname>Cafarella</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Soderland</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Broadhead</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Etzioni</surname>
          </string-name>
          ,
          <article-title>Open information extraction from the web</article-title>
          ,
          <source>in: IJCAI</source>
          ,
          <year>2007</year>
          , pp.
          <fpage>2670</fpage>
          -
          <lpage>2676</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          [19]
          <string-name>
            <given-names>G.</given-names>
            <surname>Angeli</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. J. Johnson</given-names>
            <surname>Premkumar</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C. D.</given-names>
            <surname>Manning</surname>
          </string-name>
          ,
          <article-title>Leveraging linguistic structure for open domain information extraction</article-title>
          ,
          <source>in: ACL</source>
          ,
          <year>2015</year>
          , pp.
          <fpage>344</fpage>
          -
          <lpage>354</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          [20]
          <string-name>
            <given-names>K.</given-names>
            <surname>Gashteovski</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Gemulla</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Del Corro</surname>
          </string-name>
          ,
          <article-title>Minie: minimizing facts in open information</article-title>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>