<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="26050" 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/26050?output=omeka-xml" accessDate="2026-06-18T09:16:27+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="258714">
              <text>Rajan, Abraham; Manur, Manohar</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="50">
          <name>Title</name>
          <description>A name given to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="258715">
              <text>Fine-Tuned Deep Contextual BERT for Enhanced Aspect-based Sentiment Analysis: A Comparative Study on Laptop Reviews</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="258716">
              <text>01-01-2025</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="258717">
              <text>Proceedings of the 7th International Conference on Intelligent Sustainable Systems, ICISS 2025;pp.938-943</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="258718">
              <text>&lt;a href="https://doi.org/10.1109/ICISS63372.2025.11076195" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1109/ICISS63372.2025.11076195&lt;/a&gt; &lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/pages/publications/105012219887?origin=resultslist" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/pages/publications/105012219887?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="258719">
              <text>Rajan A., Christ (Deemed to be University), Department of Cse, Bangalore, India; Manur M., Christ (Deemed to be University), Department of Cse, Bangalore, India</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="258720">
              <text>Sentiment analysis entails the care full analysis, conduction of interpretation and conclusion of subjective texts even as an evaluation. In the business context, the companies' strategies towards growth makes use of both level of experience of consumers, market reach, social media, opinion and reputation of the brand. The different levels of performing the analysis includes the analysis at the document, phrase, and aspect levels. The sentiment which targets the polarity on some components of texts is often recognized by various Natural language processing (NLP) tasks for example aspect level sentiment analysis. This study presents the fine-tuned deep contextual BERT (FTDC BERT) aiming at improving the accuracy of sentiment polarization prediction. We look at different types of models including the LSTM based and the attention based and the BERT based models and where they performed on the laptop dataset. The fine-tuned and pre-trained BERT model exceeded all benchmarks and gave the most accurate work at 84.48%. This remarkable achievement testifies to the capability of the model in adapting its structure to varying degrees of sentiment contained in laptop reviews. Based on the comparative analysis, different models have different degree of success which indicates that sentiment has to be modelled separately for every set of data. This paper describes interesting areas of the future inline sentiment analysis for researchers and practitioners.   2025 IEEE.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="258721">
              <text>Aspect based sentiment analysis; BERT model; Fine-Tuned Deep Contextual-BERT (FTDC-BERT); Natural Language Processing; Sentiment polarity</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="258722">
              <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="258723">
              <text>ISBN: 979-833152243-8;</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="258724">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="258725">
              <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="258726">
              <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="258727">
              <text>online</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
