File Information
File: 05-lr/acl_arc_1_sum/cleansed_text/xml_by_section/abstr/06/e06-1025_abstr.xml
Size: 1,957 bytes
Last Modified: 2025-10-06 13:44:41
<?xml version="1.0" standalone="yes"?> <Paper uid="E06-1025"> <Title>Determining Term Subjectivity and Term Orientation for Opinion Mining</Title> <Section position="2" start_page="0" end_page="0" type="abstr"> <SectionTitle> Abstract </SectionTitle> <Paragraph position="0"> Opinion mining is a recent subdiscipline of computational linguistics which is concerned not with the topic a document is about, but with the opinion it expresses.</Paragraph> <Paragraph position="1"> To aid the extraction of opinions from text, recent work has tackled the issue of determining the orientation of &quot;subjective&quot; terms contained in text, i.e. deciding whether a term that carries opinionated content has a positive or a negative connotation. This is believed to be of key importance for identifying the orientation of documents, i.e. determining whether a document expresses a positive or negative opinion about its subject matter.</Paragraph> <Paragraph position="2"> We contend that the plain determination of the orientation of terms is not a realistic problem, since it starts from the nonrealistic assumption that we already know whether a term is subjective or not; this would imply that a linguistic resource that marks terms as &quot;subjective&quot; or &quot;objective&quot; is available, which is usually not the case.</Paragraph> <Paragraph position="3"> In this paper we confront the task of deciding whether a given term has a positive connotation, or a negative connotation, or has no subjective connotation at all; this problem thus subsumes the problem of determining subjectivity and the problem of determining orientation. We tackle this problem by testing three different variants of a semi-supervised method previously proposed for orientation detection. Our results show that determining subjectivity and orientation is a much harder problem than determining orientation alone.</Paragraph> </Section> class="xml-element"></Paper>