<!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>Vira@FIRE 2015: Entity Extraction from Social Media Text Indian Languages (ESM-IL)</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Vira Bagiya</string-name>
          <email>virabagiya11@gmail.com</email>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Anjana Patel</string-name>
          <email>14pgce002@charusat.edu.in</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Amit Ganatra</string-name>
          <email>amitganatra.ce@charusat.ac.in</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Charotar University of Science &amp;, Technology</institution>
          ,
          <addr-line>Changa, Gujarat</addr-line>
          ,
          <country country="IN">India</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Charotar University of Science &amp;, Technology</institution>
          ,
          <addr-line>Changa, Gujarat</addr-line>
          ,
          <country country="IN">India.</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Charotar University of Science &amp;, Technology</institution>
          ,
          <addr-line>Changa,Gujarat</addr-line>
          ,
          <country country="IN">India</country>
        </aff>
      </contrib-group>
      <fpage>107</fpage>
      <lpage>110</lpage>
      <abstract>
        <p>In this paper we have tried to identify and extract “Named Entities” from social media text using conditional random field(CRF) [3]. The paper represents our working methodology and result on Entity Extraction from Social Media Text Indian Languages task of FIRE-2015. We have extracted named entities from two languages Hindi and English. Named Entity Extraction system is implemented based on CRFSuite. CRFSuite [8] is the populer implementation of Conditional Random Fields (CRF). This is a sequential labelling task to achieve the desired tagging output. Conditional random fields (CRF) are a class of statistical modelling method often applied in pattern recognition, machine learning and many natural language processing tasks. We get F1-score of 19.82 and 3.72 for the Hindi and English text respectively.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>Named-entity recognition (NER) (also known as entity
identification, entity chunking and entity extraction) is a subtask
of information extraction that seeks to locate and classify
elements in text into pre-defined categories such as the names of
persons, organizations, locations, expressions of times, quantities,
monetary values, percentages, etc.</p>
      <p>Social Media is vast source of information- from which we can
extract lots of important data as per the specified requirements.
According to the 8th schedule, India is known to have 22 official
Indian languages. NER in Indian languages is still considered to
be a budding topic of research in the field of NLP and much of
work is needed to be performed in this regard. For English and
Hindi languages there are so many NER tagger exists and hence
this paper propose a CRF based NER tagger using CRFsuite
(Okazaki, 2007) [8]. CRFsuite is an implementation of CRF and it
is faster than CRF++ [7]. CRFsuite is an open source software
which automatically extract features from the learning.</p>
      <p>The paper is organized as follows. Section 2 gives an overview of
Task description and approaches applied for NER task and
complete description of our system. Furthermore section 3
describes the different issues in development of the system for
different Indian languages. In section 4 there is the test result and
how its accuracy can be increased. Finally section 5 concludes the
paper.
1.1</p>
    </sec>
    <sec id="sec-2">
      <title>Task Description</title>
      <p>“Entity extraction from social media text in Indian Languages” is
a task in which we have provided different tweets. --From this
tweets – our work is to annotate and classify these tweets into
different named entity tags like Person, Organization, Location,
Entertainment etc. In training dataset we have given three
columns tweet_id, user_id and tweet_text and in its processed
annotated dataset we have given tweet_id, user_id, Named Entity
tag(NE tag), Named Entity, index and its length. The Same thing
we should perform on the testing dataset provided. Our main task
is to identify named entity from testing dataset and apply
appropriate tag to it.</p>
    </sec>
    <sec id="sec-3">
      <title>1.2 System Architecture</title>
      <p>Our Named entity recognition system is developed to classify and
tagged named entities into 22 different classes such as Person,
Location, Organization, Entertainment etc. We have provided
training dataset which is mainly used for learning process.
There are following unique 22 named entity tags.
1.
2.
3.
4.
5.
6.
7.
8.
9.</p>
      <sec id="sec-3-1">
        <title>PERSON</title>
      </sec>
      <sec id="sec-3-2">
        <title>ORGANIZATION</title>
      </sec>
      <sec id="sec-3-3">
        <title>LOCATION</title>
      </sec>
      <sec id="sec-3-4">
        <title>ENTERTAINMENT DAY</title>
      </sec>
      <sec id="sec-3-5">
        <title>MATERIALS</title>
      </sec>
      <sec id="sec-3-6">
        <title>PLANTS</title>
      </sec>
      <sec id="sec-3-7">
        <title>PERIOD</title>
        <p>LOCOMOTIVE
10. YEAR
11. MONEY
12. COUNT
13. FESTIVAL
15. QUANTITY
16. FACILITIES
17. DISEASE
18. ARTIFACT
19. MONTH
20. TIME
21. LIVTHINGS
22. SDAY
We have used the supervised learning, as we are given training
dataset. We used this training dataset to train our system for
tagging named entities and kept these tags in a space separated
files. CRFsuite generate the model based on training – learning
provided. Later on, system uses these model for generate output
(named entity tagging). The training dataset is primary focus for
our training. Figure 1 - flow-chart is showing the basic flow of our
system in detail.</p>
        <p>As we have used CRFsuite to implement our NER system. In
