<!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 />
    <article-meta>
      <title-group>
        <article-title>KGMatcher Results for OAEI 2021</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Omaima Fallatah</string-name>
          <email>oafallatah@uqu.edu.sa</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Ziqi Zhang</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Frank Hopfgartner</string-name>
          <email>f.hopfgartnerg@sheffield.ac.uk</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Department of Information Systems, Umm Al Qura University</institution>
          ,
          <country country="SA">Saudi Arabia</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Information School, The University of She eld</institution>
          ,
          <addr-line>She eld</addr-line>
          ,
          <country country="UK">UK</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2021</year>
      </pub-date>
      <abstract>
        <p>KGMatcher is a scalable and domain independent matching tool that matches the schema (classes) of larger Knowledge Graphs by following a hybrid matching approach. KGMatcher is composed of an instance-based matcher which only uses annotated instances of knowledge graph classes to generate candidate class alignments, and a stringbased matcher. This year is the rst OAEI participation of KGMatcher, and it is the best performing system on the common knowledge graph track. Although KGMatcher results are promising, further improvements of the matching techniques' and matcher combination can be introduced.</p>
      </abstract>
      <kwd-group>
        <kwd>Knowledge Graphs</kwd>
        <kwd>Instance-based Ontology Matching</kwd>
        <kwd>Machine Learning</kwd>
        <kwd>Schema Matching</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>1.1</p>
    </sec>
    <sec id="sec-2">
      <title>Presentation of the system</title>
      <sec id="sec-2-1">
        <title>State, purpose, general statement</title>
        <p>
          Combining di erent matching techniques is a common practice in ontology
matching tools. Matching techniques are divided into three main categories [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ]: (1)
Element level techniques which discover similar entities by processing textual
annotation of ontologies entities, (2) Structural level techniques which study
the relation between ontologies entities to generate candidate similar pairs, and
Finally (3) Extensional or Instance based techniques which utilize populated
instances, i.e., (ABox) data to generate alignments at schema level (TBox).
        </p>
        <p>
          The matcher proposed here is a hybrid approach that combines an element
level matcher to an instance-based one. The rst matcher uses entity labels to
generate candidate pairs, and the latter produces candidate class alignments
by only using annotated instance names. While conventional ontologies mainly
focus on modelling classes and properties, Knowledge Graphs (KGs), particularly
those available on the web, are large-scale and describes numerous instances [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ].
Following a self-supervised and two-way classi cation approach, the presented
matcher trains a classi er using each KG instances as training data. Each trained
Copyright © 2021 for this paper by its authors. Use permitted under Creative
Commons License Attribution 4.0 International (CC BY 4.0).
        </p>
        <p>
          KG classi er can then be used to classify any instance name into one of the classes
from that KG. This approach is domain independent and is capable of coping
with KGs with unbalanced populations (for details, see [
          <xref ref-type="bibr" rid="ref4">4</xref>
          ]). This makes the
matcher particularly useful for matching large KGs with numerous populated
and overlapping instances such as DBpedia [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ] and YAGO [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ].
1.2
        </p>
      </sec>
      <sec id="sec-2-2">
        <title>Speci c techniques used</title>
        <p>Given two input knowledge graphs, O and O0, where O contains a set of classes
