<!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>Denoting Data in the Grounded Annotation Framework</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Marieke van Erp</string-name>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Antske Fokkens</string-name>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Piek Vossen</string-name>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Sara Tonelli</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Willem Robert van Hage</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Luciano Sera ni</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Rachele Sprugnoli</string-name>
          <email>sprugnolig@fbk.eu</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Jesper Hoeksema</string-name>
          <email>j.e.hoeksemag@vu.nl</email>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Fondazione Bruno Kessler</institution>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>SynerScope B.V</institution>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>VU University Amsterdam</institution>
        </aff>
      </contrib-group>
      <abstract>
        <p>Semantic web applications are integrating data from more and more di erent types of sources about events. However, most data annotation frameworks do not translate well to semantic web. We describe the grounded annotation framework (GAF), a two-layered framework that aims to build a bridge between mentions of events in a data source such as a text document and their formal representation as instances. By choosing a two-layered approach, neither the mention layer, nor the semantic layer needs to compromise on what can be represented. We demonstrate the strengths of GAF in exibility and reasoning through a use case on earthquakes in Southeast Asia.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>Semantic web applications are ingesting data from more and more di erent
sources such as output from natural language processing applications, sensor
data, videos or nancial transactions. Each of these domains has their own data
annotation practices which rst need to be reconciled with semantic web
standards. One issue with integrating information from di erent sources is that
representation formats tend to look at their domain in isolation, making it di cult
to integrate information that comes from other domains.</p>
      <p>
        The Grounded Annotation Framework (GAF) [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] aims at addressing this
problem by distinguishing instance mentions which can be domain speci c from
instances conform to domain independent semantic web standards. In this
manner, we can integrate information for example extracted by NLP tools or from
sensor data in a formal context which can be shared by di erent applications
and over which we can perform reasoning. This paper addresses the advantages
of using GAF from the point of view of users of Linked Data.
      </p>
      <p>We will describe GAF in Section 2, present an example in Section 3 and
conclude with pointers for future work in Section 4.</p>
      <p>
        The Grounded Annotation Framework
The main property of GAF is that it distinguishes instances from instance
mentions. A mention is the act of referring to an object where an instance
is the object itself. The relation between instances and mentions is de ned by
gaf:denotedBy, which is the only new predicate GAF introduces. Di erent
resources (or even the same resource) may refer to an instance in di erent ways
and each of these references may have properties of its own. This is quite
common in natural language, where authors tend to alternate terms to refer to the
same object for stylistic reasons, but it can also play a role in other sources of
information. If, for instance, a sensor displays a measured temperature, this
displayed value has properties of its own that are clearly not properties of the value
that was measured, such as the instrument that was used to measure it and its
error rate. In the remainder of this contribution, we will illustrate GAF through
the example of presenting instances in the Simple Event Model (SEM) [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] and
mentions in the TERENCE Annotation Format (TAF) [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] which represents
linguistic properties.
      </p>
      <p>
        SEM is a model to express who did what, where, and when. It is not the
only RDF model to describe events but as SEM is not tied to a any domain
and is among the most exible, we chose this model as the core of our semantic
layer. It should be noted however that, in principle any RDF schema can be
integrated into GAF. TAF is designed to annotate coreference relations between
event mentions as well as participants, locations and temporal expressions, which
covers the kind of information also represented in SEM. TAF has the additional
advantage that it already distinguishes between instances and instance mentions
for participants and locations. We use a slightly adapted variant of TAF that
extends this distinction to events and temporal expressions as described in [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ].
We chose TAF as it is based on the ISO-TimeML standard and ts our event
use-case, however, any representation format can be used in GAF.
      </p>
      <p>
        The gaf:denotedBy relations is used to link events represented in SEM to
