<!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>The annotation coreference task at IberEval'2017: the experience of CLUL/UE</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Amalia Mendes</string-name>
          <email>amaliamendes@letras.ulisboa.pt</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Sandra Antunes</string-name>
          <email>sandra.antunes@gmail.com</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Paulo Quaresma</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Center for Linguistics of the University of Lisbon</institution>
          ,
          <country country="PT">Portugal</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Computer Science Department, University of Evora</institution>
          ,
          <country country="PT">Portugal</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2017</year>
      </pub-date>
      <fpage>83</fpage>
      <lpage>91</lpage>
      <abstract>
        <p>In this paper the process of coreference annotation in Portuguese texts in the context of a task of IberEval 2017 is described and the main observed problems are discussed. The work was done by a team of researchers from the Centre for Linguistics of the University of Lisbon (CLUL) and from the Computer Science Department of the University of Evora (UE). Due to time constraints and the complexity of the task, only researchers from CLUL were able to nish successfully the annotation process. The main problems are presented and discussed and some possible solutions are proposed. Nevertheless, the obtained results are similar with the overall results of the task.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>We report here our annotation experience in the scope of the coreference
annotated corpus task at IberEval 2017. The rst task was for each team to select
a set of texts to be made available for annotation. The texts selected by the
CLUL/UE team are taken from the LE-PAROLE Corpus, a 3 million words
corpus of European Portuguese from di erent genres that was compiled for the
LE-PAROLE project as the Portuguese counterpart of a set of comparable
corpora of 20 European languages to be made available free of copyrights. For each
language, a subset of 250.000 words was also annotated for POS and manually
revised [5]. We selected texts from this corpus to ensure that the texts would be
cleared for copyright issues and that the results of the coreference annotation
task could be freely distributed to the community. Another reason was that this
corpus allowed us to dispose of texts from a set of di erent genres. For the
coreference annotation task, texts were meant to have a maximum of 1200 words. We
selected the shortest texts of newspapers from the LE-PAROLE and, when the
texts were longer, we adjusted the length of the document.</p>
      <p>The annotation was performed using the editor CorrefVisual [6], developed
by the Group of Natural Language Processing PLN-PUCRS at Pontif cia
Universidade Catolica do Rio Grande do Sul. We rst annotated a text sent by the
organizing committee for training and to report any problem that we might
encounter with the editor. The result of the annotation of this text was then sent
back to the organization of the task. This rst stage of the task was very
important to get used to the editor and to the guidelines, and for a rst impression of
the task.</p>
      <p>The goal was then for each element of our team to annotate 10 texts, that
were selected out of the set of texts sent by all the teams. Annotator1 (SA)
annotated the full 10 texts, annotator2 (AM) annotated only 6 texts due to
time constraints. All other annotators failed to nish the task: two of them due
to di culties with the computational process (they were not able to install and
to run the annotator) and two of them due to time constraints and the linguistic
complexity associated with the task (these annotators background was computer
science).</p>
      <p>Our experience annotating with the CorrefVisual editor is reported in section
2, some issues in identifying coreference relations are discussed in section 3, as
well as our interannotator agreement in section 4, and some nal remarks are
presented in section 5.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Working with the CorrefVisual editor</title>
      <p>The tool CorrefVisual [6] runs in Java and allows the edition of texts previously
annotated with CORP [3, 2], a nominal coreference resolution tool for the
Portuguese language. Two di erent operating systems (windows and ios) were used
during the annotation and the tool worked well on both systems. It is important,
however, to point out that two annotators were not able to install CorrefVisual
in their computers due to problems with the operating system and Java versions.
As they were not able to obtain technical help in time, they were not able to
successfully nish the annotation.</p>
      <p>We received a short description of the tool and its functionalities that was
extremely useful to get acquainted with the editor and how to proceed with the
annotation3. We also received guidelines with a description of the task, an
explanation of the concept of coreference and examples of coreference chains and also
negative examples. The guidelines were clear and well structured but, of course,
considering the complexity of the task, we encountered several cases that were
not considered in the guidelines and that we will discuss in section 3. Moreover,
two annotators, having a good knowledge in computer science but a weak
linguistic background, failed to understand all the concepts and implications of the
task and they were not able to annotate the texts. This point clearly shows the
high di culty and the requirement of very speci c skills for this task.</p>
      <p>The two successful annotators in our team worked independently on their
