<!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>Named Entity Recognition for Code Mixing in Indian Languages using Hybrid Approach</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Rupal Bhargava</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Bapiraju Vamsi Tadikonda</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Yashvardhan Sharma</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>CCS Concepts</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>WiSoc Lab, Department of Computer Science Birla Institute of Technology and Science</institution>
          ,
          <addr-line>Pilani Campus Pilani-333031</addr-line>
        </aff>
      </contrib-group>
      <fpage>3</fpage>
      <lpage>7</lpage>
      <abstract>
        <p>Automating the process of Named Entity Recognition has received a lot of attention over past few years in Social Media Text. Named Entities are real world objects such as Person, Organization, Product, Location. Identifying these entities in social media text is an important challenging task due the informal nature of text present on social media. One such challenge that is faced in recognizing named entities in Indian Social Media Text is Code Mixing. Code Mixing is usage of more than one language in a sentence. Being a multilingual country, people of India tend to know more than one language, which in turn results in the code mixing of text while expressing their opinions. This paper describes the proposed approach for shared task CMEE-IL (Code Mix Entity Extraction in Indian Language), FIRE 2016. Proposed algorithm uses a hybrid approach of a dictionary cum supervised classi cation approach for identifying entities in Code Mix Text of Indian Languages such as Hindi- English and Tamil-English.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>Computing methodologies ! Natural language
processing; Information extraction; Language resources;
Machine learning;</p>
    </sec>
    <sec id="sec-2">
      <title>1. INTRODUCTION</title>
      <p>India is a multilingual country with more than 1600
languages being spoken such as Hindi, Punjabi,Bengali, Telugu,
Marathi, Tamil, Gujarati and many more. With the
introduction of Indic keyboards and articles that use Indic
languages, people started using Indic languages in their normal
conversation and this has made people to converse easily on
the internet. With such a scenario, it is common that
people know at least one more language apart from their native
language due to which there is a high possibility that
people mix words from two or more di erent languages while
writing or speaking something. This mixing of words in
sentences is referred as code mixing. Code mixing is present
where people speak in an informal way, like in social media.</p>
      <p>Growing usage of social media platforms like Facebook,
Twitter and WhatsApp has led to an increase of code mix
data present because of interplay of Indian languages. Hence
for making best use of this data it needs to be analyzed.
Indic languages are used very much nowadays in general
conversations but there are a few Natural Language Processing
(NLP) resources that are available.When code mixed text
is combined as well very less resources are present. Hence
there is a greater need for developing NLP tool that can
handle code mixed texts with Indic languages.</p>
      <p>Entity recognition is a very important subtask of
Information extraction and nd its applications in information
retrieval, machine translation and other higher NLP
applications such as coreference resolution. Named Entities are
names of famous persons, organizations, locations, animals
etc.Named entities have a many uses like in sentiment
analysis,where recognizing named entities is important as they
don't add much value to the statement. Similarly while
tagging articles named entities are required for better search
results. There are many such uses where named entities are
used so named entity recognition is very important.Towards
this, FIRE 2016 has organized a task for entity recognition
in code mix text for Indian languages which identi es named
entity in code mix text of English-Hindi and Tamil- English
code mixed tweets. The Task was to identify the various
entities such as person names, organization names, movie
names, location names in a given tweet.</p>
      <p>Rest of the paper is organized as follows. Section 2
explains the related work that has been done in the past few
years. Section 3 presents the analysis of data set provided
by CMEE-IL 2016 Task Organizers. Section 4 explains the
Proposed Technique that have been performed for the task
with block diagrams. Section 5 discusses algorithm to
explain the procedure. Section 6 elaborates the evaluation and
experimental results and error analysis. Section 7 concludes
the paper and presents future work.
2.</p>
    </sec>
    <sec id="sec-3">
      <title>RELATED WORK</title>
      <p>
        In Named Entity recognition there has been signi cant