speci c mentions represented in TAF. If a linguistic analysis identi es a syntactic
relation between an event mention and the mention of a person, we can derive
that this person is an Actor of the event in SEM according to the analysis of
a speci c text. Mentions thus play an important role in modelling provenance
of information. To model provenance we use the PROV-O ontology [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] as it
is compatible with our RDF representation and is recommended by W3C for
provenance modelling. When we represent alternative views in SEM, these views
are linked to the mentions they were derived from. This leads us to the original
source and hence information in who expressed which view.
      </p>
    </sec>
    <sec id="sec-2">
      <title>Creating GAF Annotations</title>
      <p>
        GAF annotations can be created both by starting from the linguistic layer and
the semantic layer. When starting from text for the mention layer, rst TAF
annotations are added to the text using the Celct Annotation Tool [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], which are
then translated to SEM relations using a conversion script. Instances extracted
from a particular source (for example a document) are grouped into named
graphs, to which provenance information is added. We use manually de ned
rules for mapping TAF to SEM, but plan to use machine learning in the future.
      </p>
      <p>
        When starting from the semantic layer, events and event properties are linked
to textual mentions. We are currently working towards an annotation
environment based on CROMER [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], which will allow the user to switch easily between
the linguistic and semantic layers.
3
      </p>
      <p>Examples
