<!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>
      <journal-title-group>
        <journal-title>Journal of Web Semantics 39 (2016) 47-61. doi:10.1016/j.websem.2016.05.
001.
[17] J. L. Martinez</journal-title>
      </journal-title-group>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="doi">10.1016/j.websem.2016.05</article-id>
      <title-group>
        <article-title>FAIR Knowledge Graph construction from text, an approach applied to fictional novels</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Diego Rincon-Yanez</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Sabrina Senatore</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>University of Salerno Via Giovanni Paolo II</institution>
          ,
          <addr-line>132 - 84084 Fisciano SA</addr-line>
          ,
          <country country="IT">Italy</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2022</year>
      </pub-date>
      <volume>2180</volume>
      <fpage>05</fpage>
      <lpage>30</lpage>
      <abstract>
        <p>A Knowledge Graph (KG) is a form of structured human knowledge depicting relations between entities, destined to reflect cognition and human-level intelligence. Large and openly available knowledge graphs (KGs) like DBpedia, YAGO, WikiData are universal cross-domain knowledge bases and are also accessible within the Linked Open Data (LOD) cloud, according to the FAIR principles that make data findable, accessible, interoperable and reusable. This work aims at proposing a methodological approach to construct domain-oriented knowledge graphs by parsing natural language content to extract simple triple-based sentences that summarize the analyzed text. The triples coded in RDF are in the form of subject, predicate, and object. The goal is to generate a KG that, through the main identified concepts, can be navigable and linked to the existing KGs to be automatically found and usable on the Web LOD cloud.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;Knowledge Graph</kwd>
        <kwd>Natural Language Processing</kwd>
        <kwd>Semantic Web Technologies</kwd>
        <kwd>Knowledge Graph Embeddings</kwd>
        <kwd>FAIR</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>Due to the complex nature of real-world data, defining a data knowledge model within the
specification of a domain is not a trivial task. Semantic Web Technologies (SWT) promise formal
paradigms to structure data in a machine-processable way by connecting resources defining
semantic relations among them. The result is a rich information representation model whose
information is well defined, uniquely identifiable, and accessible as a knowledge base. However,
the knowledge representation (KR) task is becoming more challenging every day due to the
increasing need to improve, extend, and re-adapt that knowledge to the real-world evolution.</p>
      <p>
        Knowledge Graphs (KGs) provide a way of represent knowledge at diferent levels of
abstraction and granularity; generally it is described [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] as composed of a knowledge base (KB) and a
reasoning system with multiple data sources. The KB is a directed network model whose edge
represent semantic properties; traditionally those network models can be classified depending
on the relations nature into a (1) homogeneous graph [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]  = (, ), whose edges (E)
represents the same type of relationship between the vertices (V), and (2) heterogeneous graph
 = (, , )[
        <xref ref-type="bibr" rid="ref2 ref3">3, 2</xref>
        ], whose edges (E) describe a set of relations (R), i.e., natural connections
between the nodes.
      </p>
      <p>Thanks to the W3C Resource Description Framework (RDF) standard1, knowledge can be
expressed as a network of atomic assertions, also called facts, described as triples composed of
Subject (S), Predicate (P) and Object (O),  = (, , ). In the light of the traditional definition
of heterogeneous graph  = (, , ), a KB can be described by mapping  ≡ ( ∪ ) and
 ≡  as the semantic relation between nodes, leaving the description of vertices as ∀ ∈  :
 = (, , ). On the other hand, the KG Reasoning System (KRS) can be interpreted as the
combination of one or more computing or reasoning (r) techniques to read or write the the
statements in the KB, and it can be expressed as  = (, ) or  = (, (, , ))
where  = {1, 2 . . . } and  ≥ 1 e.g.:  : KGE() = (, , ). In a nutshell,
a Knowledge Graph (KG) is composed of a Knowledge Base (KB) and a Knowledge Reasoning
System (KRS)  = ({1, 2 . . . }, (, , )).</p>
      <p>
        The FAIR [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]; Findability, Accessibility, Interoperability and Reuse principles refer to the
guidelines for good data management practice: resources must be more accessible, understood,
exchanged and reused by machines; these principles in the context of SWT and particularly in
the field of Knowledge Graph, encourage communities such as Open Linked Data Community
(OpenLOD) and Semantic Web to join eforts into the Fair Knowledge Graph topology [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]
building. On the other hand, the Open Knowledge Graphs (OpenKGs) are semantically available
on the Web [
        <xref ref-type="bibr" rid="ref2 ref5">2, 5</xref>
        ], they can be focused on universal domains, e.g., DBpedia [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], WikiData [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ], or
domain-specific knowledge such as YAGO [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] or WordNet2; most of them are integrated and
can be found through the OpenLOD Cloud3, and typically, they can be queried by SPARQL
interfaces. Nowadays, Linked Open Data and FAIR principles have played an essential role in
the KG spreading. These proposals catapulted the Knowledge Base Construction (KBC) process
by providing enormous leverage helping to cross-reference and improve the new generated
KBs accuracy, increasing the number of available queryable sources on the Web.
      </p>
      <p>This work proposes a methodological approach implemented as a library to build
