<!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>Massimiliano Ruocco</string-name>
          <email>ruocco@idi.ntnu.no</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Heri Ramampiaro</string-name>
          <email>heri@idi.ntnu.no</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Data and Information Management Group, Department of Computer and Information Science Norwegian University of Science and Technology Sem Saelands vei</institution>
          <addr-line>7-9 NO-7491 Trondheim</addr-line>
          ,
          <country country="NO">Norway</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2011</year>
      </pub-date>
      <fpage>1</fpage>
      <lpage>2</lpage>
      <abstract>
        <p>In this paper we present the system used to solve the challenges of the Social Event Detection (SED) task at MediaEval 2011 challenge.</p>
      </abstract>
      <kwd-group>
        <kwd>Figure 1</kwd>
        <kwd>System Overview</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>2.1 Query Expansion</title>
      <p>
        In a social event retrieval context, a query can be
splitted and mapped in three di erent parts according to the
general parameters characterizing an event: (
        <xref ref-type="bibr" rid="ref1">1</xref>
        ) what, i.e.,
which kind of event we are looking for, (
        <xref ref-type="bibr" rid="ref2">2</xref>
        ) where, i.e., the
venue, name of place, city or region where the event that we
are looking for takes place, (
        <xref ref-type="bibr" rid="ref3">3</xref>
        ) when, i.e., the time, interval
when the event happens. In both challenges the where part
of the query is expanded in the rst block. For Challenge
1 the where part is created with all the stadium names in
Rome and Barcelona, in all languages while for Challenge
2, it was created with the names of the two venues
specied in the challenge. For both challenges, the geographical
location (latitude and longitude) are also extracted. In
order to retrieve these information, a set of SparQL queries
are submitted to DBpedia1 database by using the Jena2
interface for java. To be more speci c, for Challenge 1,
names in di erent languages and geographical information
are extracted by selecting from the DBpedia category
Football_venues_in_Italy the occurrences based on the city
of Rome and Barcelona. For Challenge 2, the geographical
location and names related to the requested venues were
extracted using the LastFM API 3 and used as query into the
LastFM database. The output of this block is a set of queries
Q = fQ1; :::; QN g, where each subset Qi = fqi1; :::; qiM g
refers to all queries related to a venue and each qij = fT; gg
is composed of two di erent parts: a textual part with
different names of the venues, and a spatial part with a pair of
real numbers representing the latitude and longitude of the
venues.
      </p>
    </sec>
    <sec id="sec-2">
      <title>2.2 Search</title>
      <p>The queries are submitted to the search engine over the
dataset. In our work, we use Solr 4 search engine to index
the dataset and perform the search. The search is done as a
1http://dbpedia.org/
2http://jena.sourceforge.net/
3http://www.last.fm/api
4http://lucene.apache.org/solr/
mix of spatial (by using latitude and longitude values) and
textual search. The data are indexed based on the textual
metadata, including Title, Description and Tags. The
search is then performed over all the three di erent
metadata. In particular for Challenge 2 the queries are boolean
queries with all the terms in AND, while in the Challenge
1 these conditions are more relaxed and the terms of each
query are composed with the boolean operator OR. The
reason for this is that in this challenge, a categorizer is provided
as next step to lter out non-relevant retrieved occurrences.</p>
    </sec>
    <sec id="sec-3">
      <title>2.3 Categorization</title>
      <p>The input of this block is a list of pictures with their
metadata. This module is used only for Challenge 1 to extract
pictures related to a soccer event. The categorization is
performed over the three textual metadata for each picture, i.e.,
Title, Description and Tags. The di erent runs will
exploit the descriptivity of each kind of metadata in the
categorization process (see Section 3). To categorize the pictures
the SemanticHacker API 5 over the di erent textual
metadata was used. The categories produced are based on the
Open Directory Project 6. The pictures are ltered by only
keeping those categorized with a category that has radix
Sports/Soccer.</p>
    </sec>
    <sec id="sec-4">
      <title>2.4 Clustering and Merging</title>
      <p>The previous block returns a set of ltered pictures
(Challenge 1 ) related to soccer events or pictures taken in the
venues speci ed in the search step (Challenge 2 ) and grouped
based on the venues. In this step the temporal information
will be used to group the temporal related pictures. In that
way the resulting clusters are nally grouped according to
their temporal and locational information. To perform the
clustering process the Quality Thresold Clustering (QT)
algorithm is used [1]. This algorithm does not require to
specify in advance the number of clusters and even it is
computationally expensive, it is used only on retrieved documents.
The resulting clusters may be semantically related and
belonging to the same event. To merge semantically similar
clusters a graph is built, where the nodes of the graph are
the clusters, and two nodes are connected if they share at
least a tag representing a named entity of an event or of an
artist. To extract the named entities, we use the tags and
submit them as queries to LastFM for the artist names and
DBPedia for event names. Clusters are merged by nding
the connected component as in [3].</p>
    </sec>
    <sec id="sec-5">
      <title>2.5 Refinement</title>
      <p>
        The resulting clusters may be incomplete, i.e. the dataset
