<!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>Unsupervised Resource-Free Entity Discovery and Linking in Natural Language Questions</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Shu Guo</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Jiangxia Cao</string-name>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Quan Wang</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Lihong Wang</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Bin Wang</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Institute of Information Engineering, Chinese Academy of Sciences</institution>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>National Computer Network Emergency Response Technical Team Coordination Center of China</institution>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>School of Computer Scince &amp; Technology, Heilongjiang University</institution>
        </aff>
        <aff id="aff3">
          <label>3</label>
          <institution>School of Cyber Security, University of Chinese Academy of Sciences</institution>
        </aff>
      </contrib-group>
      <abstract>
        <p>We present the solution to the CCKS 2017 question entity discovery and linking (QEDL) task. This task is to discover and link entity mentions in natural language questions with their referent entities in a knowledge base (KB). For entity discovery, we devise recognition patterns based on word segmentation and POS tagging. For entity linking, we leverage contextual similarity refined by rich side information contained in the KB. Our solution is fully unsupervised and resource-free, requiring neither labeled data nor auxiliary resources. Experimental results show that our solution is simple yet effective, achieving an F1-score of 44.3% which ranks the third in the QEDL task.</p>
      </abstract>
      <kwd-group>
        <kwd>Entity discovery</kwd>
        <kwd>entity linking</kwd>
        <kwd>natural language questions</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        The CCKS 2017 question entity discovery and linking (QEDL) task1 is to
recognize entity mentions from natural language questions, and link them with their
referent entities in a given knowledge base (KB), i.e., CN-DBpedia [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. For
example, given a question “吴晓敏演过什么电视剧?/What TV shows did Xiaomin Wu
play in?”, we should recognize the mention “吴晓敏/Xiaomin Wu” and link it to
its referent entity “吴晓敏(演员)/Xiaomin Wu (actress)” in the KB. Such linking
results are extremely useful for answering these questions [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ].
      </p>
      <p>
        Entity discovery and linking has long been regarded as a challenging task in
natural language processing (NLP) [
        <xref ref-type="bibr" rid="ref3 ref4">3, 4</xref>
        ]. The specific scenario of CCKS 2017
QEDL further poses new challenges to this traditional NLP task.
{ Entities are no longer restricted to the three classical types of person,
location, and organization, but instead could be more generic, e.g., “手指/finger”
and “发型/hairstyle”. Most of the currently available well-performing
systems (usually trained from massive labeled data) can only recognize entities
of the three classical types, and hence fail to work here.
{ Questions are too short, containing 13 Chinese characters on average, which
cannot provide sufficient contextual information for entity linking.
{ Only a small number of training instances are provided, i.e., 1,400
questions with 1,980 entities manually annotated, some of which might even be
mislabeled. For instance, in the question “像我这脸型适合剪什么发型?/What
hairstyle fits my facial shape?”, “发型/hairstyle” is labeled as an entity
while “脸型/facial shape” is not, although both of them have redirects in
CN-DBpedia. This limited (and potentially inconsistent) supervision makes
it difficult to train supervised models for both entity discovery and linking.
      </p>
      <p>To address these challenges, we devise a fully unsupervised method for QEDL.
In our approach, entity discovery is conducted based solely on the results of word
segmentation and POS tagging. Entity linking is performed by measuring
contextual similarity between entity mentions and their referent in the KB. As
questions are short with insufficient contexts, we further leverage side information,
e.g., titles, types, and primary tags of entities, to refine contextual similarity.
Our approach is fully unsupervised and resource-free, requiring neither labeled
training data nor auxiliary resources like hand-crafted dictionaries or thesauri.
Our approach is simple yet effective, achieving an F1-score of 44.3% which ranks
the third in the CCKS 2017 QEDL task.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Related Work</title>
      <p>
        Entity discovery is closely related to named entity recognition (NER) which
recognizes entities of specific types (person, location, and organization). Studies
on NER roughly fall into three categories: 1) rule-based methods which use
handcrafted rules and dictionaries to design recognition patterns; 2) machine
learningbased methods which pose NER as a sequence classification problem, solved by
hidden Markov models or conditional random fields; 3) hybrid methods which
combine rule-based and machine learning-based approaches. For more details
about NER methods, please refer to [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ].
      </p>
      <p>
        Entity linking is to link textual mentions with their referent entities in a
given knowledge base. Existing approaches can be roughly categorized into two
groups: 1) supervised methods which rely on massive annotated data to learn
how to rank candidate entities for each textual mention; 2) unsupervised methods
which do not require any annotated data to train the ranking model. See [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] for
a thorough review of entity linking techniques.
      </p>
      <p>Given that only a small number of annotated data is provided in the QEDL