which features can be easily extracted for labeling entities based
on the provided training datasets. Hence We can easily add our
own features by modifying some line of codes as it is an open
source software. Features can be generated for unigram as well as
bigrams.</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>2. APPROACHES FOR NER</title>
      <p>There are basically two approaches that are employed in Named
Entity Recognition. These include:
a. Rule Based Approach
b. Machine Learning Based Approach
In rule based approach there are Handcrafted or automatically
generated rules or patterns. Machine learning techniques are used
for statistical modeling which can be either unsupervised,
semisupervised or supervised mode of learning. Unsupervised and
semi-supervised mode of learning are used when there is a
scarcity of annotated data for training but the best performance is
obtained by using supervised mode of learning which requires a
large amount of good quality annotated corpus.</p>
      <p>
        We have used machine learning based approach. This approach
is also known as automated approach or statistical approach.
Machine learning based approach is more efficiently and
frequently used as compared to the Rule based approach.
We have developed a system to perform NER in English and
Hindi and submitted the same. We use the open-source
software, CRFsuite[8] which is one of the popular
implementations of Conditional Random Fields (CRF)[
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] for
training a model based on the training dataset and then use the
model to generate tags for the test dataset.
      </p>
    </sec>
    <sec id="sec-5">
      <title>2.1 Extracted features from learning</title>
      <p>For English and Hindi languages there are following
features extracted from learning
CRFsuite automatically extract some features from learning.
Other features are added for tagging different different named
entities.</p>
      <p>


</p>
      <p>Gazetter(specified as list-look up table): Gazetter of
location names has been created and applied to identify
different locations in India. Same as - Plant names,
Festival names, Entertainment , Locomaotives ,
Livthings tagged using the different different gazetters
as a feature.</p>
      <p>Suffixes: In hindi person name identified using suffix
“जी”.Means word ending with “ji” can be the person
name and it can be specified as the feature.
for example:</p>
      <sec id="sec-5-1">
        <title>Modiji is a person name</title>
        <p>If a word followed by “ko” then this word can be
specified as the person name for eample:
“Gita ko haridwar jana hain” – ‘Gita’ is aperson name
which is followed by ‘ko’.</p>
        <p>Prefixes :There are so many prefixes can be used to
identify named entities. For example, Named entity
followed by Mr. or Miss or Mrs would be a person
name
Word Context: Context of the word of window size
four is used which takes two words before and two
words after the word as feature. This helps modeling
the language structure about how where and with which
words entities are used in a sentence. There are total
seven feature values for word context which includes
the word itself, two words before it, and two words
after it, and pairing of word with its previous and next
word.</p>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>2.2 Pre-processing</title>
      <p>
        Social media text is noisy in nature. People use shorthand and
ungrammatical text for saving their time. Thus capitalization is
not properly applied as well as Spellings are not correct. This data
becomes hard to handle in the aspect of Information-extraction.
First from the given testing dataset we have removed all the links
presented in the tweets. Then tokenizing, Part-of-speech tagging
and chunking is done. For English language we have used
Stanford Part-Of-Speech tagger [
        <xref ref-type="bibr" rid="ref4">5</xref>
        ]. For Hindi language we have
used RDRPostagger [6].
      </p>
      <sec id="sec-6-1">
        <title>Input for CRFsuite(NER Tagger):</title>
        <p>As there is space separated 4 fields input to the CRFsuite, we have
combined output from tokenizer , POS tagger and make one space
separated file for training. Then this same process applied for
testing dataset.</p>
      </sec>
      <sec id="sec-6-2">
        <title>For example: PERSON Gitika NNP B-NP</title>
        <p>Each tweets is preprocessed according to the requirement of CRF
suite which needs a file in which each line has a single word and
its NER tag separated with a white space, A new line represents
end of a sentence Two processed files were created, one with BIO
tags which shows multiword entities (for English language) and
another without it (for hindi language).</p>
      </sec>
    </sec>
    <sec id="sec-7">
      <title>2.3 Post-processing</title>
      <p>Output of the NER tagger would be only NE tag. So we have
combined it with its named entity, tweet_id and user_id. Then find
the length of the named entity and its index-means position of the
named entity.</p>
      <p>And as per given format we have arranged such as:
Tweet ID:623472520352636928 User Id:241166752
NETAG:PERSON NE:Ali Index:104</p>
      <p>Length:3</p>
    </sec>
    <sec id="sec-8">
      <title>3. ANALYSIS</title>
      <p>Over the past decade, Indian language content on various media
types such as websites, blogs, email, chats has increased
significantly. And it is observed that with the advent of smart
phones more people are using social media such as twitter,
facebook to comment on people, products, services, organizations,
governments. Thus we see content growth is driven by people
from non-metros and small cities who are mostly comfortable in
their own mother tongue rather than English. Though still this
Indian language content is only a fraction of the English content.
The growth of Indian language content is expected to increase by
more than 70% every year.</p>
      <p>Hence there is great need to process this huge data automatically.
