<!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>MMIS at GeoCLEF 2008: Experiments in GIR</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Simon Overell</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Adam Rae</string-name>
          <email>a.rae@open.ac.uk</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Stefan Ru¨ger</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>General Terms</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="editor">
          <string-name>Geographic Information Retrieval, Placename Disambiguation, Geographic Indexing, Geographic
Relevance Ranking</string-name>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Department of Computing, Imperial College London</institution>
          ,
          <addr-line>SW7 2AZ</addr-line>
          ,
          <country country="UK">UK</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Knowledge Media Institute</institution>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Measurement</institution>
          ,
          <addr-line>Performance, Experimentation</addr-line>
        </aff>
        <aff id="aff3">
          <label>3</label>
          <institution>The Open University</institution>
          ,
          <addr-line>Milton Keynes, MK7 6AA</addr-line>
          ,
          <country country="UK">UK</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>In this paper we present our Geographic Information Retrieval System, Forostar, and the results of three experiments. We compare two data fusion methods, and show that a simple geographic filter outperforms a penalty based system. We compare context based disambiguation to a default gazetteer and show no significant difference. Finally we compare a unique geographic index to an ambiguous geographic index. The ambiguous index outperformed all other methods and was statistically significantly better than the baseline.</p>
      </abstract>
      <kwd-group>
        <kwd>H</kwd>
        <kwd>3 [Information Storage and Retrieval]</kwd>
        <kwd>H</kwd>
        <kwd>3</kwd>
        <kwd>1 Content Analysis and Indexing</kwd>
        <kwd>H</kwd>
        <kwd>3</kwd>
        <kwd>3 Information Search and Retrieval</kwd>
        <kwd>H</kwd>
        <kwd>3</kwd>
        <kwd>4 Systems and Software</kwd>
        <kwd>H</kwd>
        <kwd>3</kwd>
        <kwd>7 Digital Libraries</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>This paper presents the work from the MultiMedia Information Systems group at GeoCLEF 2008
with our GIR application Forostar. We submitted nine runs performing three experiments.</p>
      <p>Our first experiment compares two data fusion methods looking at how best to combine text
and geographic relevance data. Our text results take the form of a rank returned from a standard
IR system, while our geographic results take the form of a filter – an unranked list of all documents
matching the geographic part of the query. We compare penalising documents not appearing in
the filter with a learned penalisation value to simply applying the filter to the text rank.</p>
      <p>Our second experiment compares context based placename disambiguation to a default gazetteer.
We have a unique geographic index mapping each placename reference in a document to a single
location on the Earth’s surface. This mapping is not a trivial matter for ambiguous locations,
such as “Cambridge” or “London”. We compare three ways of generating this index, the
simplest matches each placename to the most common location with that name. We compare this
to two methods that use other placenames occurring in the document to provide a context to
disambiguate the ambiguous placenames. A model mined from Wikipedia is used as training
data.</p>
      <p>Our final experiment compares our unique index to an ambiguous index, in an ambiguous
index each ambiguous placename is indexed multiple times, once for each possible location. An
ambiguous index will clearly provide significantly greater recall but at a potential cost to precision
(dependent on the accuracy of the unique index).</p>
      <p>In Section 2 we outline our GIR system and the different methods used in our experiments.
Section 3 will reiterate our research questions and describe our submitted runs. Section 4 contains
our results, significance testing and comparisons to the other GeoCLEF submissions. We conclude
with Section 5 containing our observations and planned future work.
2</p>
    </sec>
    <sec id="sec-2">
      <title>System</title>
      <p>
        Forostar is our ad-hoc Geographic Information Retrieval system (Figure 1). At indexing time,
documents are analysed and named entities extracted. Named entities tagged as locations are
then disambiguated using our co-occurrence model extracted from Wikipedia [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]. The free-text
fields are then indexed by Lucene. In the querying stage we query the Geographic and Text indexes
separately combining them in the data-fusion module.
2.1
      </p>
      <sec id="sec-2-1">
        <title>Indexing Stage</title>
        <p>
          Forostar’s Indexer is based on Apache Lucene [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ]. Text fields are pre-processed by a customised