O = fC0 ; C1 ; ::; COig, and each class contains a set of instances COi = fe0; ei1; :::; eing.
i
SimilarlOy, OO0contains a set of classes such that O0 = fCO00 ; CO10 ; ::; COj0 g where
CO0 = fej0; ej1; :::; ejmg. KGMatcher has two main components: an
instancej
based matcher and a name matcher. The work ow of KGMatcher is
illustrated in gure 1.
Preprocessing Given the two input KGs, the matcher starts by parsing and
indexing the lexical data of the two KGs separately. Following the standard free
text search/index approach, an index is created for each KG where each class is
treated as a document and the content of each `document` is the concatenation
of the class's instance labels. In addition to the standard text cleaning processes,
a word segmentation method is applied in order to separate multi-word entities,
e.g., academicfield. Using a dictionary, the method is able to infer the spaces
between words and replace them with a space.
Instance-based Matcher The rst component of KGMatcher belongs to the
extensional matcher category. It uses a self-supervised machine learning
approach to map KG classes based on their instances overlap. The matching is
done in a two-way classi cation method where a KG classi er is trained using
one KG's instances data. Later on, that classi er is used to classify any instance
name into one of the classes from that KG.</p>
        <p>
          { Exact Name Filtering. The matcher starts by applying an exact name lter
to exclude class labels that exist in both input KGs. Given the large number
of classes in typical KGs, this step works as a blocking strategy which reduces
the search space of the instance-based matcher.
{ Undersampling. As the instance distribution in KGs tends to be highly
imbalanced, the goal of this step is to balance the number of populated instances
in the input KGs to avoid biased classi cation results. KGMatcher follows a
resampling strategy aimed at undersampling classes with instances number
exceeding the average number of instances per class in that KG, i.e., majority
classes. The standard TF-IDF [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ] method which often deployed to measure
word relevance in a collection of documents is used to undersample KGs
classes. Here, the TF-IDF of a word in each class represents the relevance
of that word in a particular class in comparison to other classes in the KG.
Therefore, for each majority class, the most frequent words in terms of
TFIDF score are used to undersample its instance names. Therefore, instance
names that do not compose any of the words with high TF-IDF scores are
discarded. As a result, a balanced and indicative set of a KG instance names
are obtained to be used as training data. For details about this step, see [
          <xref ref-type="bibr" rid="ref4">4</xref>
          ].
{ Training KG classi ers. Here, a KG classi er will be separately trained for
each input KG using the previously undersampled data. Pre-trained word
embeddings are used here as features to capture and present the semantics of
KG instance names. Compared to traditional feature representation
methods, word embedding and language models are recognized as e ective ways
to capture the semantic similarity of words. KGMatcher is able to train two
types of classi ers, a Deep Neural Network (DNN) model3 4 similar to other
successful NLP tasks such as [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ] and [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ], and a pre-trained BERT model [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ].
KGMatcher will automatically opt to using the BERT model if a GPU is
available during runtime. The output of this phase is two classi ers, CLSO
and CLSO0 trained using the instances from the two input KGs O, and O0
respectively.
3 The parameters selected for the DNN model: an input layer of pre-trained word
embedding model followed by four fully connected hidden layers with 128, 128, 64,
32 recti ed linear units. A dropout layer of 0.2 is added between each pair of dense
layers for regulation. Finally, a softmax layer for multi-class classi cation, taking the
total number of classes in the KG we are training a classi er for.
4 The input layer is the Google News token-based model https://tfhub.dev/google/
tf2-preview/nnlm-en-dim128/1
{ KG1 alignment elicitation is the process of generating candidate pairs using
the classi er trained on the rst input KG. Candidate pairs are generated
by iteratively applying the classi er CLSO to instances in the other KG's
classes. As a result, each instance name in COj0 is now classi ed into a class in
O. The candidate pair (COi,COj0 ) is added to the rst candidate alignments
set AO!O0 if the majority of COj0 were classi ed as instances of COi. A
similarity score between [
          <xref ref-type="bibr" rid="ref1">0,1</xref>
          ] is obtained using the percentage of instances
that voted for a particular class. Therefore, if 600 out of 1000 instance names
j
in CO0 were voting for, COi the similarity score of that pair will be 0.6.
{ KG2 alignment elicitation is similar to the above illustrated elicitation
process. However, the roles of the two KGs are reversed where CLSO0 , i.e., the
classi er trained on the second KG (O0), is applied to O instances in order
to obtain the second candidate alignment set AO0!O.
{ Similarity computing is where KGMatcher combines the two candidate
alignment sets resulted from the two-way classi cation method. First, the matcher
separately stores each directional alignment in an alignment matrix of a
jOj:jO0j dimension. The two matrices are then aggregated into one matrix by
taking the average similarity score of each pair. For example, if (CO6,CO30 ,0.88)
in AO!O0 and (CO50 ,CO3, 0.64) in AO0!O) their aggregated similarity value
will be 0.76. Consequently, the nal alignments for this matcher are chosen by
following the state-of-the-art automatic nal alignment selection approach
introduced in [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ]. Given an alignment matrix, this method iteratively select
the pair with the highest similarity score for each class in both KGs.
Name Matcher The second component of KGMatcher is an element-level
matcher, which measures the similarity of KG class labels. First, the edit distance
of each class pair is measured, and then their semantic similarity is measured by
a word embedding method. For the edit distance, KGMatcher calculates the
levenshtein distance for each class pair. Regarding the word embedding similarity,
a pre-trained word2vec model is used to represent class labels before measuring
their cosine similarities. The semantic similarity is measured in a Vector Space
Model, where words with high semantic relations are often represented closer
to each other. In the case of multi-words labels, the vector representation of
each word composing the label is aggregated with an element-wise average of
the composing word vectors. Finally, the maximum of the two similarity
measures is chosen as the name similarity of that pair. The threshold value of the
name matcher is set to 0.8. To illustrate, if the word embedding similarity of
(RailwayStation,TrainStation) is 0.83 while their levenshtein distance is 0.56,
the maximum similarity value, i.e., the word embedding similarity which is also
higher than 0.8. Nonetheless, in case that the two similarity scores are lower
than the threshold, that pair will be excluded from the candidate alignment.
Post Processing KGMatcher combines the results generated from the two
component matchers by following the same method described earlier in 2 to
combine the two instance classi cation alignments.
        </p>
        <p>Instance Matching For the OAEI participation, we have adapted KGMatcher
to also match the instances of KGs. The instance matching component is very
simple. First, standard text preprocessing techniques such as lowercasing, and
removing stopwords and non-alphanumeric characters are applied. Then,
KGMatcher generates candidate instance pairs based on the existence of the label
in the opposite knowledge graph.
1.3</p>
      </sec>
      <sec id="sec-2-3">
        <title>Adaptations made for the evaluation</title>
        <p>
          KGMatcher is mainly developed with Python. To facilitate reusing and
evaluating KGMatcher and for the OAEI submission, KGMatcher was packaged using
a SEALS client. The wrapping services from the Matching EvaLuation Toolkit
(MELT) [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ] was used to warp KGMatcher 's Python-process, and to generate the
SEALS package.
2
        </p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Results</title>
      <p>In this section, we present and discuss the results for each of the OAEI tracks
where KGMatcher was able to produce a non-empty alignment le. The results
include the following OAEI tracks: Conference, Knowledge Graph, and Common
Knowledge Graphs track.
2.1</p>
      <sec id="sec-3-1">
        <title>Conference</title>
        <p>In the Conference track, when following the rar2-M3 evaluation, KGMatcher F1
score (0.52) is slightly lower than both baselines, i.e., StringEquiv (0.53) and edna
(0.56). This particular evaluation, i.e., M3 takes into consideration both class and
property matches. The fact that KGMatcher does not match property justi es
the negative impact of the undiscovered property alignments on the matcher
performance on this task. Further, given that the Conference track datasets do
not include enough number of instances to apply the instance-based matcher,
the name matcher is the only matcher applied to map classes. In terms of the
new experimental cross-domain test case of mapping DBpedia and OntoFram,
KGMatcher performance (0.55) better than both baselines StringEquiv and edna
which have the scores 0.42 and 0.45 respectively.
2.2</p>
      </sec>
      <sec id="sec-3-2">
        <title>Knowledge Graph</title>
        <p>In the Knowledge Graph track, KGMatcher was able to generate results for
all the 5 test cases at both classes and instances level only. In terms of class
matching, the matcher yields satisfactory results, with 0.79 for F1 score. The
added instance matcher has positively impacted the overall matcher result on
this task, with a precision of 0.94, a recall of 0.66 and F1 of 0.82.</p>
      </sec>
      <sec id="sec-3-3">
        <title>Common Knowledge Graphs</title>
        <p>Along with other 6 matchers, KGMatcher was able to complete the task of
matching the classes from two cross-domain and common KGs. KGMatcher
obtained a precision of 0.97 and a recall of 0.91. With an F1 score of 0.94,
KGMatcher is the best performing matcher on this track.
3</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>General comments</title>
      <p>
        The results of KGMatcher has been very encouraging. In the common
knowledge graph track, it achieves outstanding results. This indicates that our hybrid
approach, utilizing instances data to map KG classes, is able to outperform
systems that use other matchers' combination. It is important to note that the
performance of KGMatcher instance-based component depends on the dataset
nature. Since KGMatcher is learning KG classi ers by using general pretrained
word embedding models, the more representative the KG instances of real-world
entities, the better are the instance classi cation results. Figure 2 shows the
different between the performance when classifying instances from common KGs,
e.g., NELL, compared to a single domain KG from the knowledge graph track.
Note that the latter mainly annotates classes in the entertainment domain [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ].
(a)
(b)
      </p>
      <p>In future versions of KGMatcher, we would like to improve the combination
of techniques used within the name matcher. Currently, this component is rather
simple and unable to discover matching pairs with high lexical complexity. This
has also a ected the matcher's performance on datasets where instance data are
not existing or di cult to classify. Additionally, improving the instance-based
matcher by further studying other sampling approaches and experimenting with
other machine learning methods, would likely improve the overall performance
of the matcher.
4</p>
    </sec>
    <sec id="sec-5">
      <title>Conclusion</title>
      <p>As part of OAEI 2021, this paper presents KGMatcher, a matching tool that
utilizes instance data annotated within large KGs to map their classes. The
process is done by learning KG classi ers, which are able to classify instances
into a particular KG class. The results suggest that a hybrid approach that
incorporate an instance-based technique can be highly e ective for matching
large cross-domain KGs.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Bizer</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lehmann</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Isele</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jakob</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jentzsch</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kontokostas</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mende</surname>
            ,
            <given-names>P.N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hellmann</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Morsey</surname>
            , M., van Kleef,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Auer</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bizer</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          :
          <article-title>DBpedia { A Large-scale, Multilingual Knowledge Base Extracted from Wikipedia</article-title>
          . Semantic Web pp.
          <volume>1</volume>
          {
          <issue>5</issue>
          (
          <year>2012</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Collobert</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Weston</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bottou</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Karlen</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kavukcuoglu</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kuksa</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>Natural language processing (almost) from scratch</article-title>
          .
          <source>Journal of machine learning research 12(ARTICLE)</source>
          ,
          <volume>2493</volume>
          {
          <fpage>2537</fpage>
          (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Fallatah</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zhang</surname>
            ,
            <given-names>Z.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hopfgartner</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          :
          <article-title>A gold standard dataset for large knowledge graphs matching</article-title>
          .
          <source>In: OM@ISWC</source>
          (
          <year>2020</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Fallatah</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zhang</surname>
            ,
            <given-names>Z.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hopfgartner</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          :
          <article-title>A hybrid approach for large knowledge graphs matching</article-title>
          .
          <source>In: OM@ISWC</source>
          (
          <year>2021</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Gulic</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vrdoljak</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Banek</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Cromatcher: An ontology matching system based on automated weighted aggregation and iterative nal alignment</article-title>
          .
          <source>Journal of Web Semantics</source>
          <volume>41</volume>
          ,
          <issue>50</issue>
          {
          <fpage>71</fpage>
          (
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Hertling</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Paulheim</surname>
          </string-name>
          , H.:
          <article-title>The knowledge graph track at oaei</article-title>
          .
          <source>In: European Semantic Web Conference</source>
          . pp.
          <volume>343</volume>
          {
          <fpage>359</fpage>
          . Springer (
          <year>2020</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Hertling</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Portisch</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Paulheim</surname>
          </string-name>
          , H.:
          <article-title>MELT - matching evaluation toolkit</article-title>
          .
          <source>In: Semantic Systems. The Power of AI and Knowledge Graphs - 15th International Conference</source>
          . pp.
          <volume>231</volume>
          {
          <issue>245</issue>
          (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Maiya</surname>
            ,
            <given-names>A.S.:</given-names>
          </string-name>
          <article-title>ktrain: A low-code library for augmented machine learning</article-title>
          .
          <source>arXiv preprint arXiv:2004</source>
          .
          <volume>10703</volume>
          (
          <year>2020</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Minaee</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kalchbrenner</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cambria</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nikzad</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chenaghlu</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gao</surname>
          </string-name>
          , J.:
          <article-title>Deep learning based text classi cation: A comprehensive review</article-title>
          .
          <source>arXiv preprint arXiv:2004</source>
          .
          <volume>03705</volume>
          (
          <year>2020</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Otero-Cerdeira</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rodr</surname>
            guez-Mart nez,
            <given-names>F.J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gomez-Rodr guez</surname>
          </string-name>
          , A.:
          <article-title>Ontology matching: A literature review</article-title>
          .
          <source>Expert Systems with Applications</source>
          pp.
          <volume>949</volume>
          {
          <issue>971</issue>
          (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11. Schutze, H.,
          <string-name>
            <surname>Manning</surname>
            ,
            <given-names>C.D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Raghavan</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          : Introduction to information retrieval, vol.
          <volume>39</volume>
          . Cambridge University Press Cambridge (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Tanon</surname>
            ,
            <given-names>T.P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Weikum</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Suchanek</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          :
          <article-title>Yago 4: A reason-able knowledge base</article-title>
          .
          <source>In: European Semantic Web Conference</source>
          . pp.
          <volume>583</volume>
          {
          <fpage>596</fpage>
          . Springer (
          <year>2020</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>