<!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>A Replication Study: Understanding What Drives the Performance in WikiMatch</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Lu Zhou</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Michelle Cheatham</string-name>
          <email>michelle.cheathamg@wright.edu</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>DaSe Lab, Wright State University</institution>
          ,
          <addr-line>Dayton OH 45435</addr-line>
          ,
          <country country="US">USA</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>We replicate and demonstrate that the performance of the WikiMatch automated ontology alignment system may be driven not by the particular information from Wikipedia directly used by the system, but rather by string similarity and Wikipedia's manually curated synonym sets, as encoded in the site's query resolution and page redirection system. In order to gain a detailed understanding of how Wikipedia contributes to WikiMatch, we replicate results reported for WikiMatch and analyze the results to evaluate our hypothesis.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        Introduction
The idea behind WikiMatch is to use Wikipedia's general search functionality
(through the MediaWiki API1) to retrieve a list of related article titles for each
of the entities in the two ontologies to be aligned. After retrieving the list of
titles, the similarity of each pair of entities is computed by the Jaccard index2
on these titles. If the similarity exceeds a threshold, WikiMatch considers the
entities equivalent. We began our WikiMatch replication e ort by downloading
the source code from the link speci ed in [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. We were able to compile and run
the code with minimal e ort, and our results were very similar to those in the
[
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. Then we used two di erent datasets: the conference track and anatomy track
from the OAEI3 to explore the factors driving the performance of the system.
1 https://www.mediawiki.org/wiki/API:Search
2 https://en.wikipedia.org/wiki/Jaccard_index
3 http://oaei.ontologymatching.org/
      </p>
      <p>Precision Recall F-measure TP FP FN
0.74 0.49 0.58 150 52 155
0.74 0.49 0.58 150 52 155
0.70 0.50 0.58 152 64 153
0.99 0.62 0.77 937 11 579
0.99 0.62 0.77 947 11 569
0.96 0.64 0.77 966 43 550</p>
      <p>Acknowledgments This work was supported by the US Geological Survey
agreement G16AC00120 \Demonstration of Semantic Web Technologies as Applied
to Surface Water Feature Classi cation."</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Hertling</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Paulheim</surname>
          </string-name>
          , H.:
          <article-title>Wikimatch: using wikipedia for ontology matching</article-title>
          .
          <source>In: Proceedings of the 7th International Conference on Ontology Matching-Volume</source>
          <volume>946</volume>
          . pp.
          <volume>37</volume>
          {
          <fpage>48</fpage>
          .
          <string-name>
            <surname>CEUR-WS. org</surname>
          </string-name>
          (
          <year>2012</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>