domainspecific knowledge graphs compliant with FAIR principles from an automated perspective
without using knowledge-based semantic models. The method leverages traditional Natural
Language Processing (NLP) techniques to generate simple triples as a starting point and then
enhance them using external OpenKG, e.g., DBpedia, to annotate, normalize, and consolidate
an RDF-based KG. As a case study, novels in literature were explored to validate the proposed
approach by exploiting the features from the narrative construction and relationships between
characters, places and events in the story.</p>
      <p>The remainder of this work is structured as follows: Section 2 provides an overview of relevant
approaches, knowledge base construction foundations, and KG construction approaches. Section
3 presents the proposed methodological approach at a high abstraction level. Then, Section 4
describes details of the developed tool and the case study results. Experimental evidence and
evaluation is reported in Section 5. Finally, the conclusions and the future work are highlighted
in Section 6.</p>
      <sec id="sec-1-1">
        <title>1W3C RDF Oficial Website - https://www.w3.org/RDF/ 2WordNet Oficial site - https://wordnet.princeton.edu 3Open LOD Cloud - https://lod-cloud.net/</title>
      </sec>
    </sec>
    <sec id="sec-2">
      <title>2. Related Work</title>
      <p>
        The Knowledge Base (KB) lifecycle [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] can be described by three main phases: the Knowledge
Creation, in charge of discovering initial knowledge; in this phase, initial statements are
generated systematically to feed the KB. Then, the Knowledge Curation phase annotates and validates
the generated triples. Finally, the Knowledge Deployment phase is accomplished once the KB is
mature and can be used along with a reasoning system (KRS) to perform inferring operations.
      </p>
      <sec id="sec-2-1">
        <title>2.1. Knowledge Base Construction</title>
        <p>
          A knowledge base construction (KBC) can be achieved by performing the first two stages of the
KB life cycle, populating a KB [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ] and then annotate the knowledge with semantic information
[
          <xref ref-type="bibr" rid="ref11">11</xref>
          ]. The annotation process can be approached from an automated or a human-supervised
perspective. More specifically, the human-centered methods are categorized as (1) curated,
meaning a closed group of experts or (2) collaborative, by an open group of volunteers; these
two methods must be sustained by one or more knowledge schemes (e.g., ontology-based
population). Meanwhile, automatized approaches can uphold the previous schema-based[
          <xref ref-type="bibr" rid="ref12">12</xref>
          ],
but also a schema-free approach [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ], this categorization is detailed in Table 1.
        </p>
        <p>
          The KB is often a Commonsense Knowledge (CSK) since it refers to generic concepts from
daily life; classifying and getting more specific information can enhance the CSK by adding new
statements annotated semantically. In [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ] a three-step architecture is proposed: (1) Retrieval,
(2) Extraction, (3) Consolidation are the steps aimed at fact construction to extract multiple
key-value statements pairs from the consolidated assertions. Also, Open KGs are used to match
and connect terms from existing ontologies. Since Open KGs, like DBpedia, are composed
of large amounts of triples, retrieving data by SPARQL queries or other retrieval systems is
time and resource-consuming. Working with DBpedia On-Demand [
          <xref ref-type="bibr" rid="ref15">15</xref>
          ] allows accessing a
lightweight version of the KB, by using the semi-structured fields of DBpedia articles called
info-boxes (structured knowledge from the ontology).
        </p>
        <p>Ontological reasoning, on the other hand, needs synergistic integration: in [16], for example,
lexical-syntactic patterns are extracted from sentences in the text, exploiting an SVM (Support
Vector Machines) algorithm and then finding matches with DBpedia; the resulting matches
are then integrated by a Statistical Type Inference (STI) algorithm to create a homogeneous
RDF-based KB. Furthermore, Open Information Extraction (Open IE) provides atomic units
of information, with individual references (URI) to simplify conceivable queries on external
databases, such as DBpedia [17].</p>
        <p>The KB construction has evolved along with the knowledge representation requirement for
data ingestion as well as human consumption of data [18]. This evolution has increased the
complexity in terms of data dimensionality, number of sources, and data type diversity [19]. For
these additional challenges [20], semantic tools [21] can enhance the collected data by providing
cross-context, allowing inference from native data relationships or external data sources, such
as status reports or supply chain data.</p>
        <p>Once an initial KB has been deployed, the Knowledge Completion can be accomplished,
leveraging on the open-world assumption (OWA) also by using masking functions [22] to
connect unseen entities to the KG. Specifically, a masking model uses text features with the
structure  = (, , ?) to learn embeddings of entities and relations via high-dimensional
semantic representations based on the known Knowledge Graph Embedding (GKE) models such
as TransE neural network [23]. This approach can also be used for link prediction by exploiting
existing GKE models such as DistMult, ComplEX, to perform inference using the masked form
 = (, ?, ).</p>
      </sec>
      <sec id="sec-2-2">
        <title>2.2. Knowledge Graph Embeddings (KGE)</title>
        <p>Knowledge Graph Embeddings (KGE), also called Knowledge Graph Representation Learning,
