<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="26069" public="1" featured="0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://archives.christuniversity.in/items/show/26069?output=omeka-xml" accessDate="2026-06-18T19:41:04+00:00">
  <collection collectionId="7">
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3139">
                <text>Faculty Publications</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <itemType itemTypeId="28">
    <name>Conference Paper</name>
    <description>Faculty Publications- Conference Papers</description>
  </itemType>
  <elementSetContainer>
    <elementSet elementSetId="1">
      <name>Dublin Core</name>
      <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
      <elementContainer>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="258980">
              <text>Vidhani, Nilesh; Ramasamy, Gobi; Syam Mohan, E.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="50">
          <name>Title</name>
          <description>A name given to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="258981">
              <text>From Text to Ticker: A Comprehensive Survey and Methodological Guide to Named Entity Recognition in Finance</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="40">
          <name>Date</name>
          <description>A point or period of time associated with an event in the lifecycle of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="258982">
              <text>01-01-2026</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="48">
          <name>Source</name>
          <description>A related resource from which the described resource is derived</description>
          <elementTextContainer>
            <elementText elementTextId="258983">
              <text>Proceedings of 6th International Conference on Expert Clouds and Applications, ICOECA 2026;pp.749-755</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="43">
          <name>Identifier</name>
          <description>An unambiguous reference to the resource within a given context</description>
          <elementTextContainer>
            <elementText elementTextId="258984">
              <text>&lt;a href="https://doi.org/10.1109/ICOECA68095.2026.11485558" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1109/ICOECA68095.2026.11485558&lt;/a&gt; &lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/pages/publications/105038080798?origin=resultslist" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/pages/publications/105038080798?origin=resultslist&lt;/a&gt;</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="38">
          <name>Coverage</name>
          <description>The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant</description>
          <elementTextContainer>
            <elementText elementTextId="258985">
              <text>Vidhani N., Christ University, Department of Computer Science, Bangalore, India; Ramasamy G., Christ University, Department of Computer Science, Bangalore, India; Syam Mohan E., Christ University, Department of Computer Science, Bangalore, India</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="258986">
              <text>The financial industry generates vast volumes of unstructured textual data from sources such as regulatory filings, news articles, social media, and earnings call transcripts. Extracting structured and actionable intelligence from this data remains a significant challenge. Named Entity Recognition (NER) is a fundamental task in natural language processing that supports this process by identifying and categorizing key information within text. However, the linguistic complexity, contextual ambiguity, and domain-specific terminology of financial text require specialized approaches that extend beyond general-purpose NER models. This paper presents a comprehensive survey and methodological guide to Financial Named Entity Recognition (Fin-NER). It begins by introducing the core concepts of NER while highlighting the unique challenges posed by financial text. The paper then reviews the evolution of Fin-NER approaches, ranging from rule-based systems and classical machine learning techniques to modern deep learning architectures. Furthermore, it analyzes the distinction between fine-tuned transformer-based models and general-purpose large language models in the current research. The study also examines commonly used datasets and evaluation metrics for benchmarking Fin-NER systems. Finally, it discusses key findings, existing methodological limitations, and future research directions, including hybrid modeling strategies, cross-lingual datasets, and the development of more reliable and explainable systems. Overall, this work serves both as a scholarly review of the Fin-NER field and as a practical guide for researchers and practitioners seeking to transform unstructured financial text into structured and informative representations.  2026 IEEE.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="258987">
              <text>Benchmark Analysis; Deep Learning; Domain Adaptation; Financial Natural Language Processing (Fin-NLP); Financial Text Mining; FinBERT; Information Extraction; Large Language Models (LLMs); Named Entity Recognition (NER); Transformer Models</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="258988">
              <text>Institute of Electrical and Electronics Engineers Inc.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="46">
          <name>Relation</name>
          <description>A related resource</description>
          <elementTextContainer>
            <elementText elementTextId="258989">
              <text>ISBN: 979-833157451-2;</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="258990">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="258991">
              <text>Conference paper</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="47">
          <name>Rights</name>
          <description>Information about rights held in and over the resource</description>
          <elementTextContainer>
            <elementText elementTextId="258992">
              <text>Restricted Access; Hardcopy may be available in the library</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="42">
          <name>Format</name>
          <description>The file format, physical medium, or dimensions of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="258993">
              <text>online</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
