<!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>Using Clustering to Identify Outlier Chunks of Text</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Navot Akiva</string-name>
          <email>Navot@cs.biu.ac.il</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Department of Computer Science Bar Ilan University</institution>
          ,
          <addr-line>Ramat Gan</addr-line>
          ,
          <country country="IL">Israel</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2011</year>
      </pub-date>
      <abstract>
        <p>Intrinsic plagiarism detection is a sub-task of authorship identification in which outlier chunks must be detected solely on the basis of stylistic differences from the main body of the text. We present a first attempt at utilizing words that appear infrequently in a text as stylistic markers for distinguishing outlier chunks in the text. In the first phase of our method we cluster chunks of text represented by usage of infrequent words. In the second phase, we use a training corpus to identify cluster properties of outlier chunks.</p>
      </abstract>
      <kwd-group>
        <kwd>Intrinsic plagiarism</kwd>
        <kwd>clustering</kwd>
        <kwd>outlier detection</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1 Introduction</title>
      <p>One of the main difficulties in any plagiarism task is identifying the boundaries of
plagiarized text[1]. In the case of intrinsic plagiarism detection, we face the additional
difficulty that no source text is available for comparison. We thus need to
automatically identify sudden shifts in writing style.</p>
      <p>Our approach consists of two phases: chunks clustering and cluster properties
detection.</p>
      <sec id="sec-1-1">
        <title>2.1 Chunks Clustering Phase</title>
        <p>Chunking: For a given text, we first divide the text into chunks consisting of 1000
characters. We then identify the 100 rarest words that appear in at least 5% of the
chunks. (Thus we have a set of words that are infrequent in the text but not so
infrequent as to be useless. These parameters were not optimized and no doubt can be
significantly improved.) Each chunk is now represented by a numerical vector of
length 100 corresponding to the presence or absence of each of the rare words in the
chunk. We measure the similarity of pairs of chunks using cosine.</p>
        <p>Clustering: We then use a spectral clustering method called n-cut [2] to cluster the
chunks. We cluster the texts into only two clusters, which we hope will correspond to
the true text and the plagiarized text, respectively. This hope is often unrealistic
because there is no guarantee that the plagiarized material is taken from a single
source. It might be that different plagiarized sections are not similar to each other; it
might also be that there is little or no plagiarized material and the clustering will be
along lines that are unrelated to plagiarism.</p>
      </sec>
      <sec id="sec-1-2">
        <title>2.2 Cluster Properties Detection</title>
        <p>We thus use a second phase to identify clusters that really do consist of plagiarized
text. To do this, we run our clustering method on the training corpus and we measure
a variety of properties of each cluster and each chunk in each cluster. These properties
include the relative and absolute size of each cluster, the similarity of each chunk to
its own cluster, to the other cluster and to the whole document and so forth. The
intuition is that plagiarized chunks are those that are close to the centroid of the small
cluster and very far from the centroid of the whole document.</p>
        <p>We represent each chunk in the training set as a numerical vector recording each of
the above values and we label each chunk as including plagiarized material or not. We
then use supervised learning methods to learn decision trees using WEKA [3] for
distinguishing plagiarized chunks from non-plagiarized chunks.</p>
      </sec>
    </sec>
    <sec id="sec-2">
      <title>3 Evaluation Results</title>
      <p>We found it was best to learn separate classifiers for short (up to 20K), medium
(20K to 250K) and long (above 250K) documents.</p>
      <p>We used ten-fold cross-validation to optimize parameter settings and to estimate
accuracy results. For reasons of efficiency, we did not use the full training set. In
particular, we ignored all documents with more than 40% plagiarism. We also
randomly selected chunks from among the remaining documents.</p>
      <p>Our cross-validation results are shown in Table 1. Unfortunately, these numbers
turned out to be optimistic. On the PAN-2011 evaluation set, we achieved precision
12.7% and recall of 6.6%.</p>
      <p>Analysis of the results indicates that the method achieved especially poor precision
on short documents.</p>
    </sec>
    <sec id="sec-3">
      <title>4 Conclusions and Future Work</title>
      <p>Despite the poor evaluation results, we believe that our overall method is
promising. We should significantly increase the number of training examples on our
future experiments. There are a number of parameters that first need to be optimized,
including the choice of rare words and the size of the chunks (which need not be
constant). There are a number of other considerations that might improve results,
including using the full training set and clustering into k&gt;2 clusters.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          <string-name>
            <surname>Stein</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lipka</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Prettenhofer</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <article-title>"Intrinsic plagiarism analysis,"</article-title>
          <source>Lang. Resources &amp; Evaluation</source>
          , Volume
          <volume>45</volume>
          ,
          <string-name>
            <surname>Number</surname>
            <given-names>1</given-names>
          </string-name>
          ,
          <fpage>63</fpage>
          -
          <lpage>82</lpage>
          (
          <year>2010</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          <source>Proc. ACM International Conference on Knowledge Discovery and Data Mining (KDD)</source>
          , pp.
          <fpage>551</fpage>
          -
          <lpage>556</lpage>
          . (
          <year>2004</year>
          ) Hall,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Frank</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            ,,
            <surname>Holmes</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            ,
            <surname>Pfahringer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            ,
            <surname>Reutemann</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            ,
            <surname>Witten</surname>
          </string-name>
          ,
          <string-name>
            <surname>I.H</surname>
          </string-name>
          ,
          <source>The WEKA Data Mining Software: An Update; SIGKDD Explorations</source>
          , Volume
          <volume>11</volume>
          , Issue 1. (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>