<!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>WikipEvent: Temporal Event Data for the Semantic Web</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Ujwal Gadiraju</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Kaweh Djafari Naini</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Andrea Ceroni</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Mihai Georgescu</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Dang Duc Pham</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Stefan Dietze</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Marco Fisichella</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>L3S Research Center, Leibniz Universitat Hannover</institution>
          ,
          <country country="DE">Germany</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>In this demo we present WikipEvent, an exploratory system that captures and visualises continuously evolving complex event structures, along with the involved entities. The framework facilitates entitycentric and event-centric search, presented via a user-friendly interface and supported by temporal snippets from corresponding Wikipedia page versions. The events detected and extracted using di erent mechanisms are exposed as freely available Linked Data for further reuse.</p>
      </abstract>
      <kwd-group>
        <kwd>Events</kwd>
        <kwd>Temporal Evolution</kwd>
        <kwd>Wikipedia</kwd>
        <kwd>RDF</kwd>
        <kwd>Interface</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>
        Exploratory search systems help users to search, navigate, and discover new facts
and relationships. We detect and extract events from di erent sources and merge
these events into a unique event repository. Each event is described primarily in
terms of (i) a list of entities (Wikipedia pages) participating in the event, (ii) a
textual description of the event, (iii) start and end dates of the event, and (iv)
the extraction method used to obtain the event. We further classify entities as
people, organizations, artifacts, and locations by exploiting the class hierarchy
de ned in YAGO2 [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], since di erent entity categories play di erent roles while
participating in an event.
      </p>
      <p>
        In this demo, we showcase two popular usecase scenarios. First, we show
that WikipEvent can be used in order to explore the events in which particular
entities have been involved. Secondly, we show the suitability of WikipEvent to
explore the evolution of entities based on the events these are involved in. Both
these scenarios can be additionally surveyed based on the temporal dimension.
In addition to the events that are presented using a timeline1, we adopt a
versioning approach introduced previously[
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] in order to display signi cant versions
of wikipages corresponding to the entities involved in the event.
      </p>
      <p>
        WikipEvent facilitates the understanding of events and their related
entities on a temporal basis. Instead of exploration of isolated knowledge bases,
WikipEvent takes advantage of the complimentary nature of sources
contributing to the underlying event repository.
1 Interface: http://wikipeventdemo.l3s.uni-hannover.de/WikiEventEntity/
We extract events from three sources; Wikipedia Current Events portal[
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], Yago[
        <xref ref-type="bibr" rid="ref2">2</xref>
        ],
and an event detection method called Co-References [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. Firstly, the WikiTimes
project2 provides an API for 50,000 events between 2001-2013, acquired from
the Wikipedia Current Events portal. The second event source is the YAGO2
ontology including entities which describe events, e.g. 2011 Australian Open as
well as facts connecting entities, e.g. &lt; BobDylan &gt; wasBornIn &lt; Duluth &gt;.
The Co-References method introduced in [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] extracts Wikipedia pages (entities)
related to an event by using the Wikipedia edit history. The edits corresponding
to a Wikipedia page (entity) are analysed for indications of the occurrence of an
event involving that entity.
      </p>
      <p>The resulting repository contains more than 2:6 million events, extracted from
the di erent sources as shown in Table 1. The contribution from the sources
is skewed due to two reasons. Firstly, they cover very di erent time periods:
YAGO2 contains events and temporal facts spanning over thousands of years,
Current Events captures events since 2001 only, and, for performance reasons,
the Co-References method has been restricted to edits in 2011. In addition,
Co-References exclusively analyses entities of type politician, while YAGO2 and
Current Events contain almost all the Wikipedia pages. To facilitate
comparisons across entities occurring in all three sources, in the rest of this section we
will consider only those events that occurred in 2011 and involved politicians.</p>
      <p>Source Total Politicians Politicians 2011</p>
      <p>All 2,629,740 50,168 1,401</p>
      <p>YAGO2 2,578,547 42,399 360
Current Events 50,951 7,527 799</p>
      <p>Co-Reference 242 242 242
Table 1: Number of events within the event repository, split by di erent sources.</p>
      <p>Co-References is able to detect events with di erent duration and granularity
(from a wrestling match to the Egypt Revolution). YAGO2 mostly contains
high-level and well-known events represented through temporal facts regarding
entities, often lacking textual descriptions. Current Events portal contains daily
events which have a self explanatory textual description and are reliable, thanks
to the high level of control within Wikipedia. The complimentary nature of
the di erent sources in terms of complexity (number of participants), duration,
and granularity of events is evident. Due to these reasons, also the schemas
used to represent events across di erent sources are distinct, yet overlapping.
While certain properties (for instance for time points) are overlapping yet follow
di erent conventions, we lifted the events from di erent sources into a uni ed
dataset following Linked Data principles and deploying a joint RDF schema.</p>
      <p>Exposing Events Data as RDF.</p>
      <p>We have exposed the WikipEvent events data through a public Linked Data</p>
      <sec id="sec-1-1">
        <title>2 http://data.l3s.de/dataset/wikitimes</title>
        <p>WikipEvent: Temporal Event Data for the Semantic Web
interface using D2R Server3, enabling URI dereferencing via content negotiation
and providing a public SPARQL endpoint. This data can be accessed and queried
via http://wikipevent.l3s.uni-hannover.de/ and using our SPARQL
endpoint4.</p>
        <p>We represent events through established event RDF vocabularies, to facilitate
reuse, interpretation and linking of our data through third parties. In particular,
we use properties from the LODE ontology5 to map di erent properties
pertaining to events in our dataset, for instance, property lode:atPlace is used as
predicate for stating venues of events. Figure 1 presents an example of an event
and its entailing properties in our event repository.
3</p>
      </sec>
    </sec>
    <sec id="sec-2">
      <title>Use Case Scenarios</title>
      <p>
        WikipEvent can help students, scholars, historians, or journalists by facilitating
temporal search focussed on either the entities at hand or the events. Thus, the
WikipEvent framework can be used to satisfy two primary scenarios -
entitybased and event-based information needs. Results are presented through a
userfriendly interface, that supports faceted search, query-path tracing, query
completion, temporal settings, and is abridged with events' sources as well as lters
for related entities. The underlying versioning system [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], helps us to identify
signi cant wikipage revisions of the entities involved in the event. These
signi cant revisions of wikipages are also presented to the user in addition to the
timeline of events. As introduced in our previous work, a signi cant revision is
one where the edits between preceding and succeeding revision are above a
certain threshold. Here, the notion of signi cance is modeled based on the Cosine
distance between successive revisions [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ].
      </p>
      <p>Entity-based Search. Users may want to learn about entities of interest
with respect to their temporal participation in events. For example, journalists
might aim at studying political a liations of individuals, and the campaigns
3 http://d2rq.org/
4 http://wikipevent.l3s.uni-hannover.de/snorql/
5 http://linkedevents.org/ontology/
they participated in. Existing systems however, make it cumbersome to easily
access this information. The WikipEvent interface overcomes this challenge by
presenting a timeline of events that an entity is involved in. Additional lters
for relevant entities help users to navigate through the retrieved results. Figure
2 presents an example of an entity-based search on WikipEvent.</p>
      <p>Event-based Search. Historic events are a subject of interest to a wide
array of people, ranging from students to archivists. WikipEvent facilitates a
free-text search for events. Events relevant to a given query are presented in the
form of a continuous timeline (Figure 3), while highlighting the entities involved.
WikipEvent enables users to sift through event related information on a temporal
basis, in order to learn more about the events and the participating entities.</p>
      <p>To gain a complete understanding of the WikipEvent framework, we point
the reader to a demo video 6.</p>
      <sec id="sec-2-1">
        <title>6 A demo video is available on the home screen of the web interface.</title>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <given-names>Andrea</given-names>
            <surname>Ceroni</surname>
          </string-name>
          , Mihai Georgescu, Ujwal Gadiraju, Kaweh Djafari Naini, and
          <string-name>
            <given-names>Marco</given-names>
            <surname>Fisichella</surname>
          </string-name>
          .
          <article-title>Information evolution in wikipedia</article-title>
          .
          <source>In Proceedings of the 10th International Symposium on Open Collaboration, OpenSym '14. ACM</source>
          ,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2. Johannes Ho art, Fabian M Suchanek,
          <string-name>
            <given-names>Klaus</given-names>
            <surname>Berberich</surname>
          </string-name>
          , and Gerhard Weikum.
          <article-title>Yago2: a spatially and temporally enhanced knowledge base from wikipedia</article-title>
          .
          <source>Articial Intelligence</source>
          ,
          <volume>194</volume>
          :
          <fpage>28</fpage>
          {
          <fpage>61</fpage>
          ,
          <year>2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <given-names>Giang</given-names>
            <surname>Binh</surname>
          </string-name>
          Tran and
          <string-name>
            <given-names>Mohammad</given-names>
            <surname>Alrifai</surname>
          </string-name>
          .
          <article-title>Indexing and analyzing wikipedia's current events portal, the daily news summaries by the crowd</article-title>
          .
          <source>In Proceedings of the companion publication of the 23rd international conference on World wide web companion</source>
          , pages
          <volume>511</volume>
          {
          <fpage>516</fpage>
          ,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Tuan</surname>
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Tran</surname>
            , Andrea Ceroni, Mihai Georgescu, Kaweh Djafari Naini, and
            <given-names>Marco</given-names>
          </string-name>
          <string-name>
            <surname>Fisichella</surname>
          </string-name>
          .
          <article-title>Wikipevent: leveraging wikipedia edit history for event detection</article-title>
          .
          <source>In Web Information Systems Engineering - WISE</source>
          <year>2014</year>
          , Thessaloniki, Greece,
          <fpage>12</fpage>
          -14
          <source>October</source>
          <year>2014</year>
          , Proceedings,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>