<!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>TOMATO : results of the 2023 OAEI evaluation campaign</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Philippe Roussille</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Olivier Teste</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>École 3iL</institution>
          ,
          <addr-line>Limoges</addr-line>
          ,
          <institution>Institut de Recherche en Informatique de Toulouse</institution>
          ,
          <addr-line>Toulouse</addr-line>
          ,
          <country country="FR">France</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Université Toulouse 2 Jean Jaurés, Institut de Recherche en Informatique de Toulouse</institution>
          ,
          <addr-line>Toulouse</addr-line>
          ,
          <country country="FR">France</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>This paper presents the results obtained by TOMATO in the OAEI 2023 evaluation campaign. We describe here the results in the Conference track. We report a general discussion on the results and future improvements of the system. TOMATO (TOolkit for MATching Ontologies) takes inspiration from previous work on ontology matching systems such as POMAP++ [1]. TOMATO is designed as a pairwise matcher, aligning pairs of input ontologies against each other. At its core, TOMATO utilizes machine learning approaches to learn from element similarities. In earlier versions, it focused mainly on stringbased similarity measures of ontology elements [2]. However, in 2023 we started working beyond this initial approach. While string similarities continue to provide baseline features, we have incorporated additional structural and semantic similarity measures. This includes leveraging relationships between ontology entities, as well as leveraging external knowledge sources. The goal is to move beyond solely lexical matching and capture more of the intended meaning during the alignment process. Lacking a robust ground truth beyond the reference alignment, this line of work was shelved temporarily to investigate supplemental evaluation methods. In this iteration of TOMATO, we took a more direct approach to developing the optimal matching strategy. Rather than starting with local strategies as in the previous year[3], our aim was to first identify the best global strategy across all entity types. To achieve this, we focused on empirically determining the most pertinent similarity measures to incorporate. In our evaluations, we considered a broader set of 11 measures: Levenshtein, Jaccard, Jaro-Winkler, cosine, iSub, dice, 3-gram, Monge-Elkan Levenshtein, Monge-Elkan Jaro-Winkler, and overlap coefficient. By systematically evaluating these measures in various combinations through our machine learning models, our goal was to arrive at the global configuration that performed best when</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Presentation</title>
      <sec id="sec-1-1">
        <title>1.1. Overview</title>
        <p>applied uniformly. Once identified, we could then examine how to potentially refine this global
strategy by incorporating localized decompositions based on entity characteristics, as we had
explored in earlier versions of TOMATO.</p>
        <p>This new evaluation-driven approach aimed to build up the optimal strategy incrementally,
starting from the best global foundation before incorporating targeted local enhancements. The
rationale was that this may yield stronger baseline results compared to our prior method of starting
with localized configurations.</p>
        <p>The workflow in TOMATO begins by taking as input two OWL ontologies to be aligned,
along with their associated reference RDF alignment files. These reference alignments provide
examples of entity matches that serve as ground truth for the learning process.</p>
        <p>TOMATO then prepares the data by combining all ontology entity pairs (both matched and
unmatched based on the references) into a single dataset. This set contains all possible entity
couples across the input ontologies, along with their reference match status.</p>
        <p>From here, TOMATO can be used in one of two modes:
1. Learning mode: A machine learning model is trained on the full mixed dataset to learn the
patterns of matching vs non-matching entities.
2. Matching mode: A pre-trained model is applied to new ontology entity pairs to predict
their alignment status.</p>
        <p>Unlike previous versions where we explored a variety of similarity measures, this year our
focus is on determining which measures are most pertinent to the matching task and which can
be eliminated.</p>
        <p>By fully combining all entity pairs and reference alignments upfront, TOMATO is able to learn
from all available matching examples without viewing the ontologies separately.</p>
      </sec>
      <sec id="sec-1-2">
        <title>1.2. Matching steps</title>
        <p>The initial step in TOMATO’s workflow is to parse and ingest the input ontologies. We leverage
the owlready2 Python library to build an in-memory representation containing all ontology
elements and relationships.</p>
        <p>Each entity such as classes, data properties and object properties is indexed via a unique
identifier, with the preferred identifier being the element’s label if present. As a fallback, the final
segment of the entity’s URI is used.</p>
        <p>Structural relationships between classes are also extracted and stored. This includes
superclasssubclass links as well as relations defined through object properties.</p>
        <p>By fully populating an internal graph structure in this way, TOMATO is able to consider
both lexical properties of entities as well as their positions and connections within the ontology
taxonomy during the matching process. This combined view aims to capture more contextual
evidence about intended semantic correspondence compared to considering elements in isolation.</p>
        <p>The loaded ontologies can then be queried as needed during the various steps of similarity
computation, model training and alignment prediction.</p>
        <sec id="sec-1-2-1">
          <title>1.2.1. Ontology Preprocessing</title>
          <p>As in prior iterations, we apply standard text preprocessing techniques to clean and normalize
entity labels before computing similarities. This includes:
• Converting CamelCase to snake_case
• Replacing non-alphanumeric symbols with spaces
• Performing English stemming
• Removing stop words</p>
          <p>However, unlike previous versions that employed matching strategies based on element types,
in this work we utilize K-means clustering as described below.</p>
        </sec>
        <sec id="sec-1-2-2">
          <title>1.2.2. Similarity Score Computation</title>
          <p>All possible entity pairs between the input ontologies are generated without regard to element
type (e.g. class vs property). For each pair, we compute similarities across several measures
(Levenshtein, Jaro-Winkler, etc.).</p>
          <p>New to this year, rather than hardcoding similarity computation strategies, we compute directly
over the multi-dimensional similarity space. As we showed last year, this will allow us to focus
on the worst possible outcome, which could be further improved in a case-by-case local strategy.</p>
        </sec>
        <sec id="sec-1-2-3">
          <title>1.2.3. Train and match</title>
          <p>Training a Model We use GridSearchCV from scikit-learn to determine the best combination
of similarity measures for predicting matches. The dataset is split 60/40 for training/testing with
10-fold cross validation. The reference alignments are used to label entity pairs as matches (1) or
non-matches (0). This labeled similarity matrix is fed to an SVM classifier to train a matching
model.</p>
          <p>
            The TOMATO system is based on a machine learning approach that exploits 60% of data for
training and 40% of data for testing. The training set is classicaly used to learn a model that
consists in finding an optimal weighting of different similarity measures. Clearly, we use a subset
of the reference alignments provided by OAEI that is considered as an overfitting. However, it
is important to consider that the obtained model never considered the 40% set aside for testing.
To avoid this overfitting, we plan to use external resources as ground truth during the training
phase[
            <xref ref-type="bibr" rid="ref4">4</xref>
            ].
          </p>
          <p>Computing Alignments A similarity matrix is constructed for the target ontology pair.
This matrix is then input to the pre-trained matching model, which outputs the predicted entity
alignments.</p>
          <p>Unlike previous versions, in this work we utilize a distributed approach to avoid crashes or
slowdowns when processing large or dense ontologies. The classification tasks are handled in
parallel across computational threads/processes for improved robustness and performance.</p>
        </sec>
      </sec>
      <sec id="sec-1-3">
        <title>1.3. Adaptations made for OAEI</title>
      </sec>
      <sec id="sec-1-4">
        <title>1.4. Technical Adaptations for OAEI</title>
        <p>In preparation for the OAEI evaluation, we focused on improving our ability to handle large
ontologies in a distributed manner. Previously, training classifiers on the full matching dataset
could lead to memory issues or lengthy processing times.</p>
        <p>Therefore, in this iteration we implemented a multi-threaded resampling scheme during model
training. The matching data is partitioned and resampled in parallel across CPU threads, with
intermediate results merged to update the shared model.</p>
        <p>Additionally, we experimentally found that training classifiers with a class imbalance favoring
non-matching examples (e.g. 90% negative, 10% positive) led to more effective models compared
to a balanced class distribution. This better reflects the natural skew in real-world ontology
alignments.</p>
        <p>To validate different modeling configurations, models trained with both global and local
strategies were considered. However, due to time constraints of the competition format, we only
submitted results using our global strategy models for evaluation.</p>
        <p>The enhancements to our data processing and sampling methodology aimed to enable TOMATO
to efficiently learn from very large ontologies in real-world settings, while still optimizing for
high matching accuracy.</p>
      </sec>
    </sec>
    <sec id="sec-2">
      <title>2. Evaluation of Class Balancing Techniques</title>
      <sec id="sec-2-1">
        <title>2.1. Class Imbalance Problem</title>
        <p>We face a significant class imbalance problem in our ontology matching task, where the number
of positive matches between ontologies is much smaller than the number of negative matches.
This poses challenges for training effective machine learning models.</p>
        <p>During model training, the non-matching or negative examples dominate the training data
distribution. As a result, models can become biased towards predicting negatives and fail to
properly learn from the minority positive class.</p>
      </sec>
      <sec id="sec-2-2">
        <title>2.2. Proposed Resampling Method</title>
        <p>To address class imbalance, we implement a resampling scheme during model training based on
a resampling proportion hyperparameter  .</p>
        <p>The dataset consists of positive matches labeled 1 and negative matches labeled 0. We partition
the negative examples into ⌊ 1⌋ subsets of size 1, where 1 is the number of positives.</p>
        <p>We then create a balanced training set by combining the positive examples with a randomly
selected negative subset. This ensures equal representation of both classes for learning. We vary
 to study its impact.</p>
      </sec>
      <sec id="sec-2-3">
        <title>2.3. Experiments and Results</title>
        <sec id="sec-2-3-1">
          <title>2.3.1. Raw results</title>
          <p>
            We train several models on matching data, varying  ∈ [
            <xref ref-type="bibr" rid="ref1">1, 100</xref>
            ]. Performance is evaluated using
macro/micro precision, recall and F1.
          </p>
          <p>Table shows optimal performance is achieved with  = 41, with macro F1=0.43. Lower 
leads to poor predictive ability for negatives, while higher  may worsen learning of positives.</p>
          <p>This table summarizes the key performance metrics for our models across different values of
the resampling proportion  , showing the optimal value is  =41.</p>
          <p>The macro F1 score is a weighted average of F1 scores calculated for each class individually,
giving equal importance to each class regardless of prevalence.</p>
          <p>The micro F1 score aggregates counts across all classes to determine a single F1 score. It
places more weight on accuracy for frequent, majority classes compared to macro F1 which
balances across classes.</p>
          <p>Together these metrics provide a more comprehensive assessment of model performance for
both frequent and rare classes in a multiclass classification problem like ontology matching.</p>
        </sec>
      </sec>
      <sec id="sec-2-4">
        <title>2.4. Analysis</title>
        <p>The resampling balances overall class distributions during training, addressing biases towards
negatives. Higher proportions improve discrimination of matches by emphasizing difficult positive
examples. Optimally, sufficient data from both classes is provided for robust learning.</p>
        <p>However, residual recall indicates mismatches remain challenging. Future work involves
combining resampling with techniques like data augmentation to further boost positive example
diversity and learning.</p>
        <p>In conclusion, resampling addresses class imbalance effectively, enhancing ontology matching
model performance. Careful tuning of resample rates leads to improved classification accuracy.</p>
      </sec>
      <sec id="sec-2-5">
        <title>2.5. OAEI results</title>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>3. Evaluation Results for the OAEI 2023 Conference Track</title>
      <p>This section analyzes the evaluation results published on the OAEI 2023 Conference Track results
page (https://oaei.ontologymatching.org/2023/results/conference/).</p>
      <sec id="sec-3-1">
        <title>3.1. Participating Matching Systems</title>
        <p>A total of 11 matching systems participated in this track and produced alignments over the
Conference domain ontologies: ALIN, AMD, GraphMatcher, LogMap, LogMapLt, LSMatch,
Matcha, OLaLa, ProMatch, SORBETMtch, and TOMATO.</p>
      </sec>
      <sec id="sec-3-2">
        <title>3.2. Evaluation Based on Crisp Reference Alignments</title>
        <p>The systems were evaluated based on the main reference alignment rar2-M3 using precision,
recall, F-measure, and other metrics.</p>
        <p>TOMATO achieved a precision of 0.57, recall of 0.47, and F-measure of 0.52 on rar2-M3 as
shown in Table 2. This placed it below the StringEquiv baseline but above ProMatch. Compared
to 2022 results in Table 3, TOMATO’s precision and F-measure increased slightly while recall
decreased.</p>
        <p>TOMATO’s performance remains in the mid-range. While recall could improve, gains were
seen in precision and F-measure compared to 2022.</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>4. Conclusion and Future Work</title>
      <p>In this paper, we presented the results of the TOMATO ontology matching system on the OAEI
2023 Conference track benchmark. TOMATO employs a machine learning approach combined
with strategy selection based on domain characteristics.</p>
      <p>Our evaluation showed that TOMATO achieved moderate performance. While its precision
and F-measure improved slightly over last year, recall decreased. Nonetheless, TOMATO
demonstrated the utility of adapting its strategy based on ontology features.</p>
      <p>There remain opportunities for enhancing TOMATO’s matching capabilities. In future work,
we plan to explore:
• Additional machine learning classifiers and similarity measures
• Deeper analysis of ontology structures to better leverage structural context
• Techniques like data augmentation to improve generalization of learned models
• Integration of external sources like knowledge graphs to strengthen matching
We are optimistic that such improvements can lift TOMATO’s rankings on this benchmark
by further refining its abilities to identify correct mappings. Continued participation in OAEI
also allows ongoing evaluation versus state-of-the-art matchers. Overall, the results provide
motivation to push the boundaries of adaptive ontology matching.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>A.</given-names>
            <surname>Laadhar</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Ghozzi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>I.</given-names>
            <surname>Megdiche</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Ravat</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Teste</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Gargouri</surname>
          </string-name>
          , POMap++
          <article-title>results for OAEI 2019: fully automated machine learning approach for ontology matching</article-title>
          ,
          <source>in: 14th International Workshop on Ontology Matching co-located with the International Semantic Web Conference (OM@ISWC</source>
          <year>2019</year>
          ), Auckland, New Zealand,
          <year>2019</year>
          , pp.
          <fpage>169</fpage>
          -
          <lpage>174</lpage>
          . URL: https://hal.archives-ouvertes.fr/hal-02942337.
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>M.</given-names>
            <surname>Cheatham</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Hitzler</surname>
          </string-name>
          ,
          <article-title>String similarity metrics for ontology alignment</article-title>
          , in: H.
          <string-name>
            <surname>Alani</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          <string-name>
            <surname>Kagal</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Fokoue</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          <string-name>
            <surname>Groth</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          <string-name>
            <surname>Biemann</surname>
            ,
            <given-names>J. X.</given-names>
          </string-name>
          <string-name>
            <surname>Parreira</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          <string-name>
            <surname>Aroyo</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          <string-name>
            <surname>Noy</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          <string-name>
            <surname>Welty</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          Janowicz (Eds.),
          <source>The Semantic Web - ISWC 2013</source>
          , Springer Berlin Heidelberg, Berlin, Heidelberg,
          <year>2013</year>
          , pp.
          <fpage>294</fpage>
          -
          <lpage>309</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>P.</given-names>
            <surname>Roussille</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Teste</surname>
          </string-name>
          ,
          <article-title>Tomato: results of the 2022 oaei evaluation campaign</article-title>
          ,
          <source>in: 17th International Workshop on Ontology Matching co-located with the International Semantic Web Conference (OM@ISWC</source>
          <year>2022</year>
          ), Hangzhou, China,
          <year>2022</year>
          , pp.
          <fpage>1</fpage>
          -
          <lpage>13</lpage>
          . URL: http://disi. unitn.it/~pavel/om2022/papers/oaei22_paper13.pdf.
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>A.</given-names>
            <surname>Laadhar</surname>
          </string-name>
          ,
          <article-title>Local matching learning of large scale biomedical ontologies</article-title>
          ,
          <source>Ph.D. thesis</source>
          , Université Paul Sabatier - Toulouse III,
          <year>2019</year>
          . URL: https://theses.hal.science/tel-02651332.
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>