research done so far in English but same cannot be said
for Indian Languages due to rich morphology of indian
languages. Sujan et al [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] proposed a Named Entity
Recognition (NER) system which is a hybrid of maximum entropy
model, language speci c rules and gazetteer lists.This
system performs well for hindi and bengali languages. Malarkodi
et al [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] have developed a system speci c for tamil language
using Conditional random elds(CRF). Entity Extraction
from Social Media Text - Indian Languages (ESM-IL) task
of FIRE 2015 [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] had proposed a task of identifying Entities
in Indian Languages for social media text. As a baseline
system, task organizers build a system which just used raw
data and was trained on Conditional Random Field. It was
observed by them that most of the participants obtained
similar precision as that of baseline. However, there was a
signi cant improvement of recall over the baseline. As a
submission to the task Pallavi et al [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] proposed a system using
Conditional Random Fields(CRF)whereas Anand et al [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]
proposed a system using a Support Vector Machine (SVM).
Kamal et al. [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] used POS tag as a state and developed
a system using Hidden Markov Model (HMM) Classi er for
the task.
      </p>
      <p>
        In current scenario there has been a lot of work going on
recently found out trend of code-mixed texts in Indian
Languages. Parth et al. [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] in 2014 formally introduced the
concept of Mixed Script Information Retrieval (MSIR) and
challenges associated with it. Code Mixing recieved attained
some attention in 2015. In shared task MSIR, FIRE 2015
[
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] problem was proposed, for identifying mix scripts in text
along with 9 di erent Indian languages, Named Entities and
punctuations for which signi cant results were obtained. It
was found that most confusing language pair was that of
Hindi and Gujarati. Further, it was concluded that
performance of the system for each of the category is dependent on
the tokens used for that category. Not only this code mix
has found its application in di erent areas such as Query
Labeling [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], Sentiment Analysis [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], Question Classi cation
etc.
      </p>
    </sec>
    <sec id="sec-4">
      <title>DATA ANALYSIS</title>
      <p>Data Set provided by task organizers contained two code
mix data set, Tamil-English and Hindi- English. In Each
dataset , the training data consisted of two les, A text le
containing raw tweets along with their tweetID and UserID
and another text le containing Annotations to the tweets
present in the raw tweets le. The raw tweet les consists
of 2700 tweets in the Hindi-English corpus and 3200 tweets
in the Tamil-English corpus. All the tweets in the
HindiEnglish corpus were already romanized whereas the
tamilenglish corpus had a mixture of both tamil script and
romanised script. There were 22 tags present in the corpus as
mentioned in Table 1.</p>
      <p>Named Entity (NE) Tag Person, Entertainment and
Location occupies majority of the instances in Tamil -English
corpus. Person tag comprises of Names of Famous Actors,
Actresses, Politicians, New Reporters and Social Media
Celebrities. Entertainment Comprises of Names of Famous TV
shows and movies while Location consists of Names of
Famous Cities, Indian Towns and Names of Countries.</p>
      <p>Apart from these, there are some Numerical and Time
based Tags that are present as well which comprise of the
remaining part of Tamil-English data set. These tags
include Count, Distance, date, money, month, time and year.
Money represents numbers along with a monetary tag like
'15 dollars'. Organization is another tag present which
consists of names of organizations. The rest of the tags have
very less annotations present in the annotated le.</p>
      <p>Comparing Hindi-English with Tamil-English, The
percentage of tags for the minority tags remains almost the
same. But in the Hindi- English corpus the Tag
Entertainment has the highest number of annotations present.It is
followed by Person which is close to Entertainment.The rest
of order remains the same but with varying percentages.
4.</p>
    </sec>
    <sec id="sec-5">
      <title>PROPOSED TECHNIQUE</title>
      <p>A word level NE-recognition system is designed to
recognise Named Entities in a tweet. The proposed methodology
involves a pipelined approach for detecting each NE tag and
has been divided into following four phases:</p>
      <sec id="sec-5-1">
        <title>1. Pre-processing</title>
      </sec>
      <sec id="sec-5-2">
        <title>2. Number Based Named Entity Recognition</title>
        <p>3. Gazetteer List Based Named Entity Recognition</p>
      </sec>
      <sec id="sec-5-3">
        <title>4. Tree Based Named Entity Identi er</title>
        <p>4.1</p>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>Pre-Processing</title>
      <p>The Data is pre-processed before detecting named entities.
This is done to ensure that the data is uniform and the
system can bene t from that. The preprocessing consists
of creating a copy of the string in lowercase for uniformity.
It also removes all links present in the tweet. This
preprocessed tweet along with the original tweet is then passed
to the next phase.
4.2</p>
    </sec>
    <sec id="sec-7">
      <title>Number Based Entity Recognition</title>
      <p>This phase of proposed algorithm identi es number based
