<!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>Entity Linking and Knowledge Discovery in Microblogs</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Pikakshi Manchanda</string-name>
          <email>pikakshi.manchanda@disco.unimib.it</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Department of Computer Science</institution>
          ,
          <addr-line>Systems and Communication</addr-line>
          ,
          <institution>Universita di Milano-Bicocca</institution>
          ,
          <addr-line>Milano</addr-line>
          ,
          <country country="IT">Italy</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Social media platforms have become signi cantly popular and are widely used for various customer services and communication. As a result, they experience a real-time emergence of new entities, ranging from product launches to trending mentions of celebrities. On the other hand, a Knowledge Base (KB) is used to represent entities of interest/relevance for general public, however, unlikely to cover all entities appearing on social media. One of the key tasks towards bridging the gap between Web of Unstructured Data and Web of Data is identifying such entities from social media streams which are important and haven't been yet represented in a KB. The main focus of this PhD work is discovery of new knowledge from social media streams in the form of new entities and/or new mentions of existing entities while enriching KBs as well as lexically extending them for existing entities. Based on the discovery of new entities or new mentions, structured data in the form of RDF (Resource Description Framework) can be extracted from the Web.</p>
      </abstract>
      <kwd-group>
        <kwd>Social Media</kwd>
        <kwd>Knowledge Base</kwd>
        <kwd>Web of Data</kwd>
        <kwd>RDF</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>1.1</p>
    </sec>
    <sec id="sec-2">
      <title>Objective of the Research</title>
      <p>Microblogging platforms have become an indispensable resource for users by
providing services such as sales and marketing, news and communication, trend
detection and a variety of customer services. Due to their dynamic nature, they
experience a steady emergence of new knowledge in the form of new entities (such
as product launches), new relations between existing entities (such as a
football player playing for FC Barcelona and Real Madrid ), as well as new/popular
mentions of existing entities (such as trending colloquial names for celebrities).
Knowledge bases provide a broad (yet intrinsically non exhaustive) coverage of
a variety of entities found on the Web and social media streams. However, it
is unlikely that a KB can provide coverage of all new entities that emerge
constantly on the Web. As a result, tasks such as Named Entity Recognition (NER),
Disambiguation (NED) and Linking (NEL) have gained signi cant attention of
NLP practitioners. Named entity recognition is the task of identifying a piece of
text as a named entity and classifying into types such as person, location,
organization etc. whereas a named entity disambiguation task is to disambiguate a
named entity with a resource in a KB and nally link it with the said resource.</p>
      <p>In order to enrich a KB for new/relevant entities emerging on social media in
real-time, it is necessary to identify those entities and gather contextual
information from the Web and social media. The objective of this work is not only
to identify and extract new knowledge, but also being able to use it in order to
enrich and lexically extend KBs. In the process, we will be able to improve the
accuracy of named entity recognition as well as disambiguation tasks.
1.2</p>
    </sec>
    <sec id="sec-3">
      <title>Research Questions</title>
      <p>The proposed research work aims to address the following research questions:
RQ1: Can we perform NER and NEL in microposts as a joint task and link the
named entities to resources in a KB?
RQ2: Is it possible to use the results of an Information Extraction (IE) task to
identify new entities?
RQ3: Can we use an enriched/lexically extended KB to improve the IE process
of new entities from microblogging platforms?
1.3</p>
    </sec>
    <sec id="sec-4">
      <title>Motivation and Relevance</title>
      <p>Signi cant gain in momentum for IE (achieved mainly through NER and
NEL), from news archives, blogs and Web pages, is attributed to need for
bridging the gap between Document Web and Web of Data. The main motivation for
carrying out a research on discovery of new knowledge by means of IE tasks is
primarily because new entities emerge frequently over social media. Another
motivating factor is being able to perform entity recognition and disambiguation on
short textual formats, such as microblogs, as a joint task in an end-to-end entity
linking pipeline. This is also important from the point of view of KB enrichment
and its lexical extension for existing entities.</p>
      <p>KB Enrichment can be performed automatically to some extent (by
identifying a new entity, and collecting contextual information from the Web) or can
even be performed interactively, for instance, driven by social content creation
communities. The output of my research work combined with these techniques
can be used to enrich KBs periodically. Furthermore, a lot of research (Semantic
Search, Recommendation Systems, Disaster Discovery, Sentiment Analysis) is
dependent on entity disambiguation and discovery of new knowledge.
1.4</p>
    </sec>
    <sec id="sec-5">
      <title>Challenges and Opportunities</title>
      <p>
        Challenges: The task of identi cation and disambiguation of entities from
