Specific annotation guidelines
This section collects detailed guidelines pertaining to distinctions and decision points found to be challenging during annotation. It is intended to be used primarily as a reference to consult to resolve particular issues rather than for reading through as a whole.
data-item vs. quality
There is a systematic potential ambiguity for qualities that can be measured and represented as data. For example, while reference to the weight of a person is in general be annotated as quality , the “weight” datum representing the result of measuring that quality is annotated as data-item.
The decision between annotating data-item or quality is based on the context of each mention (rather than e.g. its surface form). In difficult cases permitting either reading, the type data-item is preferred over the more generic quality.
data-item vs. plan
Mentions of metrics (e.g. TFIDF
) are annotated as PLAN when understood as referring to methods for calculating a value, and as data-item when understood as referring to those values themselves (see plan).
artifact vs. plan
References to systems explicitly presented as involving both hardware and software components (as opposed to software only implicitly executed by hardware) could arguably be annotated both as artifact or plan. These cases are resolved according to context: if the composite is discussed as a passive, physical object, the artifact type is applied; if its behaviour is discussed in any way, plan is assigned.
Classes and neutral collections
Many words referring to collections of individual entities are neutral in the sense that they can be used with (almost) any entity type (consider e.g. set
(neutral) vs. crowd
(non-neutral)). Separated from context, it would not be possible to determine what type to assign to such expressions. However, in context, these expressions are assigned with the same type as the entities that are members of the collection: the annotation does not differentiate between individuals and collectives (Individuals, collectives, and universals).
apply-to vs. input
In expressions such as method using X
and method based on X
, the relation between method
and X
is annotated either as apply-to or input depending on what X
is. If X
is static data (data-item or similar) input is used; if it is a method, approach or similar, apply-to is used. (See apply-to; input)
attribute vs. condition
Expressions such as document in English
are annotated with the attribute relation type: