<!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>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Xiaowen Wang</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Yizhi Jiang</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Hongfei Fan</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Hongming Zhu</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Qin Liu</string-name>
          <email>qin.liug@tongji.edu.cn</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>School of Software Engineering, Tongji University</institution>
          ,
          <addr-line>Shanghai</addr-line>
          ,
          <country country="CN">China</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>FTRLIM is a distributed framework that is designed for large-scale instance matching. The FTRLIM framework leverages the blocking algorithm to generate candidate instance pairs, and applies the follow-the-regularized-leader model to determine whether candidate instance pairs are matched. FTRLIM participated in the SPIMBENCH Track of OAEI 2020, and achieved the fastest matching e ciency both in SANDBOX and MAINBOX, as well as the competitive matching quality.</p>
      </abstract>
    </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>
          The instance-based matching has gradually become a promising topic recently[
          <xref ref-type="bibr" rid="ref1">1</xref>
          ].
Many methods have been proposed to complete the instance matching task.
Several state-of-the-art instance matching methods evolve from ontology matching
methods such as LogMap[
          <xref ref-type="bibr" rid="ref2">2</xref>
          ], AML[
          <xref ref-type="bibr" rid="ref3">3</xref>
          ], RiMOM-IM[
          <xref ref-type="bibr" rid="ref4">4</xref>
          ], and Lily[
          <xref ref-type="bibr" rid="ref5">5</xref>
          ]. As the scale
of the data increases, the e ciency and cost requirements of instance matching
methods become more stringent.
        </p>
        <p>FTRLIM is a distributed instance matching framework that focus more on
the matching e ciency. When matching instances, it rst generates indexes for
instances based on their attributes. Instances with the same index are divided
into the same instance block, and instances from di erent sources under the same
block form the candidate instance pairs. Then FTRLIM gures out the matched
instance pairs leveraging the online-learning model, follow-the-regularized-leader
(FTRL). This is the second time that FTRLIM has participated in the OAEI
evaluation. To participate in the SPIMBENCH Track, FTRLIM is rebuilt using
JAVA with core functionalities as the submitted version. The complete version
of FTRLIM has been developed and deployed on a Spark cluster, which provides
the FTRLIM framework with ability to deal with large-scale data. Compared
with last year's version, this year's FTRLIM has been slightly changed, which
will be introduced later.
1.2</p>
      </sec>
      <sec id="sec-2-2">
        <title>Speci c techniques used</title>
        <p>
          This section introduces the re ned working ow of FTRLIM. FTRLIM consists
of four major components: Blocker, Comparator, Trainer, and Matcher. The
framework accepts input instances in the OWL format, which are stored in
source dataset and target dataset, respectively. FTRLIM nds matched instances
between the two datasets. The overview of the FTRLIM's work ow is presented
in Fig. 1.
Blocker Since the scale of instances that need to be matched is usually very
large, it is very time-consuming and space-consuming to compare all the
instances with each other to nd matched instance pairs. Blocker extracts
features of textual attributes related to instances to generate indexes for them.
The interactions among di erent textual information are taken into
consideration, which allows instances to be ne-grained divided. It also has the ability to
infer indexes for instances whose textural attributes are in-completed or
missing. FTRLIM supports users to generate indexes for instances via more than
one attribute. Instances with the same index are divided into the same instance
block, and instances from di erent sources under the same block will form
candidate instance pairs. Only when a pair of instances is a candidate pair can it be
matched in the following procedures. When there are only two instances from
di erent data sources in the same block, these two instances will form a unique
instance pair[
          <xref ref-type="bibr" rid="ref4">4</xref>
          ], which will be regarded as an matched instance pair directly.
Comparator All candidate pairs will be sent to the comparator to calculate
similarity. The comparator compares two instances from user-speci ed aspects.
The edit distance similarity is calculated for textual instance attributes, while
the Jaccard similarity is calculated for instance relationships. The calculation
results will be arranged in order to form the similarity vector. Formally, let the
list of predicates adopted by Comparator be hp1; p2; : : : ; pni, then the similarity
vector of the two instance is
        </p>
        <p>hs1; s2; : : : ; sni ; si 2 [0; 1]; (i = 1; 2; : : : ; n)
where si is the similarity of the two instances under the i-th predicate.
Trainer FTRLIM treats the instance matching as a regression problem, where
the similarity score between two instances can be regarded as the probability that
the two instances are matched. We innovatively introduce the FTRL model[6] to
solve the problem. FTRL is a widely-used online logistic regression model with
high precision, excellent sparsity, fast training speed and satisfactory streaming
data processing ability. Trainer is designed to train the FTRL model for instance
matching. It rst generates train set for the FTRL model. After the preparation
of train set is completed, the FTRL model will be trained with hyperparameters
in con guration les. Bene ting from the FTRL model's feature, the training
process won't cost a long time. The Trainer component plays a greater role in
the complete version. It can be used to accept the feedback of users and adjust
the parameters of the FTRL model. Users are allowed to choose a batch of
candidate instance pairs and correct the similarity score, or pick up a certain
pair to correct.</p>
        <p>
          Matcher All candidate pairs will obtain their nal similarity scores in this
component. Since FTRLIM produces the similarity scores in the interval [
          <xref ref-type="bibr" rid="ref1">0,1</xref>
          ],
candidate pairs whose scores are greater than 0.5 will be regarded as matched
pairs. The matching score s is calculated as follows:
s =
        </p>
        <p>
          1
1 + e xT w
(1)
where x is the similarity vector, w is the weight of the FTRL model. In this
year's submission, all elements of similarity vectors accepted by the FTRL model
are uni ed from [
          <xref ref-type="bibr" rid="ref1">0, 1</xref>
          ] to [
          <xref ref-type="bibr" rid="ref1">-1, 1</xref>
          ] to satisfy the symmetry of the equation.
Con gurations FTRLIM is easily to be tailored according to user's
requirements. We expect that all matching procedures are under user's control, thus
we allow users to customize their own FTRLIM system using con guration les.
Users are able to set the attributes for index generation, the attributes and
relationships for comparison, the hyperparameters for the FTRL model and many
other detailed parameters to get a better result.
1.3
        </p>
      </sec>
      <sec id="sec-2-3">
        <title>Adaptions made for the evaluation</title>
        <p>To participate in the evaluation, we rebuilt FTRLIM and replaced some manual
operations with automatic strategies.</p>
        <p>The train set for training the FTRL model is automatically generated in the
submitted version, while it needs manual scoring in the completed version. The
train set is composed of instance pairs' similarity vectors as well as their
similarity scores. The Trainer regards all unique pairs as matched pairs. Therefore,
it selects all similarity vectors of unique pairs as positive samples, and assigns
them with similarity score 1.0. The mismatched pairs are built by replacing one
instance of each unique pair randomly. These pairs are assigned with
similarity score 0.0 and treated as negative samples in the train set. In the completed
version, however, FTRLIM does not regard all unique pairs as matched pairs
directly. It will compute the mean value of similarity vectors' elements as the
raw score for each instance pairs. Then it will select a batch of instance pairs
that have raw scores higher than a threshold as positive samples, as well as the
same amount of instance pairs whose raw scores are lower than the threshold
as negative samples. Users will determine the similarity score by themselves to
generate the train set. Besides, we excluded the non-core functionalities of
FTRLIM such as the user-feedback and the load balance mechanism. The ways of
input and output is adapted for the evaluation as well.
1.4</p>
      </sec>
      <sec id="sec-2-4">
        <title>Link to the system and parameters le</title>
        <p>The implementation of FTRLIM and relevant System Adapter for HOBBIT
platform can be found at this FTRLIM-HOBBIT's gitlab page.1
2</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Result</title>
      <p>
        In this section, we present the results obtained by FTRLIM in the OAEI 2020
competition. FTRLIM participated in the SPIMBENCH Track, which aims at
determining whether two OWL instances describe the same Creative Work. The
datasets are generated and transformed using SPIMBENCH[7]. Our competitors
includes LogMap[
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], AML[
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], Lily[
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] and REMinder. The rst three systems have
participated in this track for many years, while REMinder is a new contestants
in this year. The results are published in this OAEI 2020 result page2.
2.1
      </p>
      <sec id="sec-3-1">
        <title>SPIMBENCH</title>
        <p>The SPIMBENCH task is executed in two datasets, the SANDBOX and the
MAINBOX, of di erent size. The SANDBOX has about 380 instances and 10000
triplets, while the MAINBOX has about 1800 instances and 50000 triplets. We
summarized the results of the SPIMBENCH Track in Table 1 and Table 2, where
the best results are indicated in bold.</p>
        <p>Compared with all competitors, FTRLIM achieves the best time performance
on both two datasets. The time cost of our framework is reduced by 25.6% than
the second fastest one, Lily, on SANDBOX, while it is reduced by 42.4% than
Lily on MAINBOX. The results on time performance indicate the e ciency of
FTRLIM, which is more essential for large-scale instance matching. The
FTRLIM also achieves the highest recall on SANDBOX and almost the highest recall
on MAINBOX. The precision of FTRLIM is relatively low on both datasets.
There are two reasons that account for this situation. One reason is that the
automatic strategy we adopted for generating train set is awed. In the generated
train set, there is almost no similarity between the the sample instance pairs with
low score. Although this kind of samples helps the FTRL model learn to
distinguish similar instance pairs from dissimilar instance pairs, it does not help the
model distinguish matched instance pairs from similar instance pairs. Then the
model prefers to predict high similarity scores for similar instance pairs, which
improves the recall but reduces the precision. Another reason is that there may
be problems with the way unique pairs are treated. Regarding the unique pairs
as matched pairs directly will also a ect the precision of the prediction. But the
overall matching quality of FTRLIM is still competitive.</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>General comments</title>
      <sec id="sec-4-1">
        <title>Comments on the result</title>
        <p>FTRLIM has achieved time performance in both datasets of SPIMBENCH. The