may contain other pictures related to the event clusters
extracted but not retrieved in the search step. The re
nement module is used here to query the dataset by using the
(
        <xref ref-type="bibr" rid="ref1">1</xref>
        ) top-k frequent tags and (
        <xref ref-type="bibr" rid="ref2">2</xref>
        ) top-k frequent entity names
(artists and events). The results of the re nement step can
still be ltered to avoid retrieving non-relevant occurrences.
      </p>
    </sec>
    <sec id="sec-6">
      <title>3. EXPERIMENTS AND RESULTS</title>
      <p>In this section, we present the di erent runs and their
evaluation over di erent metrics. Table 1 provides a summary
of our results.</p>
    </sec>
    <sec id="sec-7">
      <title>3.1 Challenge 1</title>
      <p>Two di erent runs were performed in the rst challenge.
In the rst run (Run 1 ) all the work ow of the system is
performed excluding the re nement step and semantic merge
between clusters. For Run 1 the categorization is performed
by using only Tag metadata, while for the second run (Run
2 ), we also include the Title and Description metadata.
From the results obtained (see Table 1) we can observe that
including other metadata than tags resulted in a decrease of
precision, probably due to the lack of descriptiveness of the
other metadata.</p>
    </sec>
    <sec id="sec-8">
      <title>3.2 Challenge 2</title>
      <p>For this challenge, three di erent runs were performed. The
Run 1 (the baseline run) executed the algorithm without
including the semantic merge and re nement steps. In both
Run 2 and Run 3 the semantic merge and re nement steps
were performed. Semantic merge was done by considering
each cluster represented by the named entity representing
events or artists. Moreover in Run 2, re nement is
performed by querying the top-100 tags and the temporal range
in which each cluster is closed. In Run 3, we used the entity
names representing artists or events extracted from the set
of tags of each cluster.</p>
      <p>Precision</p>
      <p>Recall
F-Measure</p>
      <p>NMI</p>
    </sec>
    <sec id="sec-9">
      <title>4. CONCLUSIONS</title>
      <p>We have presented a system to extract events for the given
two challenges. As described in this paper, the best result in
terms of precision was obtained in the rst challenge by
using only the tags for the categorization step, while the other
evaluation measure were better when using all the textual
metadata. In the second challenge the best result was
obtained using the complete work ow of the algorithm, i.e.
using re nement step, in particular using the entity names
in the re nement query for each cluster. Our future
experiments, especially for the rst challenge, will include the use
of the re nement step and semantic merge over the totality
of the results (instead of applying it over groups of results
coming from the query).</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>L. J.</given-names>
            <surname>Heyer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Kruglyak</surname>
          </string-name>
          , and
          <string-name>
            <given-names>S.</given-names>
            <surname>Yooseph</surname>
          </string-name>
          .
          <source>Exploring Expression Data: Identi cation and Analysis of Coexpressed Genes. Genome Research</source>
          ,
          <volume>9</volume>
          (
          <issue>11</issue>
          ):
          <volume>1106</volume>
          {
          <fpage>1115</fpage>
          ,
          <string-name>
            <surname>Nov</surname>
          </string-name>
          .
          <year>1999</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>S.</given-names>
            <surname>Papadopoulos</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Troncy</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Mezaris</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Huet</surname>
          </string-name>
          ,
          <string-name>
            <given-names>and I.</given-names>
            <surname>Kompatsiaris</surname>
          </string-name>
          . Social Event Detection at MediaEval 2011:
          <article-title>Challenges, Dataset and Evaluation</article-title>
          . In MediaEval 2011 Workshop, Pisa, Italy, September 1-2
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>M.</given-names>
            <surname>Ruocco</surname>
          </string-name>
          and
          <string-name>
            <given-names>H.</given-names>
            <surname>Ramampiaro</surname>
          </string-name>
          .
          <article-title>Event clusters detection on ickr images using a su x-tree structure</article-title>
          . Multimedia, International Symposium on,
          <volume>0</volume>
          :
          <fpage>41</fpage>
          {
          <fpage>48</fpage>
          ,
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>