task, we employ a rule-based method for entity discovery, and an unsupervised
method for entity linking.
3</p>
    </sec>
    <sec id="sec-3">
      <title>Our Approach</title>
      <p>Entity Discovery
• Recognition patterns
− Word segmentation
− POS tagging</p>
      <p>Mention: 吴教</p>
      <p>Entity Linking
• Contextual similarity
• Side information
− Entity titles
− Entity types
− Entity primary tags</p>
      <p>Candidate Entities
吴教
Xiaomin Wu (professor)
Xiaomin Wu (actress)
吴市
Xiaomin Wu (mayor)
word segmentation and POS tagging. Entity linking is then performed by
measuring contextual similarity between textual mentions and their referent entities,
refined by rich side information in the KB. Our approach is fully unsupervised
and resource-free, requiring neither labeled training data nor auxiliary resources.
3.1</p>
      <p>Entity Discovery
Given an input natural language question, we employ the SWJTU Chinese word
segmentation system to perform word segmentation and POS tagging. This
system supports two segmentation manners, i.e., coarse-grained and fine-grained
segmentations. The former uses a longest matching algorithm, and the latter
can split the words into smaller units. For example, “新浪微博/Sina Microblog”
is segmented into a single word “新浪微博/nt” in coarse-grained segmentation,
but two separate words “[新浪/ntc 微博/n]/nt” in fine-grained segmentation.
Here, “nt”, “ntc”, and “n” are POS tags.2 After word segmentation and POS
tagging, we detect entity mentions as follows (see Table 1 for concrete examples).
Rule 1 Words with coarse-grained POS tags of nr (person name), ns (place),
and nt (organization) are recognized as entity mentions, e.g., “霍建华”, “宁
波”, and “普陀山”.</p>
      <p>Rule 2 Words with coarse-grained POS tags of nz (proper noun) and n (noun)
are recognized as entity mentions if they have redirects in the KB, e.g., “湘潭
火车站”. Otherwise, any fine-grained units therein that have redirects are
determined as entity mentions, e.g., “中国” in the coarse-grained segmentation
“[中国/ns 领土/n]/nz”.</p>
      <p>Rule 3 Words with coarse-grained POS tags of nz (proper noun) can further
be concatenated with their antecedent or succedent words. If the combined
words have redirects in CN-DBpedia, they are also identified as entity
mentions, e.g., “qq木马病毒” and “三星note2”.
2 They stand for organization, company name, and noun, respectively. A full
description of POS tags is available at http://ics.swjtu.edu.cn.
霍建华/nr 演/v 过/uguo 哪些/ry 电视剧/n
从/p 宁波/ns 到/v 普陀山/ns 怎么走/nz 最/d 方便/a
[湘潭/ns 火车站/n]/nz 什么/ry 时候/n 通车/vi
求/v 钓鱼岛/ns 属/v [中国/ns 领土/n]/nz 的/ude 资料/n
qq/x [木马/n 病毒/n]/nz 怎么/ryv 编写/v
三星/nz note2/x 电池/n 怎么样/ryv
Entity mentions
霍建华
宁波, 普陀山
湘潭火车站
中国, 钓鱼岛
qq木马病毒
三星note2
3.2</p>
      <p>Entity Linking
Entity linking consists of three modules: candidate entity selection, candidate
entity ranking, and NIL (unlinkable entities) detection, detailed as follows.
Candidate entity selection. For each recognized mention, we query it directly
in the CN-DBpedia search engine3 and retrieve a list of relevant entities. These
entities are taken as candidates for that mention.</p>
      <p>Candidate entity ranking. We rank candidates for each mention by measuring