annotations and didn't discuss the work among them. They relied solely on the
guidelines that were made available by the organizing team. This was done on
purpose to properly evaluate interannotator agreement.</p>
      <p>The main problem that was encountered with the editor was the delimitation
of phrases: when changing the length of a phrase, the editor returned an error
message saying that more than one phrase was selected, even when only one
phrase was highlighted. After reporting on this issue, there was information to
use the ESC key but making sure that at least one free phrase was selected,
3
http://www.inf.pucrs.br/linatural/wordpress/index.php/recursos-eferramentas/correfvisual/
otherwise the unselection wouldn't work. This solved the problem and it was
then easy to unselect all current selections (even invisible ones) and proceed
with the selection and manipulation of a single phrase.</p>
      <p>The NPs are not editable in the editor, and they have to be selected out
of the list of NPs that have been automatically identi ed in the preprocessing
stage. Some of the NPs were automatically attributed to a reference chain and
the remaining ones were listed in a separate window. The annotator task was
to verify the contents of each suggested reference chain and to modify it when
necessary, using the list of NPs in the separate window (free nominal phrases).</p>
      <p>The NPs in the reference chains were frequently inadequate and in this case it
was necessary to remove the NPs to the list of free nominal phrases (by dragging
it to the window) or to manipulate the NP to obtain the right length. When the
NP that was aimed for was not available in the list of free nominal phrases,
another NP close in the context had to be selected and its length manipulated
until it tted. In selecting a di erent NP, it was crucial to make sure that it
would not be required for another reference chain.</p>
      <p>For instance, there are two di erent reference chains in Apos a sua
constituic~ao: the NP refers to one reference chain and the possessive pronoun to
another one. In order to identify the possessive separately, one had to choose
a free nominal phrase close by in the context and remove and add tokens until
the possessive was correctly identi ed. In other cases, it was not possible to nd
a sequence, among the free nominal phrases available, that could correctly
capture the NP that we were aiming for. For instance, according to the guidelines,
the apposition should be identi ed as a separate referential expression, as in o
feiticeiro ( o psiquiatra colectivo ou o Moreno de ent~ao ), but there was no free
nominal phrase that would single out the part between curved brackets.</p>
      <p>To identify the correct NP in the list of free nominal phrases, the annotator
could use the function Search nominal phrases, that would highlight the NPs
containing the sequence that was queried. This was very helpful for the task.
Several NPs could be highlighted as the result of the search (although not visible
in the screen) and the annotators had to remind to check the results of the search
before dragging an NP to the reference chain box, otherwise all the highlighted
NPs would be dragged together. The identi cation of the correct NP in the list
of free nominal phrases was anyway time consuming, especially when several
NPs had very similar content. This involved checking them one by one in the
context before selecting the right one.</p>
      <p>
        Some of the problems that we experienced in the identi cation of the nominal
phrases are due to the preprocessing of the texts, namely tokenization and the
grouping of tokens as named entities. For instance, titles were grouped together
with the rst token of the following sentence as one named entity, as in Hospital
de Castelo Branco O Hospital Distrital and also Linha de o Corgo Esta. Some
named entities that were automatically identi ed contained more lexical material
than required. For instance, in the sequence Extinc~ao do Gabinete de
Planeamento e de Coordenac~ao do Combate a Droga, we couldn't eliminate the rst two
tokens Extinc~ao do and had to select the whole sequence. The tokenization
process wrongly treated the accusative pronoun nos as the contraction of em and os,
in example (
        <xref ref-type="bibr" rid="ref1">1</xref>
        ). Consequently, we included both tokens as part of the reference
chain.
(
        <xref ref-type="bibr" rid="ref1">1</xref>
        )
