<!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>The University of Amsterdam at WebCLEF 2007: Using Centrality to Rank Web Snippets</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Valentin Jijkoun</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Maarten de Rijke</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>ISLA, University of Amsterdam</institution>
        </aff>
      </contrib-group>
      <abstract>
        <p>We describe our participation in the WebCLEF 2007 task, targeted at snippet retrieval from web data. Our system ranks snippets based on a simple similarity-based centrality, inspired by the web page ranking algorithms. We experimented with retrieval units (sentences and paragraphs) and with the similarity functions used for centrality computations (word overlap and cosine similarity). We found that using paragraphs with the cosine similarity function shows the best performance with precision around 20% and recall around 25% according to human assessments of the first 7,000 bytes of responses for individual topics.</p>
      </abstract>
      <kwd-group>
        <kwd>• topic title (e</kwd>
        <kwd>g</kwd>
        <kwd />
        <kwd>Big Bang Theory )</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>The WebCLEF 2007 task1 differed substantially from the previous editions (2005–2006 of
WebCLEF). Rather than retriving a ranked list of web documents relevant to a topic, in the 2007
setup, systems were asked to return a ranked list of snippets (character spans) extracted from
the top 1,000 web documents identified using the Google web search engine. The definition of
the retrieval unit (snippet) was left up to a system, and thus the task is targeting information
retrieval rather than document retrieval.</p>
      <p>The remainder of this paper is organized as follows. We describe the WebCLEF 2007 task and
topics in Section 2, present the architecture of our system in Section 3, describe our three runs,
evaluation measures and evaluation results in Section 4, and conclude in Section 5.
The task of a system is to return a ranked list of text spans from the provided web pages that,
together, would satisfy the user’s information need.</p>
      <p>Task organizers provided two development topics and 30 test topics.
3</p>
    </sec>
    <sec id="sec-2">
      <title>System Architecture</title>
      <p>For each topic, our system used only text versions of the web documents. One the one hand, the
decision not to use the original versions of the documens (HTML, PDF, Postscript, etc.) led to
some noise in the output of the system. In the text versions, the text encoding was often broken,
which was especially problematic for non-English documents (the task included Spanish and Dutch
topics and pages). Moreover, in cases where an original document was a double-column PDF, in
the corresponding text version, the lines of the columns were often intervened, making the text
version hardly readable for humans. For some of the original documents (e.g., for Word files) text
versions were missing, and therefore our system did not use these documents at all. On the other
hand, using only text version simplified the data processing considerably:
• no sophisticated content extraction had to be developed, and
• the text versions often preserved some text layout of the original pages (e.g., paragraph
starts), which we used to detect suitable snippet boundaries.</p>
      <p>Given a topic, our system first identifies candidate snippets in the source documents by simply
splitting the text of the documents into sentences (using punctuation marks as separators) or into
paragraphs (using empty lines as separators). The same snippet extraction method is applied to
the text of the “known” pages for the topic, resulting in a list of known snippets. We ignored
candidate and known snippets shorter that 30 bytes.
3.1</p>
      <sec id="sec-2-1">
        <title>Ranking snippets</title>
        <p>
          We rank the candidate snippets based on similiarity-based centrality, which is a simplified version
of the graph-based snippet ranking of [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ], inspired by the methods for computing authority of the
Web pages, such as PageRank and HITS [
          <xref ref-type="bibr" rid="ref4">4</xref>
          ]. For each candidate snippet we compute a centrality
score by summing similarities of the snippet with all other candidate snippets. Then, to avoid
assiging high scores to snippets containing information that is already known to the user, we
subtract from the resulting centrality score similarities of the candidate snippet with all known
snippets. As a final step, we remove from consideration candidate snippets whose similarity to one
of the known snippets is higher than a threshold. The pseudocode for this calculation is shown
below:
let c1 . . . cn be candidate snippets
let k1 . . . km be known snippets
for each candidate snippet c
let score(c) = 0
for each candidate snippet c0
        </p>
        <p>let score(c) = score(c) + sim(c, c0)
for each known snippet k</p>
        <p>let score(c) = score(c) − sim(c, k)
for each known snippet k
if sim(c, k) &gt; simmax</p>
        <p>let score(c) = 0
Finally, the candidate snippets are ranked according to score(·) and top snippets are returned so
that the total size of the response is not larger that 10,000 bytes.
3.2</p>
      </sec>
      <sec id="sec-2-2">
        <title>Similarity between snippets</title>
        <p>
          A key component of our snippet ranking method is the snippet similarity function sim(x, y).
Similarly to [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ], we conducted experiments with two versions of the similarity function: one based on
word overlap and one based on the cosine similarity in the vector space retrieval model.
Specifically, for two text snippets, word overlap similarity is defined using the standard Jaccard coefficient
on snippets considered as sets of terms:
where x0 and y0 are sets of non-stopwords of snippets x and y respectively.
        </p>
        <p>The vector space similarity between two snippets is defined as the cosine of the angle between
the vector representations of the snippets computed using the standard TF.IDF weighting scheme:
simwo(x, y) = |x0 ∩ y0| ,
|x0 ∪ y0|
−→x · −→y
simvs(x, y) = √−→x · −→x √−→y · −→y .</p>
        <p>Here, −→a · −→b denotes the scalar product of vectors −→a and −→b.</p>
        <p>Components of the vectors correspond to distinct non-stopword terms occuring in the set of
