Hi Devi, My feeling is CleartK based pipelines are the currently recommended ones to use. They have specific pipeline for each property you may want to detect (neg, uncertainty, subject, etc), thus providing more concise and understandable coding style.
From my personal experience, Assertion Non CleartK pipelines work well in detecting generic and subject properties while I have difficulty putting CleartK based pipelines to work for these two properties on user mode. On developer mode, I was not able to apply Assertion Non CleartK pipelines due to some errors, so it looks CleartK based pipelines are the only choices you have. I don’t think context annotator are still recommended now. Again, that’s only my feedback, welcome more discussion. Best, Yiming > On Apr 5, 2017, at 5:38 AM, Devikiran Ramadas <devikir...@gmail.com> wrote: > > Hi, > > I have been looking into the cTAKES code base for sometime now.. and have > few confusions related to identifying Negation, Uncertainty and other > properties for the identified named entity. > > It can be done by : > 1) Assertion module > - Cleartk based (neg, Uncertainty, subject, history, generic etc.) > - Non Cleartk (generic, subject ) > 2) Context Annotator (Negation, Uncertainty and history ) > > I have been using Context Annotator but saw usage of the Cleartk based > pipes even in the svn trunk version of Clinicalpipelinefactory class. > > Could some one please clear the air on what pipe is recommended for each of > the properties of Identified Annotation? > > Regards, > Devi