The example sentences shown in Figure 1 both contain information about the
2004 Indian Ocean Earthquake and Tsunami. The articles disagree on the cause
of the earthquake; where Bloomberg ascribes it to moving tectonic plates,
Veteran's Today sees a stealth attack submarine as the likely cause. Figure 2 shows
that these two declarations can co-exist within the GAF representation of the
earthquake. It is up to the application or user accessing the information to
interpret the fact that there is a contradiction and for example select only particular
sources for further processing. GAF provides the glue to connect non-semantic
web data to semantic web representation formats. The rdfs:isDe nedBy relation
at the top of Figure 2 shows how RDF predicates can be used to link GAF
representations to external resources such as the Linked Open Data cloud.1
"Indonesia lies in a zone where the Indo-Australian, Eurasian, Philippine and Pacific plates
meet and occasionally shift, causing earthquakes and sometimes generating tsunamis. There
have been hundreds of earthquakes in Indonesia since a 9.1 temblor in 2004 caused a
tsunami that swept across the Indian Ocean, devastating coastal communities and leaving more
than 220,000 people dead in Indonesia, Sri Lanka, India, Thailand and other countries."
(Bloomberg, 2009-01-07 01:55 EST)
"...were most concerned about the cause, scope, and consequences of the December 26, 2004
Indian Ocean tsunamis because they were far bigger and more destructive than they had
anticipated. More important, it had no clear alibi that their most likely source of the
disaster, the Multi-Mission Platform of the new stealth attack submarine, the USS Jimmy
Carter, had not been the culprit."
(Veteran's Today, 2011-10-02)
We have presented GAF, a grounded annotation framework for integrating
information from various sources. We have shown its exibility in representing
contradicting information from di erent textual sources.</p>
      <p>We are currently developing an annotation tool that allows users to easily
switch between linguistic and semantic annotation layers. After which we plan
to develop tools supporting easy integration of other types of information, such
as data from the Linked Open Data cloud, video metadata or sensor data.
1 http://groundedannotationframework.org/ provides full examples and the GAF
definition.</p>
    </sec>
    <sec id="sec-3">
      <title>Acknowledgements</title>
      <p>This research is supported by the European Unions 7th Framework Programme
via the NewsReader Project (ICT-316404) and by the BiographyNet project,
funded by the Netherlands eScience Center (http://esciencecenter.nl/).
sem:Place</p>
      <p>dbpedia:Bloomberg
dbpedia:Veterans_Today rdf:type
prov:at ributedTo</p>
      <p>skos:exactMatch
gaf:G2
dbpedTirau:nScuhndra_
skos:exact</p>
      <p>Match
gaf:INSTANCE_200
owl:objectProperty sem+:causes
wn30:synset-stableadjective-1
gaf:INSTANCE_201
skos:exact</p>
      <p>Match
dbpedia:USS_Jimmy_Carter
_(SSN_23)
gaf:INSTANCE_202
sem:Event
rdf:type</p>
      <p>rdf:type
rdf:type rdf:type rdf:type
dbepaerdthiaq:u2a0k0e4__aInnddi_ants_uOncaemain_
wn30:synnosuent--1tsunami</p>
      <p>sem:EventType
sem:subEventOf
sem:EventTypesem:subEventOf</p>
      <p>gaf:INSTANCE_188
sem+:causes
gaf:INSTANCE_186
taf:INSTANCE_MENTION_118
taf:causal_c
taf:INSTANCE_MENTION_120
prov:at ributedTo rdfs:isDefinedBy</p>
      <p>gaf:G3
dbpedia:Tectonic_Plate
gaf:INSTANCE_197
sem:has
Actor
wn30:synset-shiftverb-4</p>
      <p>rdf:type sem:EventType
sem:EventType gaf:INSTANCE_181</p>
      <p>gaf:causes sem:subEventOf
gaf:INSTANCE_179
skos:exactMatch</p>
      <p>gaf:denotedBy
gaf:G4</p>
      <p>gaf:denotedBy
taf:INSTANCE_MENTION_112
taf:hasParticipant</p>
      <p>_nsubj
taf:INSTANCE_MENTION_40
str:anchorOf str:anchorOf
"plates"@en "shift"@en</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Fokkens</surname>
            , A., van Erp,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vossen</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tonelli</surname>
            , S., van Hage,
            <given-names>W.R.</given-names>
          </string-name>
          , Sera ni, L.,
          <string-name>
            <surname>Sprugnoli</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hoeksema</surname>
            ,
            <given-names>J.:</given-names>
          </string-name>
          <article-title>GAF: A grounded annotation framework for events</article-title>
          .
          <source>In: Proceedings of the rst Workshop</source>
          on Events: De nition, Dectection, Coreference and Representation, Atlanta, USA (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <given-names>Van</given-names>
            <surname>Hage</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.R.</given-names>
            ,
            <surname>Malaise</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            ,
            <surname>Segers</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            ,
            <surname>Hollink</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            ,
            <surname>Schreiber</surname>
          </string-name>
          ,
          <string-name>
            <surname>G.</surname>
          </string-name>
          :
          <article-title>Design and use of the simple event model (SEM)</article-title>
          .
          <source>Journal of Web Semantics</source>
          (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Moens</surname>
            ,
            <given-names>M.F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kolomiyets</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pianta</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tonelli</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bethard</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <source>D3</source>
          .
          <article-title>1: State-ofthe-art and design of novel annotation languages and technologies: Updated version</article-title>
          .
          <source>Technical report, TERENCE project-ICT FP7 Programme-ICT-2010-25410</source>
          (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Moreau</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Missier</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Belhajjame</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>B'Far</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cheney</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Coppens</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cresswell</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gil</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Groth</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Klyne</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lebo</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>McCusker</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Miles</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Myers</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sahoo</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tilmes</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          :
          <article-title>PROV-DM: The PROV Data Model</article-title>
          .
          <source>Technical report, W3C</source>
          (
          <year>2012</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <given-names>Bartalesi</given-names>
            <surname>Lenzi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            ,
            <surname>Moretti</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            ,
            <surname>Sprugnoli</surname>
          </string-name>
          , R.:
          <article-title>CAT: the CELCT Annotation Tool</article-title>
          . In
          <source>: Proceedings of LREC</source>
          <year>2012</year>
          .
          <article-title>(</article-title>
          <year>2012</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Bentivogli</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Girardi</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pianta</surname>
          </string-name>
          , E.:
          <article-title>Creating a Gold Standard for Person CrossDocument Coreference Resolution in Italian News</article-title>
          . In: Workshop on Resources and
          <article-title>Evaluation for Identity Matching, Entity Resolution</article-title>
          and
          <string-name>
            <given-names>Entity</given-names>
            <surname>Management</surname>
          </string-name>
          . (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>