their contextual similarity. Specifically, given a mention m and a candidate entity
e, we construct two feature vectors m and e for them. The former is composed
of context words of the mention in the question, and the latter context words
of the entity in its abstract. Here only words that are tagged as noun and verb
are considered. The contextual similarity between m and e can be calculated as,
e.g., the dot product of m and e, i.e., s(m; e) = ⟨m; e⟩. However, since both the
question and the entity abstract are short, we might not get enough contextual
information in m and e. So we propose to further use side information in
CNDBpedia, and calculate a refined contextual similarity s˜(m; e) = w × s(m; e).
Candidate with the largest s˜(m; e) score will be selected as the true referent.
Three types of side information are considered to calculate the refining factor w,
including entity title, entity type, and primary tag.</p>
      <p>Entity title is the title of an entity page in CN-DBpedia. The intuition here is
that referent entities are usually those that have similar titles with their mentions
(string matching). For example, given the mention “格林豪泰”, the entity “格林豪
泰” is more likely to be the true referent than “林豪泰”. So we define the refining
factor as string similarity between the mention m and entity title e, i.e.,
edit(m; e)
w1 = 1 − max(|m|; |e|) ;
where | · | is the length of a string, and edit(·; ·) the edit distance.</p>
      <p>Entity type is the category to which an entity belongs, denoted as type(e).
Usually, a mention can only be linked to entities of certain types, e.g., China/ns
should be linked to countries. So we specify a type set T for each POS tag, e.g.,
3 http://knowledgeworks.cn:30001/?p=**
http://knowledgeworks.cn:20313/cndbpedia/api/entity?mention=**
T = {Place; Country; City} for ns (space), and define the refining factor as
1;
</p>
      <p>type(e) ∈ T ;
1; type(e) = ∅;
 2; type(e) ̸∈ T and type(e) ̸= ∅;
where 0 ≤ 2 &lt; 1 &lt; 1. Here we specify type sets for only three POS tags, i.e.,
nr (person name), ns (space), and nt (organization).</p>
      <p>Primary tags indicate the most popular entities of the given mentions.
Candidates with primary tags are more likely to be the true referent. So we define
the refining factor according to the presence or absence of primary tags, i.e.,
where is a parameter in the range of [0; 1). These three weights can further be
aggregated together, giving a combined refining factor. For example, aggregating
all the three weights gives a combined refining factor of w = w1 × w2 × w3.
NIL detection. Not all mentions have referent entities in the KB. To detect
such unlinkable mentions, we use a simple heuristic: mentions with no candidates
after performing the candidate entity selection module are predicted to be NIL.
To yield more accurate NIL, we do this only for mentions discovered by Rule 1.
4</p>
    </sec>
    <sec id="sec-4">
      <title>Experiments</title>
      <p>
        Datasets and evaluation metrics. The training set consists of 1,400
questions with 1,917 mentions manually linked with their referent entities, and 63
mentions labeled as NIL. The test set consists of 749 unlabeled questions. As
our approach is fully unsupervised, we use the training data as a development
set only for parameter tuning. Submissions are finally evaluated on the test set.
Three metrics Precision, Recall, and F1-score are used for the QEDL task.
Implementation details. We use Rule 1, Rule 2, and Rule 3 to detect entity
mentions (Section 3.1). And for entity linking (Section 3.2), we test different
settings. In the calculation of contextual similarity, we use different term weighting
schemes including Boolean, TF, and TF-IDF [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] to compute feature vectors, and
we explore two similarity measures, i.e., cosine similarity (Cos) and dot product
(Dot). In the calculation of refining factor, we apply each of the three types of
side information (Title, Type, and Tag) alone, and get a refining factor of w1, w2,
and w3, respectively. We also test all possible combinations, e.g., Title+Type,
and get a refining factor of, e.g., w1 × w2. Due to the space limitation, we only
report the combination with the highest entity linking F1-score on the training
set, i.e., Title+Tag which gives a refining factor of w1 ×w3. All parameters in our
approach are determined by maximizing entity linking F1-score on the training
set. The optimal configurations are: 1 = 0:8, 2 = 0:75, and = 0:3.
Results. Results of entity discovery and linking are shown in Table 2. For
discovery, we can see that the recognition rules are simple yet effective in recognizing
Boolean (Cos)
      </p>
      <p>Boolean (Dot)