(
        <xref ref-type="bibr" rid="ref2">2</xref>
        )
      </p>
      <p>Para em os explicarmos temos de ir buscar a ponta a o princ pio de o
seculo ( le dn81701)</p>
      <p>The post-verbal accusative or dative clitic is usually treated as an
independent token that can be identi ed separately as part of a reference chain (as in
(2-a)), but in some cases, the tokenization didn't separate verb and clitic, and
both tokens had to be selected as part of the chain, as illustrated in (2-b).</p>
      <p>o homem n~ao devia obedecer a a natureza , mas sim venc^e {la
(dn88218).</p>
      <p>desa ar e vencer a natureza contrariando-a (dn88218)</p>
      <p>In several cases, the manipulation of the length of the NP would create an
incorrect tokenization by including parts of the previous or following token. For
instance, when modifying a sequence to obtain a single token que, it included
the rst letter of the following token hoje. The result of the annotation is que h
and it couldn't be corrected.
3</p>
    </sec>
    <sec id="sec-3">
      <title>Linguistic issues in annotating coreference</title>
      <sec id="sec-3-1">
        <title>Near Identity</title>
        <p>In many contexts, it is di cult to establish with absolute certainty that two
NPs are coreferent [4]. For instance, in the initial training phase, we decided
to treat as coreferent the NP os primeiros c~aes domesticos and the NP c~aes
domesticos that occurs in the larger NP fosseis de c~aes domesticos. It can be
debated whether the two are coreferent: although the second NP refers to fossils
which are consequently old, it might not refer exactly to the fossils of the rst
domestic dogs. The two NPs were treated as coreferent to avoid dividing the
data into many reference chains. This brings about the question of Near-Identity,
which will be treated according to the level of granularity and the general goals of
the annotation. Another example from the training phase is the NP diversidade
genetica and the noun diferencas that were treated as coreferent because the
di erences were interpreted contextually as genetic di erences. This reference
chain was already automatically pre-identi ed in the CorrefVisual editor.</p>
        <p>
          In another case, we annotated two near corereferent NPs as part of di erent
reference chains. In example (
          <xref ref-type="bibr" rid="ref3">3</xref>
          ), ser humano and a humanidade are treated as
non coreferent due to the explicit mention of their di erent scope in the context,
although they appear to be used in the rest of the text as synonyms.
(
          <xref ref-type="bibr" rid="ref3">3</xref>
          )
        </p>
        <p>
          o ser humano e, por extens~ao, a humanidade (dn81201)
Nominal phrases may be lexically distinct but very similar in terms of their
reference, as in examples (4-a) and (4-b), where estac~oes de recolha and estac~oes
meteorologicas refer to the same entity and a escala mundial and o planeta refer
to the same scope of the network. We considered the two NPs as part of the
same reference chain.
(
          <xref ref-type="bibr" rid="ref4">4</xref>
          )
        </p>
        <p>a rede de estac~oes de recolha a a escala mundial (pu92214)
a rede de estac~oes meteorologicas de o planeta (pu92214)</p>
        <p>
          The following case raises even more questions about what can be considered
as coreferent. In example (5-a), the nouns modelos matematicos and
computadores are modi ed by an adjectival phrase with very speci c lexical material.
In example (5-b), the same nouns are modi ed by the less informative adjective
melhores. Could we consider that the better models and computers that the
second example mentions are the ones capable of modelizing the weather and the
meteorological conditions? We consider that it is indeed the case, based on the
context, and annotated as coreferent.
(
          <xref ref-type="bibr" rid="ref5">5</xref>
          )
        </p>
        <p>Ha alguns anos , faltavam estaco~es de observaca~o e na~o havia modelos
matematicos nem computadores capazes de modelizar o clima e as
condic~oes meteorologicas (pu92214)
Considera que os principais problemas consistem em a falta de dados
de base , de melhores modelos matematicos , de melhores
computadores (pu92214)</p>
      </sec>
      <sec id="sec-3-2">
        <title>Quanti cation</title>
        <p>
          The quanti cation of the NPs raises many questions regarding the annotation
of coreference. The NPs descargas eletricas atmosfericas and um raio, in (6-a)
denote the same type of entity in the text and di er in terms of their register
(more vs. less specialized). Although the rst is in the plural form and the
second in the singular, they both have a generic reading that points to a case of
coreference (or near identity). Compare, however, (6-a) with (6-b): in the second
sentence, the NP also has a generic reading but it is quanti ed. The question is
whether it should be included in the same reference chain. However, quanti ed
NPs are not considered coreferent: even if they denote the same type of entity,
they refer to a speci c subset of those entities. These issues should be made
explicit in the annotation guidelines.
(
          <xref ref-type="bibr" rid="ref6">6</xref>
          )
a.
        </p>
        <p>Lago de Maracaibo , em a Venezuela , apresenta a concentraca~o
mais elevada de descargas eletricas atmosfericas de o mundo . Em
algum lugar de o mundo esta caindo um raio em este momento .
(Texto11.txt)
44 descargas eletricas atmosfericas a cada segundo (Texto11.txt)</p>
      </sec>
      <sec id="sec-3-3">
        <title>Modality</title>
        <p>The presence of epistemic modal markers (i.e, lexical markers that express values
such as uncertainty, possibility) raises issues in terms of the annotation of
coreference [1]. The same entity is referred to through the view of a di erent source
(7)
(8)
in examples (7-a) and (7-b) (the NPs are in italic, while the modal marker is
underlined). This would mean that the coreference exists only for this speci c
source: for instance, aquela organizaca~o do trabalho and um dos primeiros passos
num caminho que tende a levar longe have the same reference for the source,
namely o sacrossanto poder do patr~ao na empresa, but it is clear that the author
of the text disagrees with this view. Coreference would then be dependent on
the view of each source.</p>
        <p>os depoimentos de quem viveu a cadeia , desde o velho Navel a o
recente Haraszti , deixam -nos a impress~ao de um trabalho
destruidor..." (Texto11.txt)
Aquela organizaca~o de o trabalho , a o conferir poderes a os
trabalhadores sobre as condico~es de o trabalho , e vista por o sacrossanto
poder de o patr~ao em a empresa como um de os primeiros passos em
um caminho que tende a levar longe . de a resist^encias (Texto11.txt)
In example (8), modality does not refer to the viewpoint of another source.
Modality is expressed by a conditional clause and the equivalence between the
two NPs is only valid if the condition applies. In this speci c case, the condition
is to be pragmatically understood as a goal, so that modality doesn't seem to
a ect the existence of coreference.</p>
        <p>E o principal objectivo de a OMM e e a coisa mais sensata a fazer se
queremos compreender o fenomeno de o aquecimento global e de as suas
implicac~oes.</p>
      </sec>
      <sec id="sec-3-4">
        <title>Embedded and coordinated NPs</title>
        <p>One of the rst issues faced during the annotation was whether an embedded
NP could be part of another reference chain. For instance, the NP illustrated in
(9) would refer to the two reference chains indicated in the example. We treated
embedded NPs as part of other reference chains, when applicable.
(9)
o estudo das sociedades primitivas (dn81201)
reference chain 1: o estudo das sociedades primitivas
reference chain 2: as sociedades primitivas
The same issue arose in what concerns coordinated NPs. For instance, could the
NP os primatas in (10) be included in the reference chain os antropoides ? We
treated coordinated and embedded NPs similarly.
(10)</p>
        <p>Os animais inferiores , os primatas e o homem primitivo constituem uma
linha evolutiva que se revela sempre mais complexa , ate desembocar em
o salto qualitativo que e a civilizaca~o . (dn81201)</p>
      </sec>
      <sec id="sec-3-5">
        <title>Modi ed NPs</title>
        <p>Another issue is whether a modi ed nominal head can be considered
independently of its modi ers. For instance, in (5-a) the complex nominal head modelos
matematicos and the head computadores are modi ed by an adjectival phrase.
We considered that the modi er had to be included since it restricts the reference
of the nominal.</p>
      </sec>
      <sec id="sec-3-6">
        <title>Implicit content</title>
        <p>The antecedent of an anaphoric element can be implicit in the context. For
example, the meetings refered in (11-b) are the meetings of the Comission refered
in (11-a), so this entity is implicit in the NP: essas reuni~oes [da Comiss~ao
Intergovernamental de Negociac~ao]. The question is whether the NP in (11-b) should
be considered as part of the reference chain of the entity Comiss~ao
Intergovernamental de Negociac~ao.
(11)
An NP can refer to information that is scattered in the previous context, as the
NP todas essas estac~oes de observac~ao que e preciso montar ou reactivar. The
demonstrative relates to information showed in italic, but there is no clear NP
that could be considered coreferent with the underlined NP and such cases were
not annotated:
(12)</p>
        <p>A falta de estac~oes de recolha de dados e a que nos parece de maior
import^ancia superar , para permitir melhorar a abilidade de as previs~oes
. Quanto a os modelos que se usam actualmente , s~ao muito rigorosos
e n~ao nos parecem responsaveis por a imprecis~ao de as previs~oes : e a
qualidade de os dados que se fornecem a o computador que as condiciona
. em uma previs~ao de 24 horas para um pa s de a Europa ocidental ,
por exemplo , e preciso ter dados de toda a Europa , de uma grande parte
de Africa , etc. Se quisermos uma previs~ao a quatro dias , ja se torna
necessario cobrir cerca de metade de o globo . E , para uma previs~ao
alem dos os quatro ou cinco dias , s~ao precisos dados de todo o globo .
Mesmo que se tenha uma densidade optima de estaco~es de observaca~o
em Portugal , n~ao podemos esperar uma boa previs~ao , nem sequer para
Portugal , se o resto de o mundo n~ao estiver bem coberto . Existem mais
de dez mil estac~oes terrestres de observaca~o em o mundo e mais de 1500
estac~oes atmosfericas . (...)
Como espera nanciar todas essas estaco~es de observaca~o que e
necessario montar ou reactivar?</p>
      </sec>
      <sec id="sec-3-7">
        <title>Relatives</title>
        <p>Restrictive relatives were included in the NP because they contribute to establish
the reference of the NP. There could be two possible annotations of such cases,
illustrated in (13-a) and (13-b). Option 1 (a single NP) was preferred due to
the fact that the restrictive relative is included in the NP and is crucial for the
reference, but their was some hesitation in the annotation.
(13)
a gorila a quem M. Patterson conseguiu...
a. [a gorila a quem M. Patterson conseguiu. . . ]
b. [a gorila] a [quem]</p>
      </sec>
      <sec id="sec-3-8">
        <title>Length of the NPs</title>
        <p>Other constructions beside relative clauses raise questions about what to include
in the NP of a reference chain. For instance, in the case of the context illustrated
in (4-a), the issue was whether a escala mundial should be included in the NP or
not. The fact that a similar NP, illustrated in (4-b), occurred in the text lead to
the selection of the whole sequence. In contexts such as (14), the parenthetical
segment wasn't included because it is not essential to the reference of the NP
(just as a non restrictive relative would also be left out).
(14)
a de nic~ao e concretizaca~o de uma estrutura associativa empresarial
solida e e caz, essencialmente de base regional (dn81625)
4</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>Results and interannotator agreement</title>
      <p>Based on two les annotated by both annotators (pu92214 and dn81201), the
interannotator agreement reached a moderate kappa value of 0.40. We inspected
our results and compared the annotation of these les. In both les, Annotator2
treated more reference chains than Annotator1: 65 vs. 40 chains for pu92214
and 75 vs. 43 chains for dn81201. There is an average of 37 common reference
chains in the two annotations. The number of NPs in these common chains is
very similar among the two annotators. The di erences lie mostly in the
annotation of embedded NPs, and we believe that this could be easily improved with
explicit mention in the guidelines. There is also a di erence in the number of
pronominal elements in the chains (demonstrative, personal, possessive and
relative pronouns) and in the length of some NPs. For example, in the le dn81201,
22 reference chains that were identi ed by Annotator2 (and not by Annotator1)
involve relative pronouns, as can be observed in (15-a) and (15-b).
(15)
homem revelou aquela alma espiritual que hoje parece ser su ciente
tal como um carro que comeca a diminuir a velocidade por falta de
combust vel</p>
      <p>The annotation had to deal with clear cases of Identity but also with
NearIdentity relations, predicative relations and bridging. Results are positive
considering the complexity of the task, the lack of training of the annotators and the
level of granularity of the guidelines that were distributed. Also, we believe that
the manual edition of the NPs would have made the task easier and provided
conditions for a higher level of agreement among the annotators.
5</p>
    </sec>
    <sec id="sec-5">
      <title>Conclusion</title>
      <p>The main conclusion of our participation in this task is the high level of di culty
of the annotation process: it requires some computer science skills and a high
linguistic knowledge. As a consequence of these requirements all the annotators
without strong linguistic background failed to nish the task.</p>
      <p>The use of pre-identi ed NPs is also a potential problem: if they are correct
it helps the annotation process; but if they are incorrect this brings an overhead
to the process having, as a consequence, the need to manually undo the initial
annotation. The same problem is associated with the use of the visual editor: it
helps when the NPs are correct but it showed to lack stronger editing options,
allowing to easily change pre-identi ed segments.</p>
      <p>In spite of all the described problems we believe this task allowed us to
better understand the complexity and the details of coreference annotation and
to contribute to the creation of a reference annotated corpus for the Portuguese
language.
6</p>
    </sec>
    <sec id="sec-6">
      <title>Acknowledgments</title>
      <p>This work was partially supported by national funds through FCT { Fundaca~o
para a Ci^encia e Tecnologia, under projects PEst-OE/LIN/UI0214/2013 and
PEst/CEC/UI04668/2013.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Bouma</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Daelemans</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hendrickx</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hoste</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mineur</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>The corea-project, manual for the annotation of coreference in dutch texts</article-title>
          .
          <source>Tech. rep. (</source>
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Fonseca</surname>
            ,
            <given-names>E.B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vieira</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vanin</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Corp: Coreference resolution for portuguese</article-title>
          .
          <source>In: 12th International Conference on the Computational Processing of Portuguese, Demo Session (PROPOR)</source>
          (
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Fonseca</surname>
            ,
            <given-names>E.B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sesti</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Antonitsch</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vanin</surname>
            ,
            <given-names>A.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vieira</surname>
          </string-name>
          , R.:
          <article-title>Corp - uma abordagem baseada em regras e conhecimento sema^ntico para a resoluca~o de correfer^encias</article-title>
          .
          <source>Linguamatica</source>
          <volume>9</volume>
          (
          <issue>1</issue>
          ),
          <volume>3</volume>
          {
          <fpage>18</fpage>
          (
          <year>2017</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Mendes</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Organizaca~o textual e articulaca~o de oraco~es</article-title>
          . pp.
          <volume>1691</volume>
          {
          <fpage>1755</fpage>
          .
          <article-title>Gramatica do Portugu^es, vol. II. Lisboa: Fundaca~o Calouste Gulbenkian (</article-title>
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5. do Nascimento,
          <string-name>
            <given-names>M.F.B.</given-names>
            ,
            <surname>Mendes</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            ,
            <surname>Pereira</surname>
          </string-name>
          ,
          <string-name>
            <surname>L.</surname>
          </string-name>
          :
          <article-title>Providing on-line access to portuguese language resources: corpora and lexicons</article-title>
          . pp.
          <source>1825{1828. Proceedings of the IV International Conference on Language Resources and Evaluation - LREC2004</source>
          , Lisbon, Centro de Cultural de Belem (
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Tubino</surname>
          </string-name>
          , M.d.O.,
          <string-name>
            <surname>Silva</surname>
            ,
            <given-names>M.M.S.:</given-names>
          </string-name>
          <article-title>Visualizac~ao, manipulaca~o e re namento de correfer^encia em l ngua portuguesa</article-title>
          . Trabalho de conclusa~o de curso,
          <source>Pontif cia Universidade Catolica do Rio Grande do Sul</source>
          (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>