Hi Abhishek,
Yes,
Jay and I will have a session at ApacheCon on Drug Monitoring using
Spark/Hadoop and twitter feeds...
Will be happy to meetup.  Let's coordinate offline if you happen to be
around the area and to see if we can meet up.
--Pei

On Tue, Apr 7, 2015 at 8:03 PM, Abhishek Srivastava <[email protected]>
wrote:

> Thanks for the thread. I would love to meet up with CTAKES people.
>
>
>
> Please let me know how can we coordinate this. Please reach out to me my
> email Id is abhishes -at-  gmail -dot- com
>
>
>
> Does CTAKES have a session at apache con?
>
>
>
> *From:* Pei Chen [mailto:[email protected]]
> *Sent:* Monday, April 6, 2015 10:07 AM
> *To:* [email protected]
> *Subject:* Re: Getting Started with CTAKES
>
>
>
> I believe Tim started a thread on how to programmatically extract the
> entitis/cui's currently via this thread:
>
>
> http://mail-archives.apache.org/mod_mbox/ctakes-dev/201503.mbox/%3ce084d8efe2b03a408b324458c5212e9434c10...@chexmbx3a.chboston.org%3e
>
>
>
> A couple of us are going to be in Austin,TX for Apache Con so if you
> happen to be there, we can plan to meet up.
>
> --Pei
>
>
>
> On Sun, Apr 5, 2015 at 2:51 AM, Abhishek Srivastava <[email protected]>
> wrote:
>
> I have already searched the archive of this mailing list however if this
> question is duplicate then please don't flame me.
>
>
>
> I have some experience with NLTK in Python. I have gone through some of
> the basic literature on natural language processing.
>
>
>
> Using NLTK I can perform entity extraction pretty easily.
>
>
>
> My questions are
>
>
>
> 1. is there a tutorial available on CTAKES from a development perspective.
> I need to use the API to perform entity extraction. (i need exact APIs).
>
>
>
> 2. How can someone build a custom corpus with CTAKES. I know it works in
> medical context but my use case is even narrower (like text related to
> gynecology)
>
>
>
> Also, lastly, is there anyone on this mailing list in Dallas region I
> would love to meet you in person.
>
>
>
> Regards,
>
> Abhishek.
>
>
>
>
>
>
>
>
>

Reply via email to