has become a powerful tool for link prediction, triple classification, over an existing KG. These
approaches encode entities and relations of a knowledge graph into a low-dimensional
embedding vector space; these networks are based on Deep Learning techniques arriving at a score by
minimizing a loss function ℒ.</p>
        <p>KGE provides a comprehensive framework to perform operations [24] over a KB, usually
provided in the KB deployment phase. TransE [23], being one of the most studied KGE models,
   = −‖  +  − ‖, computes the similarity between the  translated by the
embedding of the predicate  and the object . TransE model is often exploited for applications
such as a knowledge validation model and achieves state-of-the-art prediction performance.</p>
        <p>TorusE is a TransE-based embedding method that, combined with the use of Lie Groups
knowledge base (KGLG) [25], is used to validate an inferred KB; it has been tested using
standard de-facto datasets to evaluate the multidimensional distance between spaces of computed
embeddings. Other KGE methods such as DistMult [26]    = {, , } use a
trilinear dot product to capture and extract semantic relations, while the method ComplEx [27]
  = ({, , }) uses a Hermitian dot product.</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>3. The proposed approach</title>
      <p>The proposed approach provides an incremental unsupervised methodology, compliant with
the FAIR principles, to build a knowledge graph on a specific domain, without exploiting
any ontology schema, but achieving the discovery, construction, and integration of triples
 = (, , ), extracted from an unstructured text, with zero initial knowledge. The approach
is described by the pipeline of Figure 1 shows the interaction of the main components of the
proposed framework.</p>
      <p>From a high-level perspective, the input is represented by the natural language text sources
and feeds the Triple Construction component, in charge of extracting triples from the analysis of
sentences in the text. The text parsing and the triples extraction are tailored to exploit the specific
prosaic text features, starting from the narrative properties and the implicit relations created by
the recurring entities described in the text. The facts extracted from textual data sources are plain
triples &lt; , ,  &gt; that, are incorporated as formal statements in the KB.
The triple elements are annotated semantically, by querying external semantic knowledge bases
such as DBpedia or Wikidata. This task is accomplished by the Triple Enrichment component,
generating a RDF-compliant KB. Afterward, this triple set is input to Embedding Training
component responsible for the KB completion. It accomplishes the reasoning on the KB,
exploiting a KGE model, to infer and validate the collected KB.</p>
      <p>Next subsections provides additional details about the introduced components of the
framework pipeline of Figure 1.</p>
      <sec id="sec-3-1">
        <title>3.1. Triple Construction</title>
        <p>NLP-based parsing tasks are applied to extract plain triple-based sentences. The Triple
Construction component initially carries out the Basic POS annotation on the input raw text, consisting of
traditional preliminary text analysis, namely, the tokenization, stop-word removal and -tagging
routines to identify and annotate the basic part of speech entities.</p>
        <p>Once the Basic POS annotation is accomplished, parallel activities, namely Information
Extraction and Chunking Rules and Tagging Pattern Execution are carried out, as shown in Figure
2.
3.1.1. Information Extraction:
This block is composed of three basic tasks necessary to get an further processing of the
tagged text yield by the Basic POS Annotation. The text is indeed given to the Named Entity
Recognizer (NER) which identifies named entities according to some specific entity types: person,
organization, location, event. Then a Dependency Parsing task allow locating named entities into
subject or object and finally, the Relation Extraction task is in charge of the triple composition,
starting by the detected entities. Let us remark that the named entities has a crucial role in the
triple identification and generation.
3.1.2. Tagging Pattern:
This task accomplish ad-hoc text processing, considering the nature of the text from a linguistic
perspective. Linguistic patterns were defined specifically for processing the prosaic narrative
and for this reason, for example, some stop words are not discarded. Those patterns can be
implemented to discriminate additional triple-based statement to feed the KB; in particular,
a finite-state machine is proposed, implementing three evaluation steps, one for each triple
component  = (, , ). Figure 3 sketches a few of the implemented state transitions used in
the development of this methodology.
3.1.3. Chunking Rules:
This task achieve a parallel shallow syntactic analysis where certain sub-sequences of words are
identified as forming special phrases. In particular, a regular-expression has been defined over
the sequence of word tags to select and extract basic triple for enriching the KB, such as the
following tag string   : {&lt;  &gt;? &lt;   * &gt;&lt;   &gt;? &lt;  * &gt;&lt;  &gt;? &lt;   * &gt;&lt;
  &gt;}. This regular expression pattern says that a triple pattern TP chunk should be formed
by the subject chunker which finds an optional determiner (DT) followed by any number of
adjectives (JJ) and then a noun (NN); then the predicate-chunker composed of the verb (in its
tenses) an finally the object-chunker that is similar to the subject chunker, except that it could
be a pronoun besides the noun. Subject and object chunkers are typical noun phrases. Some
rule example application is shown in Figure 4.</p>
        <p>As final result of the Triple Construction component, all the generated data are integrated
into a set of plain triples,   ≡  ∪   ∪ ℎ, where the  represents
resulting triples of Information Extraction task, the  , the result of Tagging Pattern and
ℎ is the Chunking Rules result, once redundant and duplicated are discarded. Finally,
the resulting triple set   is stored into a plain format file.</p>
      </sec>
      <sec id="sec-3-2">
        <title>3.2. Triple Enrichment</title>
        <p>Once the construction of the triple has been completed and stored, the Triple Enrichment
component (Figure 1) is in charge of annotating semantically the triple elements. First, each
element of triples is a candidate to be enriched semantically, by assigning a URI to it; for this
purpose, SPARQL queries whose arguments are the individual subject and object of the triples
are submitted to OpenKGs such as DBpedia or Wikidata, to retrieve the relative URIs, when
they are available. Similarly, the predicate is also looked up in the semantically enhanced lexical
database WordNet, once the verb has been transformed into its infinitive form.</p>
        <sec id="sec-3-2-1">
          <title>Algorithm 1 Triple enrichment Algorithm Input: Plain Triple Data set Output: RDF Triple Data set</title>
          <p>1: for all [, , ] :   do
2: for (S and O) as Entity do
3: [URI, Label] = QueryOpenKG(Entity)
4: triples.replace( Entity, URI )
5: triples.append( (URI, rdfs:label, label) )
6: end for
7: O = QueryWordNet( tokenization(O) )
8: end for
9: return RDF Triples</p>
          <p>The general process of the Triple Enrichment component is described in Algorithm 1. It
takes the triple collection as input and for each triple subject and object, search for the
corresponding URI in a OpenKG; and then, once retrieved, replaced the URI in the triple, along
with the associated rdfs:label. Let us notice that not only the external OpenKG URI is
extracted from the query, but also the rdfs:label for each entity added to the KB. A similar
query is carried out on WordNet, for the predicate: a simple disambiguation task is
accomplished considering the other triple elements, by similarity between terms in the WordNet
definition and triple words. Otherwise, the first sense is retrieved for default. Future
development are taken into account to select the right sense after a more accurate disambiguation
task. The output of the Triple Enrichment component is a semtic version of the collected
triples:  −  ≡  −  ∪  −   ∪  − ℎ, where  −  ,
 −  ,  − ℎ are the RDF-annotated triples coming from the corresponding
tasks of the Triple Construction component.</p>
        </sec>
      </sec>
      <sec id="sec-3-3">
        <title>3.3. KG Embeddings Training</title>
        <p>Last component of the described pipeline is the Embedding Training that is responsible to train
the KGE model on the processed triples. The KGE model provides a mechanism to perform
operations with the discovered KB, such as fact checking, question answering, link prediction
and entity linking.</p>
        <p>According to the close-world knowledge assumption (CWA) [22] of the knowledge graph,
in general no new statements (triples) can be added to an existing KG, except that predicting
relationships between existing, well-connected entities. In the light of this consideration, it is
essential to integrate some reasoning mechanism (KRS) that allows the KG to perform operation
within the statements inside the KB, to reach the so called closed-world Knowledge Graph
Completion. At the same time, once all the possible statements are saturated, additional new
statement could be added by considering external information sources, in order to enrich the
KB.</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>4. Implementation detail: A case study</title>
      <p>The approach has been implemented and validated, considering a case study relative to the
narrative domain, specifically books and article synopses describing short stories, fairy tales,
adventure stories. This section describes the methodology at a technical level to identify the
main characters, capture the relationships among them, places and events where they are
involved by exploiting linguistic features and qualities of the narrative prose.</p>
      <p>An enlarged view of the proposed pipeline of Figure 1 is shown in Figure 5 where the whole
high-level framework is described. A synergy between diferent methodologies and technologies
has been achieved: NLP activities are integrated with the Machine Learning models, designed
according to the principles of Information Retrieval and FAIR, through the Semantic Web
technologies (RDF, Turtle, OWL and SPARQL).</p>
      <p>The implementation is based on Python language and cover the core system shown in Figure
5. Input textual resources are downloaded from Kaggle narrative books, available in plain text
format; at the same time, the synoptic version of the book was retrieved from Wikipedia. Our
case study is applied to the book The Lord of the Rings. The text was extracted using a simple
web crawler that retrieve the content of the URL page; the data is cleaned using a standard
HTML/XML parser (Data Extraction).</p>
      <p>As shown in Figure 5, the Triple Construction component achieves the traditional POS-tagging
activities (Figure 2). The information extraction is performed by the Stanford Open-IE server
tool combined with Spacy library (en_core_web pre-trained models in English) for the extraction
of triples.</p>
      <p>The Tagging Pattern and Chunking Rules tasks from Triple Construction are ad-hoc designed;
these tasks also were implemented by exploiting WordNet. To give an example of pattern
extraction described in Figure 3 the text "But Frodo is still wounded in body and spirit" is
analyzed according to the regular expression  = (  * ,  * ,   * ), where the wildcard
character is a placeholder for possible variations of that POS-tags. The generated triple is
 = ( , , ).</p>
      <p>The triple extraction is also aimed at generating the widest set of triples from the sentence
analysis. Along with the definition of regular expression patterns for discovering simple phrase
chunks, the co-reference is also achieved: primary sentence with the same subject in secondary
sentences or simply sentences with pronoun are re-arranged to get triples with noun instead of
pronoun. The rule ( ,  ,   ) in Figure 4 allows us to obtain the pronoun PRP that will
be replaced by the right a noun ( in the previous sentence NN  = ℎ), to get the triple
2 = (ℎ, , ).</p>
      <p>Once the Triple Construction process is concluded, the generated triples are rearranged,
