<!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>A neural network based Event extraction system for Indian languages</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Alapan Kuila</string-name>
          <email>alapan.cse@iitkgp.ac.in</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Sarath chandra Bussa</string-name>
          <email>bussasarath2@gmail.com</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Sudeshna Sarkar</string-name>
          <email>sudeshna@cseiitkgp.ac.in</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Indian institute of Technology kharagpur</institution>
          ,
          <country country="IN">India</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>In this paper we have described a neural network based approach for Event extraction(EE) task which aims to discover different types of events along with the event arguments form the text documents written in Indian languages like Hindi, Tamil and English as part of our participation in the task on Event Extraction from Newswires and Social Media Text in Indian Languages at Forum for Information Retrieval Evaluation (FIRE) in 2018. A neural netork model which is a combination of Convolution neural network(CNN) and Recurrent neural network(RNN) is employed for the Event identi cation task. In addition to event detection, the system also extracts the event arguments which contain the information related to the events(i.e. when[Time], where[Place], Reason, Casualty, After-effect etc.). Our proposed Event Extraction model achieves f-score of 39:71; 37:42 and 39:91 on Hindi, Tamil and English dataset respectively which shows the overall performance of Event identi cation and argument extraction task in these three language domain.</p>
      </abstract>
      <kwd-group>
        <kwd>Event extraction Convolution neural network(CNN) Recurrent neural network(RNN)</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>A huge number of news on events, occuring in different corners of the world, are
