<!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>RDI System for Extrinsic Plagiarism Detection (RDI_RED)</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Magda B.Fayek</string-name>
          <email>magdafayek@ieee.org</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
          <xref ref-type="aff" rid="aff4">4</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Ahmed Magooda Computer Engineering Department, Cairo University</institution>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Ashraf Y. Mahgoub Computer Engineering Department, Cairo University</institution>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Computer Engineering Department, Cairo University</institution>
        </aff>
        <aff id="aff3">
          <label>3</label>
          <institution>Computer Science Department</institution>
          ,
          <country>Kuwait University</country>
        </aff>
        <aff id="aff4">
          <label>4</label>
          <institution>Mohsen Rashwan Communication department, Cairo University</institution>
        </aff>
      </contrib-group>
      <fpage>126</fpage>
      <lpage>128</lpage>
      <abstract>
        <p>Extrinsic plagiarism detection gathered the attention of many researchers lately. Plagiarism process began to be more and more difficult to be detected due to appearance of other sophisticated plagiarism approaches other than direct copy and paste such as (phrase rephrasing, word shuffling, semantic substitution, etc…). In this paper, we present RDI system for extrinsic plagiarism detection (RDI_RED). RDI_RED system performs remarkably on a wide spectrum of plagiarism techniques starting from simple copy-paste to word shuffling and also complete sentence rephrasing. RDI_RED system achieved the first three positions in Arabic language plagiarism detection competition with a Plagdet (Plagiarism Detection score) of 80% which is 20% higher than the base line and 18% higher than the second best competing system.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>Plagiarism detection is a very interesting task as it is in its core a
competition between machines and humans. The essence of
plagiarism detection is like reverse engineering human behavior and
nullifying all the effort exerted in the process of modifying the
plagiarized text. Plagiarism detection can be clustered as two main
tracks:(1) Intrinsic plagiarism detection and (2) Extrinsic
plagiarism detection.</p>
      <p>Intrinsic plagiarism detection is the process of verifying the unity
of a document against itself without the need of any external
sources. This process is concerned with finding whether the
document is written by the same author or there exists some parts that
at high probability are not written by the same author.
On the other hand extrinsic plagiarism detection is the process of
evaluating a document and verifying if there exists some parts that
have been copied from external sources, this process is held with
the presence of external source which called (source documents)
these documents are treated like probable source of copying.</p>
      <p>Hazem Raafat</p>
    </sec>
    <sec id="sec-2">
      <title>2. METHOD</title>
      <p>The proposed RDI_RED system consists of three basic modules,
(1) Candidate source documents retrieval module, (2) Alignment
module and (3) Filtering module. In the following (Param1,
Param2, Param3,Param4, Param5 and Param6) are parameters that
we vary during the training process.</p>
      <p>
        First we will explain the retrieval module in detail. The retrieval
module depends on two approaches for candidate source
document retrieval:
1.Paragraph based retrieval: In this approach,
(a) The suspicious document is chunked into paragraphs. For
each paragraph, named entities are extracted from the document
using RDI_NER [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] and Arabic Wikipedia [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] dump module
proposed in Mahgoub et al. [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ].
(b) Inverse document frequency (IDF) weights are calculated
for each term.
(c) Two queries are constructed for each of the resulting
paragraphs as follows.
      </p>
      <p>
        (i) The first query is constructed by extracting (Param1)words