discarding duplicates (coming from the parallel tasks). The remaining triples are ordered
according to the same subject and then predicate and then stored in a plain CSV file for further
use.</p>
      <p>The Triple Enrichment component uses the CSV-generated file to carry out Algorithm 1. An
initial Named Entity Recognition task allows discriminating important entities among subject
and object, in the triples in order to discard irrelevant triples (i.e., triples with no named entity)
Algorithm 2 SPARQL Query example to URI and Label extraction</p>
      <p>SELECT ∗
WHERE { {</p>
      <p>{ {
} }
d b r : { word } r d f : t y p e dbo : F i c t i o n a l C h a r a c t e r .</p>
      <p>d b r : { word } dbp : name ? l a b e l .
} } UNION { {
{ { d b r : { word } dbo : w i k i P a g e R e d i r e c t s ? URI } }
UNION
{ { d b r : { word } dbo : w i k i P a g e D i s a m b i g u a t e s ? URI } } .
? URI r d f : t y p e dbo : F i c t i o n a l C h a r a c t e r .</p>
      <p>? URI r d f s : l a b e l ? l a b e l
} }</p>
      <p>FILTER ( la ng ( ? l a b e l ) = ' en ' )
and more important, to use that entities as parameter for the query, according to Algorithm
1. The individual entities are looked at DBpedia by submitting SPARQL queries, to retrieve
the semantic annotation (URI and label) corresponding to that entity. The goal is to make the
subject or object on each triple accessible resources, according to the Linked Data principles.</p>
      <p>The query shown in Algorithm 2 was submitted to the public SPARQL end-point 4 by
