<!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>Mena B. Habib Maurice van Keulen</string-name>
          <email>m.b.habib@ewi.utwente.nl</email>
          <email>m.b.habib@ewi.utwente.nl m.vankeulen@utwente.nl</email>
          <email>m.vankeulen@utwente.nl</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Zhemin Zhu</string-name>
          <email>z.zhu@utwente.nl</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Extraction</string-name>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Extraction</string-name>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Database Chair Database Chair, University of Twente University of Twente</institution>
          ,
          <addr-line>Enschede</addr-line>
          ,
          <country country="NL">The Netherlands</country>
          <addr-line>Enschede</addr-line>
          ,
          <country country="NL">The Netherlands</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Database Chair, University of Twente</institution>
          ,
          <addr-line>Enschede</addr-line>
          ,
          <country country="NL">The Netherlands</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Phase1: NE Candidates</institution>
          ,
          <addr-line>Generation</addr-line>
        </aff>
        <aff id="aff3">
          <label>3</label>
          <institution>Phase2: NE Candidates</institution>
          ,
          <addr-line>Filtering</addr-line>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2014</year>
      </pub-date>
      <volume>1141</volume>
      <abstract>
        <p>Twitter is a potentially rich source of continuously and instantly updated information. Shortness and informality of tweets are challenges for Natural Language Processing (NLP) tasks. In this paper we present a hybrid approach for Named Entity Extraction (NEE) and Linking (NEL) for tweets. Although NEE and NEL are two topics that are well studied in literature, almost all approaches treated the two problems separately. We believe that disambiguation (linking) could help improving the extraction process. We call this potential for mutual improvement, the reinforcement effect. It mimics the way humans understand natural language. Furthermore, our proposed approaches handles uncertainties involved in the two processes by considering possible alternatives.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;Named Entity Extraction</kwd>
        <kwd>Named Entity Linking</kwd>
        <kwd>Social Media Analysis</kwd>
        <kwd>Twitter Messages</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>Extraction</p>
      <p>Linking
Our Approach For NEE &amp; NEL</p>
      <p>Linking</p>
      <p>
        According to a literature survey, almost no research tackled the