entity such as date, time, month, day, year, money, period,
quantity, distance and count using a set of Regular
Expressions Regular expressions are designed based on the common
patterns observed in the annotations for these tags.
Regular expressions work best in detection for these tags because
there are limited variations possible for each of these Tags.
For example the tag Day can be only one of the 7
possible days of a week in a language. So detecting them using
regular expressions will be e cient. While checking for NE
tags there is a possibility of having multiple tags attached to
the same token. To remove ambiguity proposed technique
checks for tags in a particular pre de ned order.
4.3</p>
    </sec>
    <sec id="sec-8">
      <title>Gazetteer Based Entity Recognition</title>
      <p>As shown in Table 1, apart from Entertainment, Location,
Person and Organization, Rest of the Tags contain very less
data that cannot be used to train a classi er. So Gazetteer
Lists are used for identifying Named Entities with insu
cient training data. Gazetteer lists are created from the
annotations given to the training data. While checking in
gazetteer list # and @ symbols were ignored.
4.4</p>
    </sec>
    <sec id="sec-9">
      <title>Classification</title>
      <p>The rest of the NE Tags are identi ed by creating feature
vector for each token of a tweet. These feature vectors are
then trained using a decision tree and extremely randomized
tree classi er . The features considered for building feature
vector are mentioned in Table 2.</p>
      <p>English dictionary feature is used to identify the presence
and absence of an english word i.e if it is a english word
it is 1 and if it is a non english word then its 0. Python
dictionary called pyenchant 1 was used for this identifying
this feature. Also for pre x su x feature a dictionary was
built using most common pre xes and su xes and presence
of these pre xes and su xes (length = 1 to 3) in tokens were
identi ed using the same. Gazetteer list feature checks for
the presence of the token in gazetteers list of the remaining
tags and uses this as a feature. Previous token tag was also
taken into account to check structure of the tweet. Using all
1http://packages.python.org/pyenchant/</p>
      <p>Algorithm 1 explains the proposed technique for Named
Entity Recognition of code mixed text. The System rst
pre-processes the input by removing the website and twitter
links (implemented by callable: Link remover ) and then
converts the tweet into lowercase (implemented by callable:
Case conversion). We check for all numerical features like
date, time, money, quantity, period, distance, day and count
(implemented by callable: check Numerical).Before adding
it to the nal predictions we check for overlapping Tags and
remove them (using add without repetition). This is the
second phase of the system.</p>
      <p>In the third phase, we tokenize the tweets (using the
function Tokenize) and check if any of the token is present in
any of the gazetteer list (using check gazetteer List) and
add them to the nal list of tags of that tweet.This ends
the third phase of the system. In the nal phase we create
feature vectors for each tweet and then predict using the
classi er (clf) already trained using a training data. The
classi er(clf) used are decision trees and extremely
randomized trees.</p>
      <p>Algorithm 1 Algorithm for Identifying Named Entity
Recognition for Code Mixed Text in Indian Language
1: Input: Code-Mixed tweets list , S
2: Output: Predicted Named Entity Labels, P
3: Initialization: P=[], toks=[], NE Data=[], NE Tags=[]
4: for i=0 to S.length do
5: Link remover(S[i])
6: Case conversion(S[i])
7: end for
8: for i=0 to S.length do
9: d=check Numerical(S[i])
10: add without repetition(d)
11: tok =Tokenize(S[i])
12: for j=0 to tok.length do
13: g = check gazetteer List(tok[ j ] )
14: add without repetition(P , g )
15: f = Create Feature vector(tok[ j ])
16: c=clf.predict(f)
17: add without repetition(P,c)
18: end for
19: end for</p>
    </sec>
    <sec id="sec-10">
      <title>EXPERIMENTS &amp; RESULTS</title>
      <p>CMEE-IL, FIRE 2016, had proposed the task of Named
Entity Recognition in Hindi-English and Tamil-English Code
mixed text. Three runs were submitted for the task
evaluation for each language pair. Four versions were created for
di erent runs submitted. In all the versions, numerical
feature were detected using numerical function as explained in
section 4.2. Rest of the tags were classi ed using di erent
versions created as speci ed in Table 3.</p>
      <p>The rest of the tags were classi ed using gazetteer list