Especially companies are interested to ascertain public view on
their products and processes. This requires natural language
processing software systems which identify entities, identification
of associations or relation between entities. Hence an automatic
Entity extraction system is required.</p>
      <p>Named Entity Recognition (NER) is one of the most important
information extractions techniques being developed in the NLP
and IR communities. Considerable success has been achieved
in English with extraction of multiple entities as per domain
of interest. However, the area poses considerable challenges
when tried in other languages and particularly Indian Languages.
Such as - There is no capitalization available in Indian languages.
There is lot of research work going on in NER for Indian
languages, such as Workshops NERSSEA-2008, SANLP 2010,
2011 but, there is lack of bench mark data to compare several
existing systems. There is no common evaluation methods exists
to judge any researchers’ work.</p>
    </sec>
    <sec id="sec-9">
      <title>4. RESULTS AND DISCUSSION</title>
    </sec>
    <sec id="sec-10">
      <title>4.1 Evaluation metrics</title>
      <p>Two standard measures, Precision (P) and Recall (R) are used for
evaluation of the Named Entity (NE) tagger, where precision is
the measure of the number of entities correctly identified over the
number of entities identified and recall is the measure of number
of entities correctly identified over actual number of entities. F
measure is calculated which is the harmonic mean of precision
and recall</p>
      <p>F =
When β = 1, F measure is called F1 measure or simply F1 score.</p>
    </sec>
    <sec id="sec-11">
      <title>4.2 Test results</title>
      <p>Languages</p>
      <sec id="sec-11-1">
        <title>Hindi</title>
      </sec>
      <sec id="sec-11-2">
        <title>English</title>
      </sec>
    </sec>
    <sec id="sec-12">
      <title>5. CONCLUSION</title>
      <p>CRF models are appropriate for the highly inflective Indian
languages and perform better than other systems like HMM,
MEMM etc. (Vijay Sundar Ram R, 2011). CRFsuite generate
model based on the learning and provides output (NE tag) as per
the generated model. But Problem is, NER system learned using
CRF takes more time for training the model. The parts-of-speech
tag is the important feature for NER to identify the named entity
chunk. Incorrect parts-of-speech tag for the token may result in
reducing the accuracy of NER system. Achieving a high
performing NER system requires more study and deeper
understating of linguistic features. Various permutation and
combination of feature sets can be used and tested for getting high
recall value and eventually higher F1-scores.</p>
    </sec>
    <sec id="sec-13">
      <title>6. FUTURE WORK</title>
      <p>In English and Hindi both language we will try to get more
accurate results in identifying and tagging named entities. For that
we will optimize our features sets.</p>
    </sec>
    <sec id="sec-14">
      <title>7. ACKNOWLEDGEMENT</title>
      <p>We would like to thanks Prof. Prasenjit Majumder sir for his
guidance throughout the work. Additionally, we would like to
thank FIRE 2015 for providing a great opportunity to work under
this task and facilitating the support.
[6] RDRPostagger
[7] Kudo, Taku. "CRF++: Yet another CRF toolkit."</p>
      <p>Software available at http://crfpp. sourceforge. net (2005)</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          <string-name>
            <given-names>Asif</given-names>
            <surname>Ekbal</surname>
          </string-name>
          ,
          <string-name>
            <surname>R.H.</surname>
          </string-name>
          :
          <article-title>Language Independent Named Entity Recognition in Indian Languages</article-title>
          . In: IJCNLP, pp.
          <fpage>33</fpage>
          -
          <lpage>40</lpage>
          (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>David</given-names>
            <surname>Nadeau</surname>
          </string-name>
          ,
          <string-name>
            <surname>S.S.</surname>
          </string-name>
          (n.d.).
          <article-title>: A survey of named Entity recognition and classification</article-title>
          . National Research Council Canada/ New York University
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>J.</given-names>
            <surname>Lafferty</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>McCallum</surname>
          </string-name>
          , and
          <string-name>
            <given-names>F.</given-names>
            <surname>Pereira</surname>
          </string-name>
          , “
          <article-title>Conditional random fields: Probabilistic models for segmenting and labeling sequence data</article-title>
          ,”
          <source>in Proceedings of ICML</source>
          , pp.
          <fpage>282</fpage>
          -
          <lpage>289</lpage>
          , (
          <year>2001</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [5]
          <string-name>
            <surname>standford</surname>
            <given-names>POStagger</given-names>
          </string-name>
          [8]
          <string-name>
            <surname>Okazaki</surname>
            ,
            <given-names>N.:</given-names>
          </string-name>
          <article-title>CRFsuite: A fast implementation of Conditional Random Fields</article-title>
          ,
          <source>CRFs</source>
          (
          <year>2007</year>
          ), retrieved from http://www.chokkan.org/software/crfsuite/
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>