analyser similar to Lucene’s default analyser: Text is split at white space into tokens, the tokens
are then converted to lower case, stop words discarded and stemmed with the “Snowball Stemmer”.
The processed tokens are held in Lucene’s inverted index.
        </p>
        <p>
          The Named Entity Reconiser used to process the text fields is Sheffield University’s General
Architecture for Text Engineering (GATE) [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ]. The bundled Information Extraction Engine,
ANNIE, performs named entity recognition, extracting named entities and tagging them as locations.
Our disambiguation system matches these placenames to unique locations in the Getty Thesaurus
of Geographical Names (TGN) [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ].
        </p>
        <p>
          PediaCrawler, the application that builds our geographic co-occurrence model, is not
discussed in detail in this paper; instead we refer the reader to [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ]. Suffice to say the co-occurrence
model produced acts as training data for our placename disambiguation algorithms described
below. The co-occurrence model used is available by contacting the lead author.
        </p>
        <p>We compare four alternative modules for the Disambiguator described below. All map the
placenames that occur in a document to locations in the TGN and store them in a geographic
Cambridge, UK
Cambridge, MA
Cambridge, NZ
index.</p>
        <p>
          • Most Referred to (MR). The most referred to method matches each each placename to
the most referred to location with that placename in the co-occurrence model. Essentially
we build a default gazetteer providing a many-to-one mapping of placenames to locations.
• Support Vector Machine (SVM). We construct a multi-dimensional vector space, which
is partitioned with an SVM [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ]: ambiguous placenames are the classification objects, possible
locations the classification classes, co-occurring locations are the features, and the features
have tf •idf weights. We train a separately classifier for each possible location–placename
mapping and classify as the location whose classifier outputs the greatest decision value.
        </p>
        <p>The co-occurrence model forms our training data.
• Neighbourhoods (Neigh). For each possible location of an ambiguous placename we
build a collection of trigger words. Trigger words are other placenames, which if they appear
in the same document as the ambiguous placename identify the location. If none of the
trigger words appear the placename is classified using the MR method.</p>
        <p>
          Trigger words are found based on a relatedness score. [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ] describe the relatedness score as
the ratio of co-occurrences between words divided by the disjunction of occurrences. This
can be defined as:
r(x, y) =
        </p>
        <p>fxy
fx + fy − fxy
where fx denotes the total number of times word x appears. The top 5 trigger words for
three different locations for the placename ‘Cambridge’ are shown in Table 1.
• No Disambiguation (NoDis). Although not strictly speaking a method of
disambiguation, the NoDis method provides an alternative to a disambiguation algorithm. NoDis builds
an ambiguous index, indexing each ambiguous placename once for each possible location. For
example the placename ‘Cambridge’ would be indexed 3 times: Cambridge, UK, Cambridge
MA, and Cambridge NZ.
2.2</p>
      </sec>
      <sec id="sec-2-2">
        <title>Querying Stage</title>
        <p>The text and geographic indexes are queried separately by two different query engines. Placenames
are manually extracted from queries and passed to the Geographic Query Engine1. Queries are
passed to the text query engine with no pre-processing.</p>
        <p>We use the standard Lucene Text Query Engine. This performs a comparison between the
documents and the query in a tf •idf weighted vector space. The cosine distance is taken between
the query vector and the document vectors. The text rank is produced in standard TREC format.</p>
        <p>We also use Lucene to store the Geographic Index. A unique string is formed for each
location, this is the TGN id of this location, preceded with the TGN id of all the parent locations,
separated with slashes. Thus the unique string for the location “London, UK” is the TGN id
for London (7011781), preceded by its parent, Greater London (7008136), preceded by its parent,
Britain (7002445). . . until the root location, the World (1000000) is reached. Giving the unique
string for London as 1000000\1000003\7008591\7002445\7008136\7011781.</p>
        <p>1The only reason this was not handled by the Named Entity Reconiser was time constraints in the
implementation.</p>
        <sec id="sec-2-2-1">
          <title>Disambig. Method MR SVN Neigh.</title>
          <p>NoDis.</p>
        </sec>
        <sec id="sec-2-2-2">
          <title>Penalisation Values</title>
          <p>2.0