phase as mentioned in section 4.3.This was done due to low
amount of training data available for few tags such as plants,
disease, locomotive etc as mentioned in Table 1. All the
Variations for the proposed algorithm were evaluated using
F-Score for each language pair and nally Run1, 2, 3 for
Hindi-English used versions 1, 2 and 4 respectively whereas
Run 1, 2, 3 for Tamil-English used versions 1, 3 and 4
respectively.
6.1</p>
    </sec>
    <sec id="sec-11">
      <title>Evaluation &amp; Discussion</title>
      <p>As shown in Table 4, run 2 performed the best for
HindiEnglish Proposed System. Similarly, run 2 performed best
for Tamil-English as well as indicated in Table 5. Based on
the F-Score, it can be concluded that algorithm with more
gazetteer List and Extremely Randomized forest (Version
2) performed well in case of Hindi- English. But in case of
Tamil-English, algorithm with less Gazetteer List and
Decision Tree (Version 3) proved to be e ective.</p>
      <p>Precision value could be less because of string matching
with elements of the gazetteer lists. Also, it can observed
that recall value is low for all the runs, this could be due
to less number of Named Entities for any sentence which in</p>
      <p>Few phases in proposed approach might have attributed
to misclassi cation for few tags. One such phase can be
the gazetteer list phase of the proposed method which is a
dictionary based approach and has disadvantages associated
with it. When there is less data present in the dictionary
the precision will be low for the system. So there is a need
for more elements in the list for a better recognition system.
Also, if there is an ambiguity in tags then there a chance
of misclassi cation. For example if we say there is a token
'Honey' it can represent a Person like 'Honey Singh' or as
a tag material. This ambiguity can only be solved using a
classi er.</p>
    </sec>
    <sec id="sec-12">
      <title>CONCLUSION &amp; FUTURE WORK</title>
      <p>In this paper, a hybrid approach of a dictionary cum