implementing the SPARQLWrapper to retrieve the DBpedia URI of the selected entities and the
rdfs:label. Let us notice that when a URI of an entity is not available, i.e., no result is returned
by the query, a customized URI is generated. In a similar way, the predicate is processed using
WordNet after reducing it to the infinitive form, e.g., the several tenses kills, killed, killing
become the infinite form kill. After these activities, a semantic knowledge base (called RDF KB)
should be available.</p>
      <p>The resulting RDF KB is passed to the KGE models (Embeddings Training in Figure 5 to
get the embeddings on the RDF triple-based KB. Embedding models such as ComplEX, TransE,
and DistMult were trained to compare and evaluate the results across this implementation. The
training was achieved and evaluated by using the evaluation proposed by the KG Embeddings
of the framework Ampligraph [28].
4.0.1. Triple Storage:
An important role was assumed by the storage component, that allows to store all the
intermediate version of the triples generated. In a nutshell, triples generated in the Triple Construction
component (Section 3.1) are stored in CSV format (to reuse them later); then, after the the Triple
Enrichment (Section 3.2), the resulting triples are stored semantically, namely in RDF/Turtle
languages. RDF-based triples can be e imported into the NEO4J5 by the neosemantics plugin
and then the resulting knowledge graph can be graphically displayed into the GUI This last</p>
      <sec id="sec-4-1">
        <title>4DBpedia SPARQL end-point - https://dbpedia.org/sparql 5https://neo4j.com/v2/</title>
        <p>storage task is crucial for reusing the KB for later validation, charts generation, query execution,
and further operations.
4.0.2. Source Code:
A demo for the implementation of this project is available on GitHub. The usage instructions
are consigned on the repository6 and the produced results (KBs) should be published under the
CC-BY-SA license.</p>
        <sec id="sec-4-1-1">
          <title>4.1. Knowledge Graph Completion Evaluation</title>
          <p>The KB validation is performed by implementing a cross-graph representation learning
approach [29] by embedding triples based on the semantic meaning of the KB; the representation
is done by estimating a confident score in each statement based on a degree of correctness.
This estimation is calculated by exploiting the KGE models and the corresponding evaluation
metrics over the discovered KB.</p>
          <p>First, the validation is accomplished by considering the output of each tasks of the Triple
Construction component and setting a pair-wise comparison among −  , −  ,
− ℎ through the trained KGE models, with the purpose of measure the
correspondence between the discovered knowledge. Then, to assess the generated knowledge base, new
triples are added to the KGE models once trained the trustworthiness (i.e., how they are true) of
these triples. These new triples are called "synthetic", because they are manually generated,
are used to perform link predictions queries of the form  = (?, , ?). The synthetic triples
are divided into two groups, positive ( , existing) and negatives (, not existing, or
unlikely to be true). Known learning-to-rank metrics to assess the performance of KGE models
are as follows.</p>
          <p>1 ∑|︁| 1
MRR = (1) HITS@N = | ∈  :  &lt; | (2)</p>
          <p>|| =1  ||</p>
          <p>The Mean Reciprocal Rank (MRR) is a statistical measure for assessing the quality of a list
of possible answers to a sample of queries, sorted by probability of correctness. MRR assume
value equal to 1 if a relevant answer was retrieved at rank 1; the intention is to measure the
correctness of each of the proposed scenarios using   to validate source knowledge against
the validation dataset. The  @ measures the percent of triples that were correctly
ranked in the top  . Besides, the combination with  , with two diferent coeficients
 = 5 and  = 3 to measure the ranking of the entities part of the statement (S, O) in the
validation dataset at the time of link prediction.</p>
        </sec>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>5. Experiment Design and Results</title>
      <sec id="sec-5-1">
        <title>5.1. Triple Discovery</title>
        <p>For the validation of the KBC process, let us focus on the KB generated by the Triple Construction
component described in Section 3.1. After the basic POS tagging tasks, the three sub-tasks,</p>
        <sec id="sec-5-1-1">
          <title>6Github Repository - https://github.com/d1egoprog/Text2KG</title>
          <p>Information Extraction, Chunking Rules and Tagging Pattern Execution generates statements for
the graph construction, the statements are grouped in  ,  , ℎ, respectively.</p>
          <p>The triples generated by using the Information Extraction ( ) are approximately 75% of
the discovered triples. The remaining 25% can be split between the triples (about 10% of the
total KB generated) coming from the Chunking Rules (ℎ) and those (around 15%) from
Tagging Pattern components ( ). Overlapping statements represent 1% of the triples
discovered.</p>
        </sec>
      </sec>
      <sec id="sec-5-2">
        <title>5.2. KG Completion evaluation approach</title>
        <p>.</p>
        <p>The results suggest that the validation of the synthetic triples produces high values (about
0.95) of   for the positive   triples and 0 for the negative   triples. The synthetic
statements appear to accurately reflect the knowledge discovered by the methodology and the
correspondence implementation, and the positive statements are potential candidates to feed
into the existing knowledge base.</p>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>6. Conclusions and Future Work</title>
      <p>This paper proposes unsupervised knowledge construction from domain-specific knowledge
given a natural language text. In particular, a case study is designed on a narrative text, exploiting
features unique to prosaic text. The text was parsed and basic triples, representing the core
part (subject, predicate and object) of the main sentences are extracted. By Semantic Web
technologies, the triple are semantically annotated to be linked and navigable into the Linked
Data cloud. At that point, Knowledge graph embedding models have been exploited to extend
the potential of the collected triples by verifying and validating the so generated knowledge.
Performance is assessed by cross-validation, scoring functions and accuracy on unseen triples.
0.53
0.40
0.42
0.28
0.40
0.28
TransE
0.92
0.01</p>
      <p>MRR</p>
      <p>MRR
0.63
0.48
0.52
0.30
0.53
0.33
MRR</p>
      <p>The work provides a general methodological approach to automatically build a knowledge
base, on a preferred domain, given in textual resources. It allows the creation of diferent types
of KBs. It can be leveraged to build ad-hoc knowledge bases, tailored to a specific domain.
Question-answering systems can act as validation systems when verification of the veracity
and reliability (degree of truth) of a given statement is required, for example, for the discovery
of fake news or just for fact-checking.</p>
      <p>As future work, the generation and enrichment of triples by querying existing Open
Knowledge bases will be improved, along with the more challenging goal of enhancing the degree of
confidence in the KB by implementing an automatic validation method.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>L.</given-names>
            <surname>Ehrlinger</surname>
          </string-name>
          , W. Wöß,
          <article-title>Towards a definition of knowledge graphs</article-title>
          ,
          <source>in: Procedings of 12th International Conference on Semantic Systems (SEMANTiCS2016)</source>
          , volume
          <volume>1695</volume>
          ,
          <string-name>
            <surname>CEUR-WS</surname>
          </string-name>
          ,
          <year>2016</year>
          , pp.
          <fpage>1</fpage>
          -
          <lpage>4</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>A.</given-names>
            <surname>Hogan</surname>
          </string-name>
          , E. Blomqvist,
          <string-name>
            <given-names>M.</given-names>
            <surname>Cochez</surname>
          </string-name>
          ,
          <string-name>
            <surname>C. D'Amato</surname>
            , G. de Melo,
            <given-names>C.</given-names>
          </string-name>
          <string-name>
            <surname>Gutierrez</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          <string-name>
            <surname>Kirrane</surname>
            ,
            <given-names>J. E. L.</given-names>
          </string-name>
          <string-name>
            <surname>Gayo</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          <string-name>
            <surname>Navigli</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          <string-name>
            <surname>Neumaier</surname>
            ,
            <given-names>A.-C. N.</given-names>
          </string-name>
          <string-name>
            <surname>Ngomo</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Polleres</surname>
            ,
            <given-names>S. M.</given-names>
          </string-name>
          <string-name>
            <surname>Rashid</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Rula</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          <string-name>
            <surname>Schmelzeisen</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          <string-name>
            <surname>Sequeda</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          <string-name>
            <surname>Staab</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Zimmermann</surname>
          </string-name>
          ,
          <article-title>Knowledge Graphs, number 2 in Synthesis Lectures on Data, Semantics, and</article-title>
          <string-name>
            <surname>Knowledge</surname>
          </string-name>
          , Morgan &amp; Claypool,
          <year>2021</year>
          . doi:
          <volume>10</volume>
          .2200/S01125ED1V01Y202109DSK022.
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>B.</given-names>
            <surname>Lee</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Zhang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Poleksic</surname>
          </string-name>
          , L. Xie,
          <article-title>Heterogeneous Multi-Layered Network Model for Omics Data Integration and Analysis, Frontiers in Genetics 0 (</article-title>
          <year>2020</year>
          )
          <article-title>1381</article-title>
          . doi:
          <volume>10</volume>
          .3389/ FGENE.
          <year>2019</year>
          .
          <volume>01381</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>M. D.</given-names>
            <surname>Wilkinson</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Dumontier</surname>
          </string-name>
          ,
          <string-name>
            <given-names>I. J.</given-names>
            <surname>Aalbersberg</surname>
          </string-name>
          , G. Appleton,
          <string-name>
            <given-names>M.</given-names>
            <surname>Axton</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Baak</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Blomberg</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. W.</given-names>
            <surname>Boiten</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L. B. da Silva</given-names>
            <surname>Santos</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P. E.</given-names>
            <surname>Bourne</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Bouwman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A. J.</given-names>
            <surname>Brookes</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Clark</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Crosas</surname>
          </string-name>
          ,
          <string-name>
            <given-names>I.</given-names>
            <surname>Dillo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Dumon</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Edmunds</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C. T.</given-names>
            <surname>Evelo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Finkers</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>GonzalezBeltran</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A. J.</given-names>
            <surname>Gray</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Groth</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Goble</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. S.</given-names>
            <surname>Grethe</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Heringa</surname>
          </string-name>
          , P. A.
          <string-name>
            <surname>t Hoen</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          <string-name>
            <surname>Hooft</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          <string-name>
            <surname>Kuhn</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          <string-name>
            <surname>Kok</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          <string-name>
            <surname>Kok</surname>
            ,
            <given-names>S. J.</given-names>
          </string-name>
          <string-name>
            <surname>Lusher</surname>
            ,
            <given-names>M. E.</given-names>
          </string-name>
          <string-name>
            <surname>Martone</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Mons</surname>
            ,
            <given-names>A. L.</given-names>
          </string-name>
          <string-name>
            <surname>Packer</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          <string-name>
            <surname>Persson</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          <string-name>
            <surname>Rocca-Serra</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Roos</surname>
            , R. van Schaik,
            <given-names>S. A.</given-names>
          </string-name>
          <string-name>
            <surname>Sansone</surname>
            , E. Schultes,
            <given-names>T.</given-names>
          </string-name>
          <string-name>
            <surname>Sengstag</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          <string-name>
            <surname>Slater</surname>
            , G. Strawn,
            <given-names>M. A.</given-names>
          </string-name>
          <string-name>
            <surname>Swertz</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Thompson</surname>
            ,
            <given-names>J. Van Der</given-names>
          </string-name>
          <string-name>
            <surname>Lei</surname>
            ,
            <given-names>E. Van Mulligen</given-names>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Velterop</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Waagmeester</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Wittenburg</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Wolstencroft</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Zhao</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Mons</surname>
          </string-name>
          ,
          <article-title>Comment: The FAIR Guiding Principles for scientific data management and stewardship</article-title>
          ,
          <source>Scientific Data</source>
          <volume>3</volume>
          (
          <year>2016</year>
          )
          <fpage>1</fpage>
          -
          <lpage>9</lpage>
          . doi:
          <volume>10</volume>
          .1038/sdata.
          <year>2016</year>
          .
          <volume>18</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>P. N.</given-names>
            <surname>Mendes</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Jakob</surname>
          </string-name>
          , C. Bizer,
          <article-title>DBpedia: A multilingual cross-domain knowledge base</article-title>
          ,
          <source>in: Proceedings of the 8th International Conference on Language Resources and Evaluation</source>
          ,
          <string-name>
            <surname>LREC</surname>
          </string-name>
          <year>2012</year>
          ,
          <article-title>European Language Resources Association (ELRA</article-title>
          ), Istanbul, Turkey,
          <year>2012</year>
          , pp.
          <fpage>1813</fpage>
          -
          <lpage>1817</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>S.</given-names>
            <surname>Auer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Bizer</surname>
          </string-name>
          , G. Kobilarov,
          <string-name>
            <given-names>J.</given-names>
            <surname>Lehmann</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Cyganiak</surname>
          </string-name>
          ,
          <string-name>
            <surname>Z. Ives,</surname>
          </string-name>
          <article-title>DBpedia: A Nucleus for a Web of Open Data</article-title>
          ,
          <source>in: Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics)</source>
          , volume
          <volume>4825</volume>
          LNCS, Springer, Berlin, Heidelberg,
          <year>2007</year>
          , pp.
          <fpage>722</fpage>
          -
          <lpage>735</lpage>
          . doi:
          <volume>10</volume>
          .1007/978-3-
          <fpage>540</fpage>
          -76298-0\ _
          <fpage>52</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>H.</given-names>
            <surname>Turki</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Shafee</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. A.</given-names>
            <surname>Hadj Taieb</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. Ben</given-names>
            <surname>Aouicha</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Vrandečić</surname>
          </string-name>
          ,
          <string-name>
            <surname>D. Das</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          <string-name>
            <surname>Hamdi</surname>
          </string-name>
          ,
          <article-title>Wikidata: A large-scale collaborative ontological medical database</article-title>
          ,
          <source>Journal of Biomedical Informatics</source>
          <volume>99</volume>
          (
          <year>2019</year>
          )
          <article-title>103292</article-title>
          . doi:
          <volume>10</volume>
          .1016/j.jbi.
          <year>2019</year>
          .
          <volume>103292</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>F. M.</given-names>
            <surname>Suchanek</surname>
          </string-name>
          , G. Kasneci,
          <string-name>
            <surname>G.</surname>
          </string-name>
          <article-title>Weikum, YAGO: A Core of Semantic Knowledge</article-title>
          ,
          <source>in: Proceedings of the 16th international conference on World Wide Web - WWW '07</source>
          , ACM Press, New York, New York, USA,
          <year>2007</year>
          , pp.
          <fpage>697</fpage>
          -
          <lpage>706</lpage>
          . URL: https://dl.acm.org/doi/10.1145/ 1242572.1242667. doi:
          <volume>10</volume>
          .1145/1242572.
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>U. S.</given-names>
            <surname>Simsek</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Angele</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Kärle</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Opdenplatz</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Sommer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Umbrich</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Fensel</surname>
          </string-name>
          ,
          <article-title>Knowledge Graph Lifecycle: Building and Maintaining Knowledge Graphs</article-title>
          ,
          <source>in: Proceedings of the 2nd International Workshop on Knowledge Graph Construction, CEUR-WS</source>
          ,
          <year>2021</year>
          , p.
          <fpage>16</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>C.</given-names>
            <surname>Ré</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A. A.</given-names>
            <surname>Sadeghian</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Z.</given-names>
            <surname>Shan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Shin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Wang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Wu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Zhang</surname>
          </string-name>
          ,
          <article-title>Feature Engineering for Knowledge Base Construction,</article-title>
          . (
          <year>2014</year>
          ). arXiv:
          <volume>1407</volume>
          .
          <fpage>6439</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>V.</given-names>
            <surname>Leone</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            <surname>Siragusa</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L. Di</given-names>
            <surname>Caro</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Navigli</surname>
          </string-name>
          ,
          <article-title>Building semantic grams of human knowledge</article-title>
          ,
          <source>in: LREC 2020 - 12th International Conference on Language Resources and Evaluation, Conference Proceedings</source>
          ,
          <year>2020</year>
          , pp.
          <fpage>2991</fpage>
          -
          <lpage>3000</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>D. R.</given-names>
            <surname>Yanez</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Crispoldi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Onorati</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Ulpiani</surname>
          </string-name>
          , G. Fenza,
          <string-name>
            <given-names>S.</given-names>
            <surname>Senatore</surname>
          </string-name>
          ,
          <article-title>Enabling a Semantic Sensor Knowledge Approach for Quality Control Support in Cleanrooms</article-title>
          ,
          <source>in: CEUR Workshop Proceedings</source>
          , volume
          <volume>2980</volume>
          ,
          <string-name>
            <surname>CEUR-WS</surname>
          </string-name>
          ,
          <year>2021</year>
          , pp.
          <fpage>1</fpage>
          -
          <lpage>3</lpage>
          . URL: http://ceur-ws.
          <source>org/</source>
          Vol-
          <volume>2980</volume>
          /paper409.pdf.
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <given-names>M.</given-names>
            <surname>Nickel</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Murphy</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Tresp</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Gabrilovich</surname>
          </string-name>
          ,
          <article-title>A Review of Relational Machine Learning for Knowledge Graphs</article-title>
          ,
          <source>Proceedings of the IEEE</source>
          <volume>104</volume>
          (
          <year>2016</year>
          )
          <fpage>11</fpage>
          -
          <lpage>33</lpage>
          . doi:
          <volume>10</volume>
          .1109/JPROC.
          <year>2015</year>
          .
          <volume>2483592</volume>
          . arXiv:
          <volume>1503</volume>
          .
          <fpage>00759</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <surname>T.-P. Nguyen</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          <string-name>
            <surname>Razniewski</surname>
          </string-name>
          , G. Weikum,
          <article-title>Advanced Semantics for Commonsense Knowledge Extraction</article-title>
          ,
          <source>in: Proceedings of the Web Conference</source>
          <year>2021</year>
          , ACM, New York, NY, USA,
          <year>2021</year>
          , pp.
          <fpage>2636</fpage>
          -
          <lpage>2647</lpage>
          . doi:
          <volume>10</volume>
          .1145/3442381.3449827.
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <given-names>M.</given-names>
            <surname>Brockmeier</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Liu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Pateer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Hertling</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Paulheim</surname>
          </string-name>
          ,
          <article-title>On-Demand and Lightweight Knowledge Graph Generation - a Demonstration with DBpedia</article-title>
          ,
          <source>in: Proceedings of the Semantics</source>
          <year>2021</year>
          , volume
          <volume>2941</volume>
          ,
          <string-name>
            <surname>CEUR-WS</surname>
          </string-name>
          ,
          <year>2021</year>
          , p.
          <fpage>5</fpage>
          . arXiv:
          <volume>2107</volume>
          .
          <fpage>00873</fpage>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>