reported each moment in online and printed media. To keep track of those news,
it is very important to identify relevant events and extract the spatio-temporal
aspects about those events. Understanding events and their descriptions in raw
text is the key factor in automatic event extraction which is an important and
challenging task in Natural Language Processing(NLP) and Information
Extraction(IE). It is also essential in practical applications like news summerization,
information retrival and knowledge base construction. Event extraction is an
important and challenging task in Information extraction(IE) which aims to detect,
from the text, the occurrence of events of speci c types, and to discover the
arguments(event participants or attributes) that are associated with the event. Event
Arguments are basically represents the event related information i.e. capturing
who does what to whom, how, when and where. For example,</p>
      <p>{ S1: Mild earthquake has been found in Indonesia's Sulawesi island.</p>
      <p>A typical automatic Event extraction system will identify from S1 that the
sentence depicts a Earthquake event and it also extract some important
information related to the earthquake such as, Place of the event: Indonesia's
Sulawesi island.</p>
      <p>
        Current event extraction systems rely on examining event trigger words to
check if an event occurs or not and if occurs then what is the type of the event.
An event trigger is a word or phrase that clearly express the occurrence of
an event. For example, in S1, earthquake is the trigger word as it is the most
salient clue in the sentence to identify the Earthquake. The Understanding and
identifying event triggers in raw text is an important and challenging problem
as the same event may be expressed by various trigger expressions and an
speci c event trigger might be used to represent different events in different context.
From the previous research it is evident that Event detection task is not a simple
trigger-token searching task. And Contextual feature information is very much
important in identi cation and classi cation of event triggers. Event argument
extraction is another challenging task. Unlike entity identi cation task, event
argument extraction task deals with discovering the speci c entities which are
relevant to the events appeared in the document. So typical NER systems are not
sufficient to solve the problem. Previously, we have worked on detecting the
segment of the text which contains some event related information from twitter[
        <xref ref-type="bibr" rid="ref18">18</xref>
        ].
This task is the extension of the previous work. Here we have tried to identify
the events as well as event arguments from news documents using supervised
learning procedure with the help of annotated corpus where event triggers and
argument phrases are tagged. So our contribution in this task is two fold. First,
we have designed a hybrid neural network based model for event extraction from
news document written in Indian languages like Hindi and Tamil as well as
English and second, we have represented the extracted events in structured format
(Table1).
2
      </p>
    </sec>
    <sec id="sec-2">
      <title>Related Studies</title>
      <p>
        A plethora of works have already been done in event extraction from text
documents. However supervised methods are dominant in this problem which
requires annotated training data to employ machine learning based approaches.
Previously, the researchers have designed various feature (lexical, contextual,
syntactic) based approach for Event Detection[
        <xref ref-type="bibr" rid="ref3 ref4">3, 4</xref>
        ]. But the problem with these
approaches is that they require thorough feature engineering, and extensive
language knowledge which also impede the designing of language independent ED
model.
      </p>
      <p>
        Now neural networks are widely applied in NLP tasks including Event
Extraction(EE) as they automatically extract underlying features. Some of the
papers apply Bidirectional recurrent neural networks(Bi-RNN) as it is capable
to capture both preceding and following context information of each token in the
sentence[
        <xref ref-type="bibr" rid="ref1 ref7">1, 7</xref>
        ]. Some have also used convolution neural network(CNN) as CNN is
good at capturing features from a sequence of objects [
        <xref ref-type="bibr" rid="ref1 ref2 ref5 ref7">1, 2, 5, 7</xref>
        ]. Liu et al., 2017
has used event argument information to enhance the quality of event detection
accuracy[
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. Peng et al., 2016 has tried to detect events from text documents
using minimal supervision approach where system needs only annotation
guidelines[
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]. It formalizes the problem as a semantic similarity problem[
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. Some
works also exists where researchers have tried to solve it through frame semantic
parser[
        <xref ref-type="bibr" rid="ref9">9</xref>
        ].
      </p>
      <p>
        Here, we are interested in news events depicting man-made or natural
disasters. In the disaster domain, maximum research works are centered around
extracting events from user generated content such as social media texts.
Extracting event from social media text consists of two subtask: Identi cation of
informative tweets and detecting events from those informative tweets[
        <xref ref-type="bibr" rid="ref10">10</xref>
        ].
Arti cial Intelligence for Disaster Response (AIDR) [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] is one such platform that
has been successfully deployed that works on streaming microblog text (twitter)
to classify messages that people post during disasters into a set of user-de ned
categories of information. Muhammad et al. (2013) has extracted disaster
relevant information from twitter and classi ed them into personal, informative
and others[
        <xref ref-type="bibr" rid="ref12">12</xref>
        ]. Something similar has been done by Chowdhury et al. (2013),
who has classi ed crisis related tweets and categorize them into: Pre-incident,
during-incident and post-incident events[
        <xref ref-type="bibr" rid="ref13">13</xref>
        ].
      </p>
      <p>
        Event extraction are also represented as a natural language understanding
problem. Previously, natural language understanding task was highly
dependent on script knowledge[
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]. Though script knowledge is very useful in
eventevent relation extraction and causality detection but scripts are heavily domain
dependent and too expensive to create[
        <xref ref-type="bibr" rid="ref15">15</xref>
        ]. To get the event structure
knowledge from documents, narrative event chain is introduced by Chambers and
Jurafsky(2009)[
        <xref ref-type="bibr" rid="ref14 ref16">14, 16</xref>
        ]. Event Detection is also formalized as Semantic Role
labeling(SRL) problem[
        <xref ref-type="bibr" rid="ref17">17</xref>
        ]. But the problem is that these works take only verbs
as events and from our experience we know that events could be noun, verb
or adjective. Chambers and Jurafsky(2009) have introduced the concept of the
protagonist[
        <xref ref-type="bibr" rid="ref14">14</xref>
        ] for event representation, which is also not feasible in case of
disaster related news documents. Though there exists several successful works for
English language such as ACE, TAC evaluation tracks 1 but there is no such
standard event extraction tool for Indian Languages. So we see that none of the
previous work is adequate to tackle the problem of event extraction from news
documents written in Indian languages.
3
      </p>
    </sec>
    <sec id="sec-3">
      <title>Problem Description</title>
      <p>Here, we focus on the sentence level Event extraction task. Given a news
document we want to extract the events inside that document and represent the events
in structured format. Our work covers the events which depicts the occurrence
of any disasters caused by nature (e.g. Flood, Earthquake etc.) or manmade
(e.g. terrorist attack, accident, riot etc). The term Event covers the type of the
1 https://tac.nist.gov/2017/KBP/Event/index.html
event and the event participants or arguments which depicts the informations
regarding that event(i.e. when[Time], where[Place], cause, effect etc). So while
extracting events rst we have to identify the type of the extracted event based
on the trigger word found in the text. Event argument identi cation is the
another crucial module of our system as arguments are realy important to describe
the events. Each event has some general attributes like place(where), time(when)
and some speci c attributes like cause, after-effect, magnitude. Our interest is
to identify these attributes for each events which are present in the document.
And if the same event has more than one argument of same type then we have
to aggregate the argument information accordingly such that no super uous
information exist in nal outcome. Table 1 depicts sentence level event extraction
output where each row indicates one event mention with corresponding argument
information.</p>
      <p>This section describes the dataset that have been used in this work. The training
and the test data have been made available to the task participants by the
organizers. The training dataset consists of annotated documents where event
trigger words as well as event arguments are tagged. The testset contains news
documents without any annotations. The dataset statistics is represented in
Table 2.</p>
    </sec>
    <sec id="sec-4">
      <title>Methodology</title>
      <p>An event extraction problem can be further subdevided into two subtasks:
(1)Event Detection, the task of nding the event mentions of prede ned event
types and (2)Event argument extraction , the identi cation of event related
information like time, place, cause, effect which are relevant to the event mentions. We
formalize the Event Detection(ED) problem as a multi-class classi cation
problem via combination of convolution neural network(CNN) and bidirectional Long
short term memory (Bi-LSTM). We expect that the Bi-LSTM and CNN would
capture syntactic and semantic information from the text so their combination
would help to enhance the overall ED performance. Let, we have k numbers of
prede ned event types E1; E2; :::; Ek. Now, given a sentence S = w1w2w3:::wn,
where n is the sentence length, for each word wi in the sentence, we want to
predict whether the current token is an valid event trigger. And if it is an event
trigger then with which event type Ej the word wi will be matched. So, the
current word along with its sentential context constitute an event trigger
candidate which will be input to our classi cation model. We have xed the context
window size in order to feed the trigger candidate to the CNN.</p>
      <p>If the window size is k then trigger candidate for word W would be
represented as [w k; w k+1; :::; w0; :::; wk 1; wk] where current word is positioned in
the middle position (i.e. w0). Now these (2k +1) size trigger candidates are taken
as input to the CNN and Bi-LSTM models.</p>
      <p>Before entering the CNNs and Bi-LSTMs, each word is converted into a real
valud vector by looking up a embedding table with an intution that these real
valued vectors will capture various semantic characteristics of the words. So the
input to our model is a matrix X of size (2k + 1) jV j where jV j is the dimension
of the real valued vectors and X = [x k; x k+1; :::; x0; :::; xk 1; xk] where xj is
the vector representation of word wj . Now the two dimensional representation
of each word is feed to a convolution layer followed by a max-pooling layer.</p>
      <p>In convolution layer we have used a set of lters F1; F2; ::Fp and each lter Fi
has a window size mi and can be represented as a matrix of size mi jV j. After
employing max-pooling on the convolution layer output we get a hidden vector
representation of size jF1j + jF2j + ::: + jFpj where, jFij represents the number of
instances of lter type Fi. The hidden vector representation which we get from
CNN model is named as FCNN .</p>
      <p>Besides CNN, we have also used Bi-directional Long Short Term
Memory(BiLSTM) in this work. The matrix representation of each word W which is
represented as X = [x k; x k+1; :::; x0; :::; xk 1; xk], is also feed to the Bi-LSTM
model. The hidden states of Bi-LSTM are computed both in forward and
backward ways at each time step. We denote the outputs of the forward and backward
LSTM as !ht and h′t respectively. At each time step t, hidden vector hi is
computed based on current input vector xt and previous hidden vector ht 1.
!ht = LST M!(ht!1; wt)
h′t = LST M (h′t 1; wt)
(1)</p>
      <p>Then the output at time t is ht = [!ht; h′t]. Here we have taken the hidden
representation of x0 i.e. concatination of hidden vector representation of forward
LSTM h!0 And hidden vector representation of h′0 as the output of the Bi-LSTM.
Formally, FBi LST M = [h!0; h′0].</p>
      <p>Now to combine the output of CNN and Bi-LSTM we have concatenated the
representation vector FCNN and FBi LST M and feed the concatenated vector
to a fully connected layer followed by a softmax layer to get the proper event
type of the current word W (see Fig. 1). The gradients are calculated using
back-propagation. We have also implemented regularization by dropout.</p>
      <p>For Event-Argument Extraction we have applied the same model which is
used for Event Trigger classi cation. Only the number of output classes is
different in these two models. We have used BIO annotation scheme for argument
identi cation as most of the arguments contain more than a single token.</p>
      <p>Now after Event-Trigger and Event-Arguments have been identi ed, our
next task is to link the event arguments (which are identi ed by the
EventArument extractor) to their corresponding event trigger words so that we can
identify the event participants for a speci c event trigger. For Event
TriggerArgument linking we have taken a simple heuristic based approach where,
For each argument phrase we have identi ed the nearest event trigger word and
link those argument- trigger pair. The distance between trigger and argument is
calculated by the number of sentences between them and if a tie is there then
decision has been taken by number of tokens in between the pairs. Sometimes,
a sentence contains useful argument information regarding an event but there
exist no event-trigger word in that very sentence. In that situation the argument
is mapped to nearest event-trigger present in the previous or next sentence.
6</p>
    </sec>
    <sec id="sec-5">
      <title>Resources and Hyperparameters</title>
      <p>We have used the same parameters for the neural network models used in trigger
identi cation and argument extraction. In Convolution neural network we have
used lter size of 2; 3; 4 and for each size we have taken 200 lters to generate
feature maps from the convolution operatons. The nal output of the CNN is
represented as FCNN which has size 600. The number of hidden units used
in Bi-LSTM is 200 which leads to the size of nal outcome of the Bi-LSTM
layer FBi LST M is 400. Regarding embedding, we have used pre-trianed word
embeddings of size 300 which we have taken from the fastText toolkit2. Finally,
we have trained the neural network models using adam optimizer with suffled
minibatches, dropout rate=0.5, backpropagation for gradient calculation and
parameter modi cation.
7</p>
    </sec>
    <sec id="sec-6">
      <title>Result Analysis</title>
      <p>According to the FIRE 2018 official evaluation metodology the performance of
the system is measured by the Precision and Recall and F-score. For example,
let there is an Event-mention E1 and there are six elds such as Event Type,
Location, Time, Event-Participants, Causes, Effects for that event. Now for that
event E1, if all these elds are identi ed correctly then the system gets full score
of 1 else according to the identi ed elds the score will be calculated. And
nally macro-average of the Precision and Recall is calculated for all events in
all documents. And the performance of our system is depicted in 3. From the
result, we can conclude that we have to improve the Recall score to enhance
the system performance. In all the three languages the precision score is quite
acceptable but due to low Recall, overall performance of the system is not so
satisfactory.
2 https://github.com/facebookresearch/fastText/blob/master/pretrained-vectors.md
Our event extraction system has three steps. Firstly we have ident ed the event
trigger words. Then, we have extracted argument phrases. Lastly we have linked
the arguments with their nearest trigger words. We have split the training data in
the the ratio of 80:20 and use the rst partition(80%) for training and remaining
20% as development set. In this section we will try to analyze the system's
performance on development set and examine the shortcomings of the system.
8.1</p>
      <sec id="sec-6-1">
        <title>Event Identi caton:</title>
        <p>While identifying the trigger words, system sometimes fail to get the contextual
information which has an important role in event identi cation. For example:
{ S2: Nepalese Maoists will not attack on ordinary people and politicians any
more.</p>
        <p>The system tagged attack as an event trigger of type Terrorist-Attack. But from
the context it is clear that this sentence does not describe any terrorist attack
event.</p>
        <p>{ S3: It is reported that 56 people were also wounded in the bombing in the
neighborhood of Dasht-e-Barchi.</p>
        <p>The event identi cation module sometimes failed to correctly classify the event
types present in the documents. We have noticed that the system is confused
among related event types like terrorist-attack, Shoot-out, Suicide-attack or
Vehicular-Collision, Transport-hazard and Accident. For example, in S3,
system classi ed trigger word bombing as Shoot-out type event but it is actually an
event of type Suicide-attack.</p>
        <p>{ S4: Officials blame the Islamic State group for this attack.</p>
        <p>In some of the cases system failed to detect the correct event triggers from the
sentences. For example, in S4, system failed to identify attack as an event trigger
word.
8.2</p>
      </sec>
      <sec id="sec-6-2">
        <title>Event-Argument Identi caton:</title>
        <p>We have checked the argument extraction output and identi ed some errors,
which we will dicuss below.</p>
        <p>Symantic Variety: Based on development set, have noticed that our system
performance is not so satisfactory for some frequent arguments like Place, Time.
The possible cause is the symantic variety. Some arguments are represented in
a very speci c way. For example,
{ S5:The magnitude of the rst quake was 4.9.
{ S6:After a short span there is an another earthquake whose magnitude is
4.1.
{ S7:The Governor of California was injured in a motorcycle accident near
the house on Sunday afternoon.</p>
        <p>The magnitude of quake is represented very speci c way (example S5, S6)
and it is always a numeric value. But arguments like place is not all time a place
entity which can be detected by typical Named entity recognizer(NER) systems.
For example in S7, near the house is not a typical location entity, but is the
place of event type VEHICULAR COLLISION.</p>
        <p>Token missing in phrase: Most of the event arguments are more than one
word phrase. But our system is failed to identify all the words in the phrase which
leads to missing important information regarding the event. For example, in the
S7 our system has extracted Sunday as time argument whereas the accurate
time information will be Sunday afternoon.</p>
        <p>Reason and After-effect: Our system has failed to identify arguments like
Reason and After-effect for any event instance. Most of the time reason and
effect of any event is an event itself and are represented by a long sequence of
words or phrase. But as there is no such speci c pattern in these two arguments
the system is failed to identify them. The cases where there is a semantic clue
present in the sentence then system can identify it. For example:
{ S8:US Airways has been forced to land in Tehran due to mechanical
disruption on its way to Amsterdam with 255 passengers from Mumbai.
The system has accurately identi ed the reason of the AVIATION HAZARD
type event as: due to mechanical disruption. The presence of the term due to
may help in this case. But in most of the cases this type of clues is not present.
And the proposed system accuracy is miserably bad for these two attributes.
Some smarter technique have to be employed to improve our performance.
8.3</p>
      </sec>
      <sec id="sec-6-3">
        <title>Event trigger-argument linking:</title>
        <p>In this mdule, we have linked the event trigger words with its corresponding
arguments using a heuristic approach stated in Section 5.</p>
        <p>Incorrect assignment It is noticed that the heuristic approach which takes
nearest token for linking, may causes wrong output. Some times due to complex
syntatic structure of the sentence a valid argument may appear far away from
the trigger word and lots of other token are exist between that argument and the
valid trigger word. But our heuristic function has selected an incorrect
triggerargument pair. For example,</p>
        <p>{ S9: Translation: Earthquake in Indonesia.
{ S10: Mild earthquake has been found in Indonesia's Sulawesi island.
{ S11: Meanwhile, one Indian has died from the four oors of Manama Hotel
in Dubai.</p>
        <p>In the sentence S11, there is no trigger word of our interest but our
EventArgument extractor has identi ed One Indian has died as a casualty argument.
Our linking module will wrongly map this with EARTHQUAKE event in the
previous sentence(S10), though they are totaly unrelated.</p>
        <p>Mutual exclusiveness It is highly probable that one single argument may
be attribute of more than one different event instance. But according to our
heuristic function one argument can only be linked to a specif event trigger
word. These problem leads to missing important information in the extracted
events and directly affect system performance.
9</p>
      </sec>
    </sec>
    <sec id="sec-7">
      <title>Conclusion and Future Work</title>
      <p>The main problem that impede the designing of Event extraction model for
Indian language news document texts is scarcity of annoatated corpus. The
second hinderance is unavailability of syntactic and semantic feature extractor for
Indian languages. In this task we have relied on automatically learning
effective features from data, without using language speci c resources. So our hybrid
neural network model incorporates both bidirectional LSTM and CNN to
capture sequencial and structural information from text. Our main insight from is
that, the sentence level event extraction is not effective in case of news
documents. When we take a news article into consideration, we have noticed that the
detected events may have their arguments distributed along the length of the
document. Sometimes event arguments and corresponding event trigger may
appear in two different sentences. And it is evident that the event span(portion of
the document where event related information exist) may be a single sentence or
multiple sentence or even a whole document. So, identifying events on sentence
level will narrow down the event span which leads to a substantial loss in
acquired event related information. Eventually the sentence level event extraction
system is inadequate to get the document level view of the events.To cope up
with this problem, detection and aggregation of coreferring event mentions could
be an useful remedy. As future work we would like to explore more sophisticated
models for Event extraction and try to incorporate background knowledge and
other language resources to improve the system performance.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Nguyen</surname>
            , Thien Huu, Kyunghyun Cho, and
            <given-names>Ralph</given-names>
          </string-name>
          <string-name>
            <surname>Grishman</surname>
          </string-name>
          .
          <article-title>"Joint event extraction via recurrent neural networks." Proceedings of the 2016 Conference of the North American Chapter of the Association for Computational Linguistics: Human Language Technologies</article-title>
          .
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Chen</surname>
          </string-name>
          ,
          <string-name>
            <surname>Yubo</surname>
          </string-name>
          , et al.
          <article-title>"Event extraction via dynamic multi-pooling convolutional neural networks." Proceedings of the 53rd Annual Meeting of the Association for Computational Linguistics and the 7th</article-title>
          <source>International Joint Conference on Natural Language Processing (Volume 1: Long Papers)</source>
          . Vol.
          <volume>1</volume>
          . 2015
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Li</surname>
            , Qi,
            <given-names>Heng</given-names>
          </string-name>
          <string-name>
            <surname>Ji</surname>
            , and
            <given-names>Liang</given-names>
          </string-name>
          <string-name>
            <surname>Huang</surname>
          </string-name>
          .
          <article-title>"Joint event extraction via structured prediction with global features. " Proceedings of the 51st Annual Meeting of the Association for Computational Linguistics (Volume 1: Long Papers)</article-title>
          . Vol.
          <volume>1</volume>
          .
          <year>2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Hong</surname>
          </string-name>
          ,
          <string-name>
            <surname>Yu</surname>
          </string-name>
          , et al.
          <article-title>"Using cross-entity inference to improve event extraction." Proceedings of the 49th Annual Meeting of the Association for Computational Linguistics: Human Language Technologies-Volume 1</article-title>
          . Association for Computational Linguistics,
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Nguyen</surname>
            , Thien Huu, and
            <given-names>Ralph</given-names>
          </string-name>
          <string-name>
            <surname>Grishman</surname>
          </string-name>
          .
          <article-title>"Event detection and domain adaptation with convolutional neural networks." Proceedings of the 53rd Annual Meeting of the Association for Computational Linguistics and the 7th</article-title>
          <source>International Joint Conference on Natural Language Processing (Volume 2: Short Papers)</source>
          . Vol.
          <volume>2</volume>
          .
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6. Liu,
          <string-name>
            <surname>Shulin</surname>
          </string-name>
          , et al.
          <article-title>"Exploiting argument information to improve event detection via supervised attention mechanisms." Proceedings of the 55th Annual Meeting of the Association for Computational Linguistics (Volume 1: Long Papers)</article-title>
          . Vol.
          <volume>1</volume>
          .
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Feng</surname>
            , Xiaocheng,
            <given-names>Bing</given-names>
          </string-name>
          <string-name>
            <surname>Qin</surname>
          </string-name>
          , and Ting Liu.
          <article-title>"A language-independent neural network for event detection</article-title>
          .
          <source>" Science China Information Sciences 61.9</source>
          (
          <year>2018</year>
          ):
          <fpage>092106</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Peng</surname>
            , Haoruo,
            <given-names>Yangqiu</given-names>
          </string-name>
          <string-name>
            <surname>Song</surname>
            , and
            <given-names>Dan</given-names>
          </string-name>
          <string-name>
            <surname>Roth</surname>
          </string-name>
          .
          <article-title>"Event detection and co-reference with minimal supervision."</article-title>
          <source>Proceedings of the 2016 Conference on Empirical Methods in Natural Language Processing</source>
          .
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Spiliopoulou</surname>
            , Evangelia,
            <given-names>Eduard</given-names>
          </string-name>
          <string-name>
            <surname>Hovy</surname>
            , and
            <given-names>Teruko</given-names>
          </string-name>
          <string-name>
            <surname>Mitamura</surname>
          </string-name>
          .
          <article-title>"Event detection using frame-semantic parser</article-title>
          .
          <source>" Proceedings of the Events and Stories in the News Workshop</source>
          .
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Imran</surname>
          </string-name>
          ,
          <string-name>
            <surname>Muhammad</surname>
          </string-name>
          , et al.
          <article-title>"Practical extraction of disaster-relevant information from social media</article-title>
          .
          <source>" Proceedings of the 22nd International Conference on World Wide Web. ACM</source>
          ,
          <year>2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Imran</surname>
          </string-name>
          ,
          <string-name>
            <surname>Muhammad</surname>
          </string-name>
          , et al.
          <article-title>"AIDR: Arti cial intelligence for disaster response</article-title>
          .
          <source>" Proceedings of the 23rd International Conference on World Wide Web. ACM</source>
          ,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Imran</surname>
          </string-name>
          ,
          <string-name>
            <surname>Muhammad</surname>
          </string-name>
          , et al.
          <article-title>"Extracting information nuggets from disaster-related messages in social media</article-title>
          .
          <source>" Iscram</source>
          .
          <year>2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Chowdhury</surname>
            ,
            <given-names>Soudip</given-names>
          </string-name>
          <string-name>
            <surname>Roy</surname>
          </string-name>
          , et al.
          <article-title>"Tweet4act: Using incident-speci c pro les for classifying crisis-related messages</article-title>
          .
          <source>" ISCRAM</source>
          .
          <year>2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Chambers</surname>
            , Nathanael, and
            <given-names>Dan</given-names>
          </string-name>
          <string-name>
            <surname>Jurafsky</surname>
          </string-name>
          .
          <article-title>"Unsupervised learning of narrative event chains</article-title>
          .
          <source>" Proceedings of ACL-08: HLT</source>
          (
          <year>2008</year>
          ):
          <fpage>789</fpage>
          -
          <lpage>797</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Chambers</surname>
            , Nathanael, and
            <given-names>Daniel</given-names>
          </string-name>
          <string-name>
            <surname>Jurafsky</surname>
          </string-name>
          .
          <article-title>"A Database of Narrative Schemas."</article-title>
          <source>LREC</source>
          .
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>Pichotta</surname>
            , Karl, and
            <given-names>Raymond J.</given-names>
          </string-name>
          <string-name>
            <surname>Mooney</surname>
          </string-name>
          .
          <article-title>"Learning Statistical Scripts with LSTM Recurrent Neural Networks."</article-title>
          <source>AAAI</source>
          .
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>Exner</surname>
            , Peter, and
            <given-names>Pierre</given-names>
          </string-name>
          <string-name>
            <surname>Nugues</surname>
          </string-name>
          .
          <article-title>"Using semantic role labeling to extract events from Wikipedia." Proceedings of the workshop on detection, representation, and exploitation of events in the semantic web</article-title>
          (DeRiVE
          <year>2011</year>
          ).
          <article-title>Workshop in conjunction with the 10th international semantic web conference</article-title>
          .
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <surname>Kuila</surname>
            , Alapan, and
            <given-names>Sudeshna</given-names>
          </string-name>
          <string-name>
            <surname>Sarkar</surname>
          </string-name>
          .
          <source>"An Event Extraction System via Neural Networks." FIRE (Working Notes)</source>
          .
          <year>2017</year>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>