timjogorman / richereventdescription Goto Github PK
View Code? Open in Web Editor NEWA living document with the guidelines for RED annotation, and any scripts useful for working with RED documents
A living document with the guidelines for RED annotation, and any scripts useful for working with RED documents
We talked about the specific phenomenon of "imperative" forms. What we settled on in the call is that:
This whole issue is flush with this other set of things like expression of desire or wanting, like "I asked him to leave". We're try to be consistent about treating those as HYPOTHETICAL. This might sometimes feel inconsistent, but I'm hoping that we can follow that distinction.
If you run into instances where Imperatives seem more like HYPOTHETICAL, or when the expressions of desire/ urges/ requests seem to be better as ACTUAL or UNCERTAIN, mention them here -- we want to get a sense of whether this is a good boundary here.
In THYME, we had the general tradition of "don't grab numbers", mostly as a justification for ignoring the numbers in things like "Platelets: 600".
In general, we are going to shift to explicitly allowing you to grab numbers when they stand for an ellided head that is referential. So "100s were killed" stands in for the victims, and should be coreferential with them, etc.
This brings up the awkward question - both in whether to mark it and what span to use -- for something like "$100,000". If "1,000 dollars" was referential, you would grab just "dollars", but [$]1,000 seems very unintuitive. Instead, just grab the whole number and dollar value when referential, as in [$1000].
An example brought up in the call of adjectives that are NOT eventive:
Tall and tan and young and lovely, the girl from Ipanema goes Ew, what�s that smell?�
We talked more about this distinction for pertainyms, particularly country ones like "French" and "American". The hard part is that it's quite hard to distinguish when something being mentioned is "really the entity" vs some general mention.
The current guidelines state "when the actual named entity is not being evoked itself, but merely some stereotype, origin or style of that entity, then ignore it", with the examples of things not to use being
We still want to avoid marking those two examples as entities, but came up with a rule that is hopefully more distinguishable: if a pertainym like "american X" can be rephrased was "in the style of X", "X-style", like "american-style music" or "indian-style food", then it is NOT an entity, but if it implies more concrete relationships like "located in America", "manufactured in America", etc., then it DOES count as a mention of that country.
We've talked a great deal recently about the range of things that appear to be either an event or an entity based upon context, or that appear to have both an event component AND an entity component. We've settled upon being pretty deterministic about them, based on type.
-We are going to default to EVENT whenever you possibly can
For discerning the span of annotations when there are possessives, we've followed this general "treebank" rule that you don't grab possessives when separated by an 's, as in [John]'s eating of the plums, but that we DO grab the whole thing for fused possessives like "his" or "their".
Someone brought up the question of how we want to handle 's when used for plurals, as in "in the 50's". For these, we DO want to grab the whole thing, so "[50's]".
A very minor comment: at least in the LDC-released annotation, it appears that the "precondition" causal type suffix is PRECONDITION
, not PRECONDITIONS
(which appears in the annotation guide).
This is an archaic argument left over from when the scholastic 'the teacher failed 10 students' sense was included in this roleset. It shouldn't be possible with the existing roleset. We should be able to delete it, and any instances remaining in back annotation should be errors (or movable to fail.02)
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.