3.0
8.0
3.0
The intermediate rank is sorted by r0 to give the final returned rank.</p>
          <p>The penalisation value p is found using a brute force search using the 75 queries and relevance
judgements from GeoCLEF 2005 – 2007 as training data. The search finds the value of p
that maximises mean average precision (MAP). The p values found for each disambiguation
method are shown in Table 2.
• Filtering. The filtering method reorders the text rank in a more aggressive way than the
penalisation method. All the results of the text rank that are also contained in the geographic
filter are returned first, followed by the text results that are not in the geographic filter. This
is equivalent to the penalisation method with a p value of ∞.</p>
          <p>An example of these two methods are shown in Figure 2. It shows a hypothetical text rank
containing two entries also in the geographic filter. The penalisation method calculates r0, shown
in brackets, to re-order the results, while the filter method simply promotes all the documents also
in the geographic filter to the top of the rank.
3</p>
        </sec>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Experiments</title>
      <p>Our experiments are all monolingual. We use the 25 English Language GeoCLEF queries and the
English Language corpus consisting of ≈ 170, 000 documents from the Glasgow Herald and Los
Angeles Times. GeoCLEF topics contain title, description and narrative fields. We only use the
title field as this field bears most similarity to the types of geographic query submitted to search
engines.</p>
      <p>As explained in Section 1 we are performing three experiments at this year’s GeoCLEF. This
involved us submitting nine runs: a simple text baseline (the text rank before data fusion) and
2This method is chosen due to the minimal context contained in queries.
both of the combination methods combined with each of the four disambiguation methods. Our
experimental questions are outlined below in brief:
• Can the more sophisticated Penalisation data fusion method outperform the more aggressive</p>
      <p>Filtering method?
• Can the more sophisticated context based disambiguation methods Neigh and SVM
outperform the default gazetteer MR method?
• Are the unique geographic index methods accurate enough to outperform the NoDis method?
4</p>
    </sec>
    <sec id="sec-4">
      <title>Results</title>
      <p>The results of our nine runs are displayed in Table 3. Mean Average Precision (MAP) is the
metric primarily used in GeoCLEF, however Geometric Average Precision (Geo AP) is also shown
to give an indication of how consistent the methods are. Notice that combining the geographic
information using the penalisation filter actually gives us worse results than the text baseline. Our
assumption here is that the penalisation training on the past GeoCLEF data is over fitting. On
the other hand, the filter method outperforms the baseline in every case showing it to be more
robust.</p>
      <p>There is minimal difference between which disambiguation method is used regardless of the
fusion method.</p>
      <p>
        We performed pairwise statistical significance testing of each method with the baseline using