supervised classi cation approach for identifying entities in
Code Mix Text of Indian Languages such as Hindi- English
and Tamil-English is submitted for the task CMEE-IL,FIRE
2016. The proposed system used a pipelined approach to
identify the named entities. There are four variants of the
system based on the number of tags, the classi er can
detect and the classi er used. Further improvisation can be
done by incorporating features related to the structure of
the sentence. POS Tagging and Chunking of the tweets has
not been included, this an be another improvisation in the
proposed algorithm. Although we need better POS Taggers
for Code mixed Languages which can tag both romanised
and non-romanised tweets for the same.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <surname>Anand Kumar</surname>
            <given-names>M</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Shriya Se</surname>
          </string-name>
          , S. K. Amrita cen@ re 2015:
          <article-title>Extracting entities for social media texts in indian languages</article-title>
          .
          <source>In Working notes of FIRE 2015 - Forum for Information Retrieval Evaluation</source>
          , Gandhinagar, India, December,
          <year>2015</year>
          (
          <year>2015</year>
          ), vol.
          <volume>1587</volume>
          of CEUR Workshop Proceedings, CEUR-WS.org, pp.
          <volume>87</volume>
          {
          <fpage>90</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <surname>Bhargava</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sharma</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Sharma</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          <article-title>Sentiment analysis for mixed script indic sentences</article-title>
          .
          <source>In Advances in Computing, Communications and Informatics (ICACCI)</source>
          , 2016 International Conference on (
          <year>2016</year>
          ), IEEE, pp.
          <volume>524</volume>
          {
          <fpage>529</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <surname>Bhargava</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sharma</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sharma</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Baid</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <article-title>Query labelling for indic languages using a hybrid approach</article-title>
          .
          <source>In Working notes of FIRE 2015 - Forum for Information Retrieval Evaluation</source>
          , Gandhinagar, India, December,
          <year>2015</year>
          (
          <year>2015</year>
          ), vol.
          <volume>1587</volume>
          of CEUR Workshop Proceedings, CEUR-WS.org, pp.
          <volume>40</volume>
          {
          <fpage>42</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <surname>Gupta</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bali</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Banchs</surname>
            ,
            <given-names>R. E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Choudhury</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Rosso</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          <article-title>Query expansion for mixed-script information retrieval</article-title>
          .
          <source>In Proceedings of the 37th international ACM SIGIR conference on Research &amp; development in information retrieval</source>
          (
          <year>2014</year>
          ), ACM, pp.
          <volume>677</volume>
          {
          <fpage>686</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <surname>Malarkodi</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pattabhi</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Sobha</surname>
            ,
            <given-names>L. D.</given-names>
          </string-name>
          <article-title>Tamil ner{coping with real time challenges</article-title>
          .
          <source>In 24th International Conference on Computational Linguistics</source>
          (
          <year>2012</year>
          ), p.
          <fpage>23</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <surname>Pallavi</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Srividhya</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          , and Rexiline Ragini John Victor, R. M. Hits@ re task 2015:
          <article-title>Twitter based named entity recognizer for indian languages</article-title>
          .
          <source>In Working notes of FIRE 2015 - Forum for Information Retrieval Evaluation</source>
          , Gandhinagar, India, December,
          <year>2015</year>
          (
          <year>2015</year>
          ), vol.
          <volume>1587</volume>
          of CEUR Workshop Proceedings, CEUR-WS.org, pp.
          <volume>83</volume>
          {
          <fpage>86</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <surname>Pedregosa</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Varoquaux</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gramfort</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Michel</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Thirion</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Grisel</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Blondel</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Prettenhofer</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Weiss</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dubourg</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          , et al.
          <article-title>Scikit-learn: Machine learning in python</article-title>
          .
          <source>Journal of Machine Learning Research</source>
          <volume>12</volume>
          ,
          <string-name>
            <surname>Oct</surname>
          </string-name>
          (
          <year>2011</year>
          ),
          <volume>2825</volume>
          {
          <fpage>2830</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <surname>Rao</surname>
            ,
            <given-names>P. R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Malarkodi</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Devi</surname>
            ,
            <given-names>S. L.</given-names>
          </string-name>
          <article-title>Esm-il: Entity extraction from social media text for indian languages@ re 2015{an overview</article-title>
          .
          <source>In Working notes of FIRE 2015 - Forum for Information Retrieval Evaluation</source>
          , Gandhinagar, India, December,
          <year>2015</year>
          (
          <year>2015</year>
          ), vol.
          <volume>1587</volume>
          of CEUR Workshop Proceedings, CEUR-WS.org, pp.
          <volume>76</volume>
          {
          <fpage>82</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>Royal</given-names>
            <surname>Sequiera</surname>
          </string-name>
          , Choudhury,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Gupta</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            ,
            <surname>Rosso</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            ,
            <surname>Kumar</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            ,
            <surname>Banerjee</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            ,
            <surname>Naskar</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S. K.</given-names>
            ,
            <surname>Bandyopadhyay</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            ,
            <surname>Chittaranjan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            ,
            <surname>Das</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            , and
            <surname>Chakma</surname>
          </string-name>
          ,
          <string-name>
            <surname>K.</surname>
          </string-name>
          <article-title>Overview of re-2015 shared task on mixed script information retrieval</article-title>
          .
          <source>In Working notes of FIRE 2015 - Forum for Information Retrieval Evaluation</source>
          , Gandhinagar, India, December,
          <year>2015</year>
          (
          <year>2015</year>
          ), vol.
          <volume>1587</volume>
          of CEUR Workshop Proceedings, CEUR-WS.org, pp.
          <volume>19</volume>
          {
          <fpage>25</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <surname>Saha</surname>
            ,
            <given-names>S. K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chatterji</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dandapat</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sarkar</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Mitra</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          <article-title>A hybrid approach for named entity recognition in indian languages</article-title>
          .
          <source>In Proceedings of the IJCNLP-08 Workshop on NER for South and South East Asian Languages</source>
          (
          <year>2008</year>
          ), pp.
          <volume>17</volume>
          {
          <fpage>24</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <surname>Sarkar</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          <article-title>A hidden markov model based system for entity extraction from social media english text at re 2015</article-title>
          . In Working notes of FIRE 2015 -
          <article-title>Forum for Information Retrieval Evaluation, Gandhinagar</article-title>
          , India, December,
          <year>2015</year>
          (
          <year>2015</year>
          ), vol.
          <volume>1587</volume>
          of CEUR Workshop Proceedings, CEUR-WS.org, pp.
          <volume>91</volume>
          {
          <fpage>97</fpage>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>