You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ctakes.apache.org by "James Joseph Masanz (JIRA)" <ji...@apache.org> on 2013/08/29 17:35:52 UTC

[jira] [Updated] (CTAKES-231) missing NEs because of inconsistent chunking for parallel sentence constructions

     [ https://issues.apache.org/jira/browse/CTAKES-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Joseph Masanz updated CTAKES-231:
---------------------------------------

    Attachment: liver.cancer.chunking.issue.xmi.xml
    
> missing NEs because of inconsistent chunking for parallel sentence constructions
> --------------------------------------------------------------------------------
>
>                 Key: CTAKES-231
>                 URL: https://issues.apache.org/jira/browse/CTAKES-231
>             Project: cTAKES
>          Issue Type: Bug
>          Components: ctakes-chunker
>    Affects Versions: 3.0-incubating
>            Reporter: James Joseph Masanz
>         Attachments: liver.cancer.chunking.issue.xmi.xml
>
>
> cancer of colon, lung and liver
> results in an annotation for liver cancer
> cancer of colon, liver and lung.
> does not result in an annotation for liver cancer or for lung cancer.
> Thanks Dennis Lee Hon Kit for reporting this.
> Details:
> Reproduced by running 3.0.0-incubating with the separately downloadable UMLS resources, using the AggregatePlaintextUMLSProcessor.xml, results in these chunk annotations:
>  [0] org.apache.ctakes.typesystem.type.syntax.NP
>  [1] org.apache.ctakes.typesystem.type.syntax.PP
>  [2] org.apache.ctakes.typesystem.type.syntax.NP
>  [3] org.apache.ctakes.typesystem.type.syntax.NP
>  [4] org.apache.ctakes.typesystem.type.syntax.PP
>  [5] org.apache.ctakes.typesystem.type.syntax.NP
>  [6] org.apache.ctakes.typesystem.type.syntax.O
>  [7] org.apache.ctakes.typesystem.type.syntax.O
>  [8] org.apache.ctakes.typesystem.type.syntax.NP

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira