Thanks Sean and Tim for the background & code on these annotators & models.
Just looking at how the EventTimeRelationAnnotator works, I think the
internal representation would be a bit different, but I get the gist of it
for sure. Unless I'm using outdated code The "actual data" is captured in
Oops, looking at what I jut wrote:
edgeNodes.put( relation.getCategory(), new Pair( argument1, argument2 )
);
would definitely NOT work. This might be better, though a little more tedious:
final Map edgeTypeCounts = new HashMap<>();
final Map> edgeNodes = new Hash
Hi Peter,
To your question:
>there isn't yet much code that pulls these relations out in any user-friendly
>way?
the answer is mostly no. The relation-related code in ctakes is mostly for
experimentation and not utilization.
Annotations/Events and Relations are translated in a few places into
Hi Peter,
I guess you're asking why there is annotator code for all the relations but
only released models for location_of and degree_of (severity)? The simple
reason is those are the only two that we felt were accurate enough to release.
We had an annotated training corpus with all the relation
Hi Sean, I've been doing a bit of reading on propbanks, framesets, etc in
relation to what I'm seeing in the CAS when I turn on some of the relation
extractors that do work (in contrast to the ones I mentioned before that
are missing a model).
Is it safe to say that these extractors are mostly
Hi (probably Sean), are the default model.jars for the
*CausesBringsAboutRelationExtractorAnnotator* and the
*ManagesTreatsRelationExtractorAnnotator* not part of the cTakes
sources?I looked through the source at all pipers and all unit tests
and on the net and I didn't find references to the