from the current paragraph. These (Param1) words are the
(Param1)/2 highest IDF named entities and (Param1)/2
highest IDF words that are not named entities.
(ii) The second query is constructed by extracting the
10grams that contains the maximum number of specified
terms, these terms are the terms which were extracted
while constructing the first query.
(d) The resulting queries are then issued to a search engine to
retrieve set of candidate source documents. Each query is
stemmed using RDI_Stemmer [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] and light10 stemmer proposed
by Leah S. Larkey et al. [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. The used search engine uses a
paragraph based index that has been constructed using LUCENE
search tool [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ].
2.Sentence based retrieval: In this approach,
(a) Source documents are chunked into sentences.
(b) For each sentence an ID is constructed.
(c) After that the constructed IDs alongside the chunked
sentences are fed into an inverted index using LUCENE.
(d) For each suspicious document the same procedure is
applied and each resulting sentence is treated as a query. Each query
is issued to LUCENE resulting in a candidate source document.
(e) All the retrieved documents for the suspicious document in
concern are sorted by the number of queries they were retrieved
by (one source document for each query).
      </p>
      <p>
        The candidate source documents retrieved by the two approaches,
are then passed to the alignment module. The alignment module
presented in this system is based upon three different alignment
approaches (1) Skip-gram based approach, (2) Sentence index
based approach and (3) Common words based approach.
1.Skip-gram based approach: This approach proceeds as follows.
(a) A suspicious document is scanned by a window of five
words with a one word step.
(b) The five words extracted by the window are stemmed
using RDI_Stemmer [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ],then all combinations of triple words are
extracted out of the five words (Skip-gram).
(c) The same approach is applied over the retrieved source
documents.
(d) For each of the suspicious document skip-grams, the
skipgram is compared to all of the source documents skip-grams and
the matched skip-grams are saved.
(e) The system then apply an expansion step. In this step for
all the matched skip-grams we group consecutive skip-grams that
are separated with no more than (Param2) number of characters
(either in suspicious document or source document) together.
2.Sentence index based approach: This alignment approach
depends mainly on the sentence based retrieval approach. Introduced
earlier, each sentence of the suspicious document is used as a
query where only the first source document match from the index
is considered for alignment. For each candidate source document,
the following steps are applied:
(a) The sentences constructed from the suspicious document
alongside the matched sentences retrieved added to a list of
(suspicious sentence ID – source sentence ID) pairs.
(b) For each (suspicious sentence ID – source sentence ID)
pair
(i) If there exists pair that resides within a window of length
(Param3) from another pair then mark this pair as a valid
matching pair.
(ii) If not, pass the text of both sentences for next module
(filtering module)
3.Common words based approach: This alignment approach
depends on the density of common words between a suspicious
document and a candidate source document pair in order to detect
the plagiarized parts between them. For each
(suspiciouscandidate source) pair, the following steps are applied:
(a) Get list of all common words.
(b) For each matching word, add list of its indices (positions of
the word in both document) into a matching indices list.
(c) Using a window of words of length (Param4), if the gap
between two consecutive matches is wider than (Param4) then we
split the list into two separate lists.
(d) Pass each set of extracted consecutive words from
suspicious document with its corresponding set in source list (which
has the maximum ratio of common words to their average length)
to the next filtering module.
      </p>
      <p>After the retrieval and alignment modules comes the filtering
module. The filtering module applies set of rules and give a final
decision to accept or reject the aligned part. For each of the
aligned parts the following rules are applied:
(a) If the source and suspicious chunks are equivalent accept
this part, else go to next rule.
(b) If the length of any of the two chunks is shorter than
(param5) of characters then this part is rejected, else continue.
(c) If the number of common words is greater than (param6)
then accept this part, else reject this part.</p>
    </sec>
    <sec id="sec-3">
      <title>3. EVALUATION</title>
      <p>In the training phase, the RDI_RED system are trained and tuned
with different set of configurations resulting into three different
training runs. Each configuration will described alongside its
training and testing performance results:
1.The first run uses the following configurations:
(a) Sentence based retrieval.
(b) Sentence index based alignment approach, and Common
words Alignment approach.
(c) Parameters tuned: Param3, Param4, Param5 and Param6.
Rank</p>
      <p>Method
Macro precision</p>
      <p>Macro recall
Micro precision</p>
      <p>Micro recall
Granularity</p>
      <p>Plagdet</p>
    </sec>
    <sec id="sec-4">
      <title>4. TECHNICAL DETAILS</title>
      <p>The systems evaluation carried out over training and test data was
performed on a personal machine with plausible specifications,
the following specifications are the specifications used during the
whole system evaluation process:
 Hardware Specifications:
─ CPU: Intel coreI7 4500U - 2 Cores – 1.8 ~ 3.0 GHz
─ RAM: 16 GB of RAM
 Software Specifications:
─ Operating System: Windows 7 x64
─ Development Environment: Visual Studio 2013
─ Programming Language: .Net C#
The RDI_RED system was trained using the training data
provided by the competition to get the best set of parameters for
(param1, param2, param3, param4, param5 and param6):
The training time for the previously illustrated approaches are:</p>
      <p>Train
160500
161190
150390
3
Magooda_1
0.80
0.79
0.88
0.81
1.05
0.77</p>
      <p>4
Palkovskii
0.97
0.54
0.99
0.58
1.16
0.62</p>
      <p>
        Baseline
0.99
0.53
0.99
0.59
1.20
0.60
different retrieval approaches using LUCENE and three different
alignment approaches. Three different configurations are tested
and tuned over the provided training dataset. Best results have
been achieved by combining more than one alignment approach
rather than using each approach as a standalone technique. The
combined approach achieved very promising results for Arabic
language despite the lack of resources. Despite being a
semilanguage-independent system RDI_RED achieved comparable
results to state of the art English language systems reported in
PAN-2014 [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ].
      </p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>[1] https://ar.wikipedia.org/</mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <surname>Mahgoub</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            ,
            <surname>Rashwan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A. M.</given-names>
            ,
            <surname>Raafat</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            ,
            <surname>Zahran</surname>
          </string-name>
          ,
          <string-name>
            <surname>A.</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            and
            <surname>Fayek</surname>
          </string-name>
          ,
          <string-name>
            <surname>B.</surname>
          </string-name>
          , M.:
          <article-title>Semantic Query Expansion for Arabic Information Retrieval</article-title>
          .
          <source>In: EMNLP: The Arabic Natural Language Processing Workshop, Conference on Empirical Methods in Natural Language Processing</source>
          , Doha, Qatar (
          <year>2014</year>
          )
          <fpage>87</fpage>
          -
          <lpage>92</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <surname>Larkey</surname>
          </string-name>
          , Leah S.,
          <string-name>
            <surname>Lisa</surname>
            <given-names>Ballesteros</given-names>
          </string-name>
          , and
          <string-name>
            <given-names>Margaret E.</given-names>
            <surname>Connell</surname>
          </string-name>
          .
          <article-title>Light stemming for Arabic information retrieval</article-title>
          .
          <source>Arabic computational morphology</source>
          . Springer Netherlands,
          <year>2007</year>
          .
          <fpage>221</fpage>
          -
          <lpage>243</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>[4] https://lucene.apache.org/</mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>[5] http://www.rdi-eg.com/index.htm</mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <surname>Potthast</surname>
          </string-name>
          ,
          <string-name>
            <surname>Martin</surname>
          </string-name>
          , et al.
          <source>Overview of the 6th International Competition on Plagiarism Detection. CLEF Conference on Multilingual and Multimodal Information Access Evaluation. ceur-ws</source>
          ,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>[7] http://misc-umc.org/AraPlagDet</mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>