the Wilcoxon signed rank test rejecting the null hypothesis only when p &lt; 5% [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. We found that
all the Penalisation results were statistically significantly worse than the baseline, and only the
NoDis-Filter method was statistically significantly better. We also performed pairwise significance
      </p>
      <sec id="sec-4-1">
        <title>Disambig. Fusion</title>
        <p>Text Baseline
MR Penalis.</p>
        <p>SVN Penalis.</p>
        <p>Neigh. Penalis.</p>
        <p>NoDis. Penalis.</p>
        <p>MR Filter
SVN Filter
Neigh. Filter
NoDis. Filter
For comparison with the rest of the participants at GeoCLEF 2008, Table 4 shows the best, worst
and quartile ranges of all the submitted runs. Our best result, NoDis-Filter, occurs in the top
quartile. The other filtered results and the baseline occur between the Median and Q3. The
Penalisation results occur in the lower quartile.
5</p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>Conclusions</title>
      <p>
        In past years at GeoCLEF many submitted methods augmented with Geographic Information
(including our past attempts) have not provided a statistically significant improvement over a
baseline [
        <xref ref-type="bibr" rid="ref6 ref7">7, 6</xref>
        ]. We were pleased to buck this trend this year with our NoDis-Filter method, which
re-orders the text result using an ambiguous geographic filter. The NoDis-Filter method was
statistically significantly better than our text only baseline, it also came in the top quartile of
methods submitted.
      </p>
      <p>In response to our research questions it is still unclear whether an ambiguous or unique text
index provides the best results, also whether context based disambiguation can improve over
noncontext based methods. We have, however, shown that using a penalisation value to combine text
and geographic data is highly sensitive to over fitting and a simple filter much more robust. In
fact using a brute force search to optimise the penalisation value resulted in an MAP on the test
data statistically significantly worse than the baseline or filter methods.
5.1</p>
      <sec id="sec-5-1">
        <title>Future work</title>
        <p>In future work we would like to expand our context based disambiguation algorithms to take into
account not only the content of the documents but also the associated meta-data, i.e. where the
documents were published. We believe treating placenames in the Los Angeles Times differently
from the Glasgow Herald could produce further improvements in disambiguation and retrieval
performance.</p>
        <p>Also we would like to further develop the Penalisation data fusion method as it is potentially
more powerful than the Filter method. Alternative methods of training the system will need to
be explored, specifically how to avoid over fitting.</p>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>H</given-names>
            <surname>Cunningham</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D</given-names>
            <surname>Maynard</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V</given-names>
            <surname>Tablan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C</given-names>
            <surname>Ursu</surname>
          </string-name>
          , and
          <string-name>
            <given-names>K</given-names>
            <surname>Bontcheva</surname>
          </string-name>
          .
          <article-title>Developing language processing components with GATE</article-title>
          .
          <source>Technical report</source>
          , University of Sheffield,
          <year>2001</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>J A</given-names>
            <surname>Guthrie</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L</given-names>
            <surname>Guthrie</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y</given-names>
            <surname>Wilks</surname>
          </string-name>
          , and
          <string-name>
            <given-names>H</given-names>
            <surname>Aidinejad</surname>
          </string-name>
          .
          <article-title>Subject-dependent co-occurrence and word sense disambiguation</article-title>
          .
          <source>In Meeting of the Association for Computational Linguistics</source>
          , pages
          <fpage>146</fpage>
          -
          <lpage>152</lpage>
          ,
          <year>1991</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>P</given-names>
            <surname>Harping.</surname>
          </string-name>
          <article-title>User's Guide to the TGN Data Releases</article-title>
          .
          <source>The Getty Vocabulary Program, 2.0 edition</source>
          ,
          <year>2000</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>D</given-names>
            <surname>Hull</surname>
          </string-name>
          .
          <article-title>Using statistical testing in the evaluation of retrieval experiments</article-title>
          .
          <source>In SIGIR conference on Research and development in information retrieval</source>
          , pages
          <fpage>329</fpage>
          -
          <lpage>338</lpage>
          ,
          <year>1993</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>T</given-names>
            <surname>Joachims</surname>
          </string-name>
          .
          <article-title>Advances in Kernel Methods - Support Vector Learning, chapter Making largeScale SVM Learning Practical</article-title>
          . MIT-Press,
          <year>1999</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>S</given-names>
            <surname>Overell</surname>
          </string-name>
          , J Magalh˜
          <article-title>aes, and S Ru¨ger. Forostar: A system for GIR</article-title>
          .
          <source>In Lecture Notes from the Cross Language Evaluation Forum</source>
          <year>2006</year>
          ,
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>S</given-names>
            <surname>Overell</surname>
          </string-name>
          , J Magalh˜
          <article-title>aes, and S Ru¨ger. GIR experiments with Forostar at geoCLEF 2007</article-title>
          .
          <article-title>In A Nardi and</article-title>
          C Peters, editors,
          <source>CLEF 2007 Workshop</source>
          , Working notes,
          <year>September 2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>S</given-names>
            <surname>Overell</surname>
          </string-name>
          and
          <string-name>
            <given-names>S</given-names>
            <surname>Ru</surname>
          </string-name>
          <article-title>¨ger. Geographic co-occurrence as a tool for GIR</article-title>
          .
          <source>In CIKM Workshop on Geographic Information Retrieval</source>
          ,
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>Apache</given-names>
            <surname>Lucene</surname>
          </string-name>
          <article-title>Project</article-title>
          . http://lucene.apache.org/java/docs/.
          <source>Accessed 1 August</source>
          <year>2007</year>
          ,
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>