candidate snippets. For a term t, the value of the component −→a is defined according to the TF.IDF
weighting scheme:
−→a (t) = TF (a, t) · log</p>
        <p>n
|{ci : t ∈ ci}|
.</p>
        <p>Here, TF (a, t) is the frequency of term t in snippet a and c1, . . . , cn are all candidate snippets.</p>
        <p>Both versions of the similarity function produce values between 0 and 1. The similarity
threshold simmax for detecting near-duplicates is selected based on manual assessment of duplicates
among candidate snippets for the development topics.
4</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Submitted Runs and Evaluation Results</title>
      <p>Our goal was to experiment with the units of snippet retrieval and with similarity functions. We
submitted three runs:
• UvA sent wo – snippets defined as sentences, word overlap used for ranking;
• UvA par wo – snippets defined as paragraphs, word overlap for ranking;
• UvA par vs – paragraphs, vector space similarity.</p>
      <p>The evaluation measures used for the task were character-based precision and recall, based on
human assessments of the first 7,000 bytes of system’s response. Precision is defined as the length
of the character spans in the response identified by humans as relevant, divided by the total of
the response (limited to 7,000 characters). Recall is defined as the length of spans in the reponse
identified as relevant, divided by the total length of all distinct spans identified as relevant for the
responses submitted by all systems.</p>
      <p>The evaluation results for the three runs are shown below:</p>
      <p>Run
UvA sent wo
UvA par wo
UvA par vs</p>
      <sec id="sec-3-1">
        <title>Precision</title>
        <p>0.0893
0.1959
0.2018</p>
      </sec>
      <sec id="sec-3-2">
        <title>Recall</title>
        <p>0.1133
0.2486
0.2561
The results indicate that paragraphs provide better retrieval units and using a more sophisticated
similarity function based on the vector space model has a slight positive effect on the performance.
Unfortunately, we did not have enough time to analyse performance of the versions of the
system per topic or to check whether the improvement with the vector space similarity function is
significant.</p>
        <p>Overall, we believe that the paragraph-based runs may serve as a reasonable baseline for the
WebCLEF task: around 1/5 of the returned character content is considered relevant by human
assessors. At the same time, such performance is probably not sufficient for a real-life information
retrieval system.
5</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>Conclusions</title>
      <p>We have described our participation in the WebCLEF 2007 snippet retrieval task. In our
submission we experimented with retrieval units (sentences vs. paragraphs) and with similarity functions
used for semantic centrality computations (word overlap vs. cosine similarity). We found what
using paragraphs with the cosine similarity function shows the best performance with precision
around 20% and recall around 25% according to human assessments of first 7,000 bytes of per-topic
responses.</p>
      <p>
        Detailed analysis of the performance of the runs is part of our immediate agenda for future
work. Another interesting direction for further study is the similarity model suitable for short
snippets. The vector space model that we use in this paper is not necessarily the best option.
However, it has been shown (see, e.g., [
        <xref ref-type="bibr" rid="ref1 ref2">1, 2</xref>
        ]) that more sophisticated models do not necessarily
lead to improvements when working with short text fragments.
      </p>
    </sec>
    <sec id="sec-5">
      <title>Acknowledgements</title>
      <p>The research presented in this paper was supported by NWO under project numbers 017.001.190,
220.80.001, 264.70.050, 354.20.005, 600.065.120, 612.13.001, 612.000.106, 612.066.302, 612.069.006,
640.001.501, and 640.002.501. We are grateful to all participants and assessors of the WebCLEF
2007 task.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>J.</given-names>
            <surname>Allan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Wade</surname>
          </string-name>
          ,
          <article-title>and</article-title>
          <string-name>
            <given-names>A.</given-names>
            <surname>Bolivar</surname>
          </string-name>
          .
          <article-title>Retrieval and novelty detection at the sentence level</article-title>
          .
          <source>In SIGIR '03</source>
          , pages
          <fpage>314</fpage>
          -
          <lpage>321</lpage>
          ,
          <year>2003</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>Sisay</given-names>
            <surname>Fissaha</surname>
          </string-name>
          <string-name>
            <surname>Adafre</surname>
          </string-name>
          , Valentin Jijkouni, and Maarten de Rijke.
          <article-title>Fact discovery in Wikipedia</article-title>
          .
          <source>In IEEE/WIC/ACM International Conference on Web Intelligence</source>
          ,
          <year>2007</year>
          ,
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>Valentin</given-names>
            <surname>Jijkoun</surname>
          </string-name>
          and Maarten de Rijke.
          <article-title>Recognizing textual entailment: Is lexical similarity enough? In I. Dagan</article-title>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Dalche</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. Quinonero</given-names>
            <surname>Candela</surname>
          </string-name>
          , and B. Magnini, editors,
          <source>Evaluating Predictive Uncertainty, Textual Entailment and Object Recognition Systems</source>
          , volume
          <volume>3944</volume>
          <source>of LNAI</source>
          , pages
          <fpage>449</fpage>
          -
          <lpage>460</lpage>
          . Springer,
          <year>2006</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>Bing</given-names>
            <surname>Liu</surname>
          </string-name>
          .
          <source>Web Data Mining. Exploring Hyperlinks, Contents and Usage Data</source>
          . Springer,
          <year>2006</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>