Blocker component makes a signi cant contribution to achieving the results.
It helps the framework lter out instance pairs with a high possibility to be
1 https://git.project-hobbit.eu/937522035/ftrlimhobbit
2 http://oaei.ontologymatching.org/2020/results
matched e ectively and e ciently. The Comparator component only needs to
compare instances with the same indexes rather than every instance pairs. The
datasets of SPIMBENCH contain a wealth of textual information, and there are
many attributes that can be used to build indexes or to compare the similarity
among instances. The FTRL model trained by Trainer is able to learn a weight
for attributes or relationships and distinguish instance pairs that points to the
same entity in the real world. Compared with other systems, the precision of
FTRLIM is unsatisfactory, which should be improved in feature works.
3.2</p>
      </sec>
      <sec id="sec-4-2">
        <title>Improvements</title>
        <p>There are still many aspects to be improved in FTRLIM. The submitted version
of FTRLIM generates awed train set for training the FTRL model, and
considers unique pairs as matched instances unconditionally. The automatic strategy
adopted by Trainer and Matcher should be optimized to address the problems.
More comparison methods for various data types should be attached to our
frameworks as well. Although FTRLIM is specially designed to solve the
instance matching problem, it is also expected to produce meaningful results in
other similar tracks in the future.
4</p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>Conclusion</title>
      <p>In this paper, we brie y presented our instance matching framework FTRLIM.
The core functionalities and components of FTRLIM were introduced, and the
evaluation results of FTRLIM were presented and analyzed. FTRLIM achieved
signi cantly better time performance than other systems on both two datasets of
SPIMBENCH, as well as the competitive matching quality. The results indicated
the e ectiveness and high e ciency of our matching strategy, which is important
for matching instances on large-scale datasets.
6. McMahan, H.B., Holt, G., Sculley, D., Young, M., Ebner, D., Grady, J., Nie, L.,
Phillips, T., Davydov, E., Golovin, D., et al.: Ad click prediction: a view from the
trenches. In: Proceedings of the 19th ACM SIGKDD international conference on
Knowledge discovery and data mining. pp. 1222{1230 (2013)
7. Saveta, T., Daskalaki, E., Flouris, G., Fundulaki, I., Herschel, M., Ngomo, A.C.N.:
Spimbench : A scalable , schema-aware instance matching benchmark for the
semantic publishing domain (2014)</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <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>
          <volume>42</volume>
          (
          <issue>2</issue>
          ),
          <volume>949</volume>
          {
          <fpage>971</fpage>
          (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Jimenez-Ruiz</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Grau</surname>
            ,
            <given-names>B.C.</given-names>
          </string-name>
          :
          <article-title>Logmap: Logic-based and scalable ontology matching</article-title>
          .
          <source>In: International Semantic Web Conference</source>
          . pp.
          <volume>273</volume>
          {
          <fpage>288</fpage>
          . Springer (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Faria</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pesquita</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Santos</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cruz</surname>
            ,
            <given-names>I.F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Couto</surname>
            ,
            <given-names>F.M.:</given-names>
          </string-name>
          <article-title>Agreementmakerlight results for oaei 2013</article-title>
          . In: OM. pp.
          <volume>101</volume>
          {
          <issue>108</issue>
          (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Shao</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hu</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Li</surname>
            ,
            <given-names>J.Z.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wang</surname>
            ,
            <given-names>Z.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chung</surname>
            ,
            <given-names>T.L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Xia</surname>
            ,
            <given-names>J.B.</given-names>
          </string-name>
          :
          <article-title>Rimom-im: A novel iterative framework for instance matching</article-title>
          .
          <source>Journal of Computer Science and Technology</source>
          <volume>31</volume>
          ,
          <issue>185</issue>
          {
          <fpage>197</fpage>
          (
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Wu</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pan</surname>
            ,
            <given-names>Z.</given-names>
          </string-name>
          , Zhang,
          <string-name>
            <given-names>C.</given-names>
            ,
            <surname>Wang</surname>
          </string-name>
          ,
          <string-name>
            <surname>P.</surname>
          </string-name>
          :
          <article-title>Lily results for oaei 2019</article-title>
          . In: OM@ ISWC. pp.
          <volume>153</volume>
          {
          <issue>159</issue>
          (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>