g TF (Cos)
ikn TF (Dot)
i TF-IDF (Cos)
n
L
y TF-IDF (Dot)
ittn TF (Dot)+Title
E TF (Dot)+Type</p>
      <p>TF (Dot)+Tag
TF (Dot)+Title+Tag
most entity mentions in short questions. However, the rules we created may
still miss some difficult cases such as “红/a 米/n note2/x”, which will be
studied in our future work. For linking, we can see that: 1) the TF term weighting
scheme combined with the dot product similarity measure performs the best in
calculating contextual similarity; 2) incorporating each of the three types of side
information alone can further improve contextual matching; 3) among all
possible combinations of side information, Title+Type performs the best, achieving
an F1-score of 44.3% on the test set;4 4) the performance on the test set is better
than that on the training set, which might indicate higher annotation quality of
the test data.</p>
    </sec>
    <sec id="sec-5">
      <title>Conclusion</title>
      <p>This paper introduces our solution to the CCKS 2017 QEDL task. We first devise
recognition patterns based on word segmentation and POS tagging to discover
mentions. Then, we utilize contextual similarity refined by rich side
information for entity linking. Our solution is simple yet effective for short questions,
achieving an F1-score of 44.3% which ranks the third in the QEDL task.
4 During the test phase, we refine the outputs using labeled data in the training set.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <given-names>B.</given-names>
            <surname>Xu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Xu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Liang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Xie</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Liang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Cui</surname>
          </string-name>
          ,
          <string-name>
            <surname>Y.</surname>
          </string-name>
          <article-title>Xiao: CN-DBpedia: A Never-Ending Chinese Knowledge Extraction</article-title>
          .
          <source>In: Proceedings of IEA/AIE</source>
          , pp.
          <fpage>428</fpage>
          -
          <lpage>438</lpage>
          (
          <year>2017</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <given-names>C.</given-names>
            <surname>Welty</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. W.</given-names>
            <surname>Murdock</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Kalyanpur</surname>
          </string-name>
          ,
          <string-name>
            <surname>J.</surname>
          </string-name>
          <article-title>Fan: A comparison of hard filters and soft evidence for answer typing in watson</article-title>
          .
          <source>In: Proceedings of ISWC</source>
          , pp.
          <fpage>243</fpage>
          -
          <lpage>256</lpage>
          (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <given-names>A.</given-names>
            <surname>Mansouri</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L. S.</given-names>
            <surname>Affendy</surname>
          </string-name>
          ,
          <string-name>
            <surname>A.</surname>
          </string-name>
          <article-title>Mamat: Named Entity Recognition Approaches</article-title>
          .
          <source>IJCSNS</source>
          , vol.
          <volume>8</volume>
          , no.
          <issue>2</issue>
          , pp.
          <fpage>339</fpage>
          -
          <lpage>344</lpage>
          ,
          <year>2008</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <given-names>W.</given-names>
            <surname>Shen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Wang</surname>
          </string-name>
          , J. Han:
          <article-title>Entity Linking with a Knowledge Base: Issues, Techniques, and Solutions</article-title>
          . IEEE
          <source>T KNOWL DATA EN</source>
          ,
          <volume>27</volume>
          (
          <issue>2</issue>
          ), pp.
          <fpage>443</fpage>
          -
          <lpage>460</lpage>
          (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <given-names>G.</given-names>
            <surname>Salton</surname>
          </string-name>
          and
          <string-name>
            <given-names>C.</given-names>
            <surname>Buckley</surname>
          </string-name>
          .
          <article-title>Term Weighting Approaches in Automatic Text Retrieval</article-title>
          .
          <source>INF PROCESS MANAGE</source>
          ,
          <volume>24</volume>
          (
          <issue>5</issue>
          ), pp.
          <fpage>513</fpage>
          -
          <lpage>523</lpage>
          (
          <year>1988</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>