combined problem of NEE &amp; NEL. Researchers either focus on
NEE or NEL but not both. Systems that do NEL like AIDA [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ],
either require manual annotations for NE or use some off-the-shelf
extraction models like Stanford NER [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. Here, we present a
combined approach for NEE and NEL for tweets with an application
on #Microposts 2014 challenge [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. Although the logical order for
such system is to do extraction first then the disambiguation, we
start with an extraction phase which aims to achieve high recall
(find as much NE candidates as possible). Then we apply
disambiguation for all the extracted mentions. Finally, we filter those
extracted NE candidates into true positives and false positives
using features derived from the disambiguation phase in addition to
other word shape and KB features. The potential of this order is
that the disambiguation step gives extra information about each NE
candidate that may help in the decision whether or not this
candidate is a true NE. Figure 1 shows our system architecture versus
traditional one.
      </p>
    </sec>
    <sec id="sec-2">
      <title>2. OUR APPROACH</title>
    </sec>
    <sec id="sec-3">
      <title>2.1 NE Candidates Generation</title>
      <p>
        For this task, we unionize the output of the following candidates
generation methods:
• Tweet Segmentation: Tweet text is segmented using the
segmentation algorithm described in [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. Each segment is
considered a NE candidate.
• KB Lookup: We scan all possible n-grams of the tweet against
the mentions-entities table of DBpedia. N-grams that matches
a DBpedia mention are considered NE candidates.
• Regular Expressions: We used regular expressions to
extract numbers, dates and URLs from the tweet text.
      </p>
    </sec>
    <sec id="sec-4">
      <title>2.2 NE Linking</title>
      <p>
        Our NEL approach is composed of three steps; matcher, feature
extractor, and SVM ranker.
• Matcher: This module takes each extracted mention
candidate and looks for its Wikipedia reference candidates on
DBpedia. Furthmore, for those mention candidates which
don’t have reference candidates in DBpedia, we use Google
Search API to find possible Wikipedia pages for these
mentions. This search helps to find references for misspelled or
concatenated mentions like ‘justinbieber’ and ‘106andpark’.
• Feature Extractor: This module is responsible for
extracting a set of contextual and URL features for each candidate
Wikipedia page as described in [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. These features give
indicators on how likely the candidate Wikipedia page could be
a representative to the mention.
• SVM Ranker: After extracting the aforementioned set of
features, SVM classifier is trained to rank candidate Wikipedia
pages of a mention. For the challenge, we pick the page on
the 1st order as a reference for the mention. The DBpedia
URI is then generated from the selected Wikipedia URL.
      </p>
    </sec>
    <sec id="sec-5">
      <title>2.3 NE Candidates Filtering</title>
      <p>
        After generating the candidates list of NE, we apply our NE linking
approach to disambiguate each extracted NE candidate. After the
linking phase, we use SVM classifier to predict which candidates
are true positives and which ones are not. We use the following set
of features for each NE candidate to train the SVM:
• Shape Features: If the NE candidate is initially or fully
capitalized and if it contains digits.
• Probabilistic Features:
– The joint and the conditional probability of the
candidate obtained from Microsoft Web N-Gram services.
– The stickiness of the candidate as described in [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ].
      </p>
      <p>– The candidate’s frequency over around 5 million tweets1.
• KB Features:
– If the candidate appears in WordNet.</p>
      <p>
        – If the candidate appears as a mention in DBpedia KB.
• Disambiguation Features:
– All the features used in the linking phase as described
in [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. We used only the feature set for the first top
ranked entity page selected for the given NE candidate.
      </p>
    </sec>
    <sec id="sec-6">
      <title>2.4 Final NE Set Generation</title>
      <p>
        Beside the SVM, we also train a CRF model for NEE. We used
the CRF model described in [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. To generate the final NE set, we
take the union of the CRF annotation set and SVM results, after
removing duplicate extractions, to get the final set of annotations.
We tried two methods to resolve overlapped mentions. In the first
method (used in UTwente_Run1.tsv), we select the mention that
appears in Yago KB [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. If both mentions appear in Yago or both
don’t, we select the one with the longer length. In the second
method (used in UTwente_Run2.tsv), we select only the mention
with the longer length among the two overlapped mentions. The
results shown in the next section are the results of the first method.
The idea behind this unionization is that SVM and CRF work in a
different way. The former is a distance based classifier that uses
numeric features for classification which CRF can not handle, while
the latter is a probabilistic model that can naturally consider
stateto-state dependencies and feature-to-state dependencies. On the
other hand, SVM does not consider such dependencies. The hybrid
approach of both makes use of the strength of each.
1http://wis.ewi.tudelft.nl/umap2011/
2011 Microblog track collection.
+
      </p>
      <p>TREC</p>
    </sec>
    <sec id="sec-7">
      <title>3. EXPERIMENTAL RESULTS</title>
      <p>
        In this section we show our experimental results of the proposed
approaches on the challenge training data [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] in contrast with other
competitors. All our experiments are done through a 4-fold cross
validation approach for training and testing. Table 1 shows the
results of ‘Our Linking Approach’ presented in section 2.2, in
comparison with two modes of operation of AIDA [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. The first mode is
‘AIDA Cocktail’ which makes use of several ingredients: the prior
probability of an entity being mentioned, the similarity between the
context of the mention in the text and an entity, as well as the
coherence among the entities. While the second mode is ‘AIDA Prior’
which makes use only of the prior probability. The results show the
percentage of finding the correct entity of the ground truth
mentions. Table 2 shows the NEE results along the extraction process
phases in contrast with ‘Stanford NER’ [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. Finally, table 3 shows
our final results of both extraction and entity linking in comparison
with our competitor (‘Stanford + AIDA’) where ‘Stanford NER’
is used for NEE and ‘AIDA Cocktail’ is used for NEL.
      </p>
      <p>Table 1: Linking Results</p>
      <sec id="sec-7-1">
        <title>Percentage</title>
      </sec>
      <sec id="sec-7-2">
        <title>Our Linking Approach 70.98%</title>
      </sec>
      <sec id="sec-7-3">
        <title>AIDA Cocktail 56.16%</title>
      </sec>
      <sec id="sec-7-4">
        <title>AIDA Prior 55.63%</title>
      </sec>
      <sec id="sec-7-5">
        <title>Candidates Generation</title>
      </sec>
      <sec id="sec-7-6">
        <title>Candidates Filtering (SVM) CRF</title>
      </sec>
      <sec id="sec-7-7">
        <title>Final Set Generation</title>
      </sec>
      <sec id="sec-7-8">
        <title>Stanford NER</title>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>A. E. Cano</given-names>
            <surname>Basave</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            <surname>Rizzo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Varga</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Rowe</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Stankovic</surname>
          </string-name>
          ,
          <article-title>and</article-title>
          <string-name>
            <given-names>A.-S.</given-names>
            <surname>Dadzie</surname>
          </string-name>
          .
          <article-title>Making Sense of Microposts (#Microposts2014) Named Entity Extraction &amp; Linking Challenge</article-title>
          .
          <source>In Proc., #Microposts2014</source>
          , pages
          <fpage>54</fpage>
          -
          <lpage>60</lpage>
          ,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>J. R.</given-names>
            <surname>Finkel</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Grenager</surname>
          </string-name>
          , and
          <string-name>
            <given-names>C.</given-names>
            <surname>Manning</surname>
          </string-name>
          .
          <article-title>Incorporating non-local information into information extraction systems by gibbs sampling</article-title>
          .
          <source>In Proc. of ACL</source>
          <year>2005</year>
          , pages
          <fpage>363</fpage>
          -
          <lpage>370</lpage>
          ,
          <year>2005</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>M. B.</given-names>
            <surname>Habib and M. van Keulen</surname>
          </string-name>
          .
          <article-title>A generic open world named entity disambiguation approach for tweets</article-title>
          .
          <source>In Proc. of KDIR</source>
          <year>2013</year>
          , pages
          <fpage>267</fpage>
          -
          <lpage>276</lpage>
          ,
          <year>2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>M. B.</given-names>
            <surname>Habib</surname>
          </string-name>
          ,
          <string-name>
            <surname>M. van Keulen</surname>
          </string-name>
          , and
          <string-name>
            <given-names>Z.</given-names>
            <surname>Zhu</surname>
          </string-name>
          . Concept extraction challenge: University of Twente at #MSM2013.
          <source>In Proc., #MSM2013</source>
          , pages
          <fpage>17</fpage>
          -
          <lpage>20</lpage>
          ,
          <year>2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>J.</given-names>
            <surname>Hoffart</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F. M.</given-names>
            <surname>Suchanek</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Berberich</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E. L.</given-names>
            <surname>Kelham</surname>
          </string-name>
          , G. de Melo, and
          <string-name>
            <surname>G. Weikum.</surname>
          </string-name>
          <article-title>Yago2: Exploring and querying world knowledge in time, space, context, and many languages</article-title>
          .
          <source>In Proc. of WWW</source>
          <year>2011</year>
          ,
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>C.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Weng</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Q.</given-names>
            <surname>He</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Yao</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Datta</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Sun</surname>
          </string-name>
          , and
          <string-name>
            <given-names>B.-S.</given-names>
            <surname>Lee</surname>
          </string-name>
          .
          <article-title>Twiner: named entity recognition in targeted twitter stream</article-title>
          .
          <source>In Proc. of SIGIR</source>
          <year>2012</year>
          , pages
          <fpage>721</fpage>
          -
          <lpage>730</lpage>
          ,
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>M. A.</given-names>
            <surname>Yosef</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Hoffart</surname>
          </string-name>
          , I. Bordino,
          <string-name>
            <given-names>M.</given-names>
            <surname>Spaniol</surname>
          </string-name>
          , and
          <string-name>
            <given-names>G.</given-names>
            <surname>Weikum. Aida</surname>
          </string-name>
          :
          <article-title>An online tool for accurate disambiguation of named entities in text and tables</article-title>
          .
          <source>PVLDB</source>
          ,
          <volume>4</volume>
          (
          <issue>12</issue>
          ):
          <fpage>1450</fpage>
          -
          <lpage>1453</lpage>
          ,
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>