microblogs is challenging due to the following reasons:
{ Short, noisy nature: An informal microblogging style, coupled with use of
Internet slang and misspellings [
        <xref ref-type="bibr" rid="ref4 ref7 ref8">4, 7, 8</xref>
        ] renders it di cult to identify new
entities, a ecting the accuracy of entity recognition and disambiguation.
{ Occurrence of Out Of Vocabulary (OOV) mentions : We de ne an OOV
mention as an existing resource in a KB, being referred by an alternate entity
mention in social media which is not present in KB. As a result, OOV
mentions can't be disambiguated, causing the performance accuracy of an
endto-end entity linking system to su er.
{ Occurrence of Out of Knowledge base (OOKB) entities : We de ne an OOKB
entity as one which is not covered by a KB and, thus, can be considered as
newly emerging.
      </p>
      <p>Opportunities: If we are able to identify an OOV mention, we can lexically
enrich the KB for said existing entity. Similarly, if we are able to detect an OOKB
entity, we can extensionally update the KB for the new entity by collecting
contextual information about it from the Web. On the other hand, by addressing
the above challenges, we will also be able to improve the accuracy of the
endto-end entity linking pipeline.
2</p>
      <sec id="sec-5-1">
        <title>Proposed Approach</title>
        <p>2.1</p>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>Formal De nition and Properties of the Approach</title>
      <p>Given a tweet t, the goal of the system is to identify named entities in t.
Further, the system maps every identi ed entity e to a referent resource r in
knowledge base K. More formally, we de ne a Named Entity Recognition task
as a function which identi es and maps a set of words W in tweet t to a tuple
of entity name, ei, and a corresponding entity type, typeei , i.e.,
fNER : W
!&lt; eit; typetei &gt;
(1)
Next, we de ne a universe U consisting of entities present in
unstructured/semistructured data on social media and the Web as well as resources covered by KBs.
Further, we de ne a Named Entity Linking task as a function which maps an
identi ed entity eit, as in equation (1), to a resource rj in K, i.e.,
fNEL : eit ! rj</p>
      <p>K
(2)
Here every resource rj in K can be associated with one or more resource types
and is represented as crj . fNEL is de ned for entities which are covered by
resources in K. OOV mentions also have referent resources in K, however, the
said mention has been referred in social media by an alternate name while K
isn't lexically updated to provide coverage for it. It is to note here, that OOV
mention, its original entity as well as the corresponding resource are present
in U, however, fNEL is unable to link the OOV mention to the corresponding
resource. On the other hand, OOKB entities are new entities, present in U, which
have not yet been covered by K and so fNEL is unable to link them as well.
2.2</p>
    </sec>
    <sec id="sec-7">
      <title>Relationship between your approach and state-of-art approaches</title>
      <p>
        Various existing approaches [
        <xref ref-type="bibr" rid="ref1 ref5 ref9">1, 5, 9</xref>
        ] as well as a variety of commercial tools,
such as Zemanta1, Alchemy API2, and DBpedia Spotlight3 are used for entity
recognition in text. However, these conventional tools perform poorly on short
textual data [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], mainly due to lack of context and informal language. [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] propose
a tweet-based NLP framework for entity recognition in tweets using a CRF model
with the help of contextual, dictionary and orthographic features. In [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], Liu et
al. (2011) propose an entity recognition framework using K-Nearest Neighbour
(KNN) Classi er with a linear CRF Model.
      </p>
      <p>
        State-of-the-art approaches provide a variety of methods for entity
disambiguation. However, few existing approaches target the detection of new entities
using existing knowledge provided by KBs. Liu et al (2013) use similarity
measures to detect OOV mentions of existing entities [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], however, OOKB entities
are not dealt with. [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] propose an end-to-end tweet-level identi cation and
disambiguation system while using structural learning techniques to jointly optimize
identi cation as well as disambiguation. However, their approach is not able
to recognize or deal with OOKB entities. An approach for discovery of
emerging OOKB entities with ambiguous names from documents has been proposed
in [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. This work is, in principle, a foundation for our research work, however,
their approach doesn't consider the entities emerging in social media streams.
      </p>
      <p>Based on the literature review, we observe that most state-of-the-art systems
treat entity identi cation and disambiguation as separate tasks. In this research
work, we propose an end-to-end entity linking pipeline where we study entity
recognition and disambiguation as a joint problem for microposts. To the best
of our knowledge, our work provides a novel contribution, in the sense, that we
not only aim to improve the disambiguation of entities using linked datasets, but
also we address the task of discovery of new entities from tweets, thus improving
the overall accuracy of the system. We distinguish between OOV mentions and
OOKB entities and also propose distinctive measures to deal with both types of
entities. We use the discovered information for KB enrichment.
3
3.1</p>
      <sec id="sec-7-1">
        <title>Implementation of the Proposed Approach</title>
      </sec>
    </sec>
    <sec id="sec-8">
      <title>The Big Picture and Current Implementation</title>
      <p>
        In this section, we present a brief overview of the system, as shown in Fig. 1.
The system performs tweet-wise evaluation using Ritter et al's (2011)
state-ofthe-art T-NER system [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] for entity recognition and classi cation. Further, for
NED, we have constructed an inverted index of the data property rdfs:label
from DBpedia4 which we currently consider for disambiguation and knowledge
discovery.
1 http://www.zemanta.com/
2 http://www.alchemyapi.com/
3 http://dbpedia.org/spotlight/
4 http://wiki.dbpedia.org/
      </p>
      <p>For every identi ed entity in a tweet, an ad-hoc index lookup is performed
to obtain a list of candidate resources which we rank using a high-recall lookup
approach. We use contextual and orthographic features, identi ed entity-type,
as well as tweet-speci c features such as use of @usernames, #hashtags and
URLs which aid in disambiguation amongst the candidate resources. This is
accomplished using a probabilistic matching function, being presented in this
work, which takes into consideration the following factors:
1. Lexical Similarity between an entity in a tweet and candidate resource
2. Coherence between an entity and (structured) document page of candidate
resource in KB
3. Relatedness between entities in a tweet, in case where there is more than
one entity in a tweet</p>
      <p>Currently, we have implemented measures to calculate similarity between
entity in a tweet and candidate resources, as well as relatedness between entities
(from KB perspective, i.e., how frequently entities mentioned in a tweet co-occur
in a KB). In the future, we plan to take into consideration the relatedness
between entities from real-world perspective.</p>
      <p>The probabilistic matching function helps to disambiguate named entities with
resources in KB. Subsequently, we will obtain a pool consisting of entities which
can't be disambiguated. This pool will consist of OOV mentions, OOKB entities
as well as noise (text wrongly identi ed as an entity). Information, such as usage
patterns, frequency of usage, as well as contextual patterns from social media
streams and the Web, will be collected for entities in pool. This information can
be used to enrich a KB, either automatically or manually by content creation
communities, with the help of which disambiguation is performed again to
improve the overall accuracy of disambiguation process of the proposed system.</p>
      <sec id="sec-8-1">
        <title>Empirical Evaluation Methodology</title>
      </sec>
    </sec>
    <sec id="sec-9">
      <title>General Strategy</title>
      <p>The research questions described above are related to a few hypotheses:
H1: If an entity is a word that appears in the lexicon of a resource, the system
links it with the resource with a certain degree of accuracy. For this, we use entity
information from tweet and resource in KB. In order to accomplish this task,
we perform NER and NEL jointly (explained in detail in section 4.2). A NER
system exhibits segmentation errors (such as St. Mary's identi ed as 2 distinct
entities), identi cation erros (such as justten being identi ed as an entity) and
classi cation errors (such as Hawaii being identi ed as Person). We use Ritter
et al.'s (2011) gold standard corpus of 2400 tweets for NER. Additionally, we
created a manually annotated gold standard collection of named entities for NEL
from gold standard corpus used for NER.</p>
      <p>H2: If there is a pool of unknown entities, we collect additional knowledge,
from the Web and social media, in order to classify them as new (OOKB)
entities or use that knowledge to resolve (OOV) entity mentions and link them
with resources in KB. A gold standard corpus of such unknown entities needs
to be created for this step. We can also use the pool of entities from NEL's gold
standard which aren't disambiguated. We plan to expand this gold standard in
the future.
4.2</p>
    </sec>
    <sec id="sec-10">
      <title>Current State of the Evaluation</title>
      <p>In this section, we present the evaluation results achieved so far for hypotheses
H1. We plan to start creating a gold standard for H2 by December 2015.</p>
    </sec>
    <sec id="sec-11">
      <title>H1-Task1: Entity Recognition (Experimental Analysis of T-NER)</title>
      <p>Using Ritter et al.'s (2011) gold standard corpus of 2400 tweets, T-NER
identies a total of 1496 named entities classi ed into 10 distinct entity types (person,
location, organization,..), in contrast to 1612 named entities as found in the
ground truth. T-NER exhibits an identi cation error rate of 9.62%, whereas
segmentation error rate is negligible. We summarize the classi cation error rate
of every entity type in Table 1 below. As is evident, the classi cation error rate
is quite high for entity types Movie and Band. A signi cant reason for this could
be attributed to out-of-date knowledge utilized by T-NER for entity recognition.</p>
    </sec>
    <sec id="sec-12">
      <title>H1-Task2: Entity Disambiguation (Experimental Analysis of Lexical</title>
    </sec>
    <sec id="sec-13">
      <title>Similarity Measure and Relatedness)</title>
      <p>In this step, we use the set of named entities identi ed in Task 1 and based
on an ad-hoc candidate match retrieval approach, we obtain candidate resources
for these named entities from our index of rdfs:label. A manually annotated gold
standard of 1455 named entities is created out of 1496 entities that were
identied in Task 1 to aid in candidate match retrieval. The remaining entities serve
as a pool of unknown entities and need to be further expanded in order to be
used as a gold standard for Task 3 described below. We have experimented with
varying forms of entity representations (only entity mention, entity mention with
its entity type, and a combination of entity mentions) in order to obtain su
cient number of candidate matches for each named entity. Table 2 summarizes
the precision-recall for varying entity representations.</p>
      <p>The rst representation produces a list of candidate resources (highest
precision) for disambiguation. Second representation produces a list with the highest
recall (fetching noisy results as well), however, there is a decrease in precision.
The reason for such an output can be due to knowledge gaps in KB for speci c
entity types (thus, a justi ed need for KB enrichment). The third representation
is for tweets which have more than one entity. This representation exhibits the
lowest precision as well as recall amongst all three. This can be due to infrequent
occurrence of various entities together in social media, thus making it di cult
to nd su cient evidences of their co-existence in a KB.</p>
      <p>
        We implement a lexical similarity measure using Lucene's Vector Space Model
of Information Retrieval to estimate similarity between an entity and a candidate
resource so as to choose the most suitable resource for an entity. We have also
used a relatedness measure in order to estimate co-occurrence frequency between
two entities in a tweet, using a method described in [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. Currently, we have
implemented this measure from KB perspective, i.e., how often entities in a
tweet can co-occur in a KB.
      </p>
      <p>We found a total of 399 tweets in Ritter et al's dataset which have more
than one entity. A high relatedness score depicts presence of a strong evidence
in the KB that said entities co-occur frequently. Use of relatedness measure is
attributed towards the need of improving the accuracy of disambiguation for
infrequent/long-tail entities found in social media streams. Another signi cant
reason for the use of this measure is in identifying an OOV entity mention.</p>
    </sec>
    <sec id="sec-14">
      <title>H2-Task3: OOV Mention/OOKB Entity discovery</title>
      <p>Discovery of OOV mentions as well as OOKB entities depends to a great extent
on the performance accuracy of entity recognition as well as disambiguation.
Herein, we propose to improve entity recognition by improving entity
disambiguation, which is currently under progress. In order to achieve this, we use
features (contextual information, evidences from KB, relatedness of an entity
with other real-world entities) for entity recognition that are conventionally
being used for entity disambiguation in the state-of-the-art. By improving entity
recognition, the overall accuracy of the system will be improved.</p>
      <sec id="sec-14-1">
        <title>5 Lessons Learned, Open Issues, and Future Directions</title>
        <p>It is essential to discover new entities for the enrichment of KBs. However, one
of the important lessons that we have learned is that, not every entity that has
been discovered can be updated in a KB. Its authenticity needs to be veri ed as
well as its relation and relevance w.r.t other entities in the real world has to be
taken into consideration to update concepts in KBs.</p>
        <p>Enrichment of KBs, speci cally enriching the lexicon of an entity in a KB
using information extracted from social media is one of the most important
open issues in the Semantic Web community. As of now, we have conducted
a variety of experiments for improving disambiguation. While we continue to
improve it, the next step in this research work is working towards enrichment of
KBs in time and extending them with quality information extracted from Social
Media and the Web.</p>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Derczynski</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Maynard</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rizzo</surname>
            , G., van Erp,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gorrell</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Troncy</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Petrak</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Bontcheva</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          <article-title>Analysis of named entity recognition and linking for tweets</article-title>
          .
          <source>Information Processing &amp; Management</source>
          (
          <year>2015</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Guo</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chang</surname>
          </string-name>
          , M.-W., and
          <string-name>
            <surname>Kiciman</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          <article-title>To link or not to link? a study on end-to-end tweet entity linking</article-title>
          .
          <source>In HLT-NAACL</source>
          (
          <year>2013</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Hoffart</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Altun</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Weikum</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          <article-title>Discovering emerging entities with ambiguous names</article-title>
          .
          <source>In Proceedings of Conference on WWW</source>
          (
          <year>2014</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Liu</surname>
            ,
            <given-names>X.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Li</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wu</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zhou</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wei</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Lu</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          <article-title>Entity linking for tweets</article-title>
          .
          <source>In ACL (1)</source>
          (
          <year>2013</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Liu</surname>
            ,
            <given-names>X.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zhang</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wei</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Zhou</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <article-title>Recognizing named entities in tweets</article-title>
          .
          <source>In Proceedings of ACL: Human Language Technologies</source>
          (
          <year>2011</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Medelyan</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Witten</surname>
            ,
            <given-names>I. H.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Milne</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          <article-title>Topic indexing with wikipedia</article-title>
          .
          <source>In Proceedings of AAAI WikiAI workshop</source>
          (
          <year>2008</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Meij</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Weerkamp</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          , and de Rijke,
          <string-name>
            <surname>M.</surname>
          </string-name>
          <article-title>Adding semantics to microblog posts</article-title>
          .
          <source>In Proceedings of the fth ACM international conference on Web search and data mining</source>
          (
          <year>2012</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Ritter</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Clark</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Etzioni</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          , et al.
          <article-title>Named entity recognition in tweets: an experimental study</article-title>
          .
          <source>In Proceedings of the Conference on EMNLP</source>
          (
          <year>2011</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Usbeck</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <given-names>Ngonga</given-names>
            <surname>Ngomo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.-C.</given-names>
            ,
            <surname>Luo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            , and
            <surname>Wesemann</surname>
          </string-name>
          ,
          <string-name>
            <surname>L.</surname>
          </string-name>
          <article-title>Multilingual disambiguation of named entities using linked data</article-title>
          .
          <source>In International Semantic Web Conference</source>
          (
          <year>2014</year>
          ).
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>