plan: information that can be realized as a process
Scope
References to methods, algorithms, experimental designs, data format specifications, programming languages, software, informal sequences of instructions, and similar information entities that can be realized as processes are annotated as plan, including collections and universals of such entities.
Syntactic constraints
Names and nominal mentions (see Span annotation: Name mention annotation and Nominal mention annotation)
Examples
-
system
implementation of the system T1 PLAN 0 14 implementation T2 PLAN 22 28 system -
algorithm
the algorithm makes lexical chains T1 PLAN 4 13 algorithm T2 PROCESS 14 19 makes T3 DATA-ITEM 20 34 lexical chains -
voting rules
match for all voting rules T1 PROCESS 0 5 match T2 QUANTITY 10 13 all T3 PLAN 14 26 voting rules -
clustering algorithm
clustering algorithm was applied T1 PLAN 0 20 clustering algorithm T2 PROCESS 25 32 applied -
multimedia system
evaluate on a multimedia system T1 PROCESS 0 8 evaluate T2 PLAN 13 31 multimedia system -
Bayesian games
the domain is modeled as Bayesian games T1 DOMAIN 4 10 domain T2 PROCESS 14 21 modeled T3 PLAN 24 39 Bayesian games -
CR framework
parameter settings within the CR framework T1 DATA-ITEM 0 18 parameter settings T2 PLAN 30 42 CR framework -
classification method
performance of the classification method T1 QUALITY 0 11 performance T2 PLAN 19 40 classification method -
formal model
extend a formal model T1 PROCESS 0 6 extend T2 PLAN 8 21 formal model
Further details
In text, there is often ambiguity between methods (and similar)
conceived of in the abstract, described in natural language, presented
in (pseudo)code on paper, implemented in a programming language in a
computer, compiled into machine code, etc. plan annotation does not require this ambiguity to be
resolved: statements such as [our] method
are annotated as plan regardless of which of the above they
refer to.
Note: 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 Specific annotation guidelines: DATA-ITEM vs. PLAN).
References
The semantic scope of plan annotation matches that of directive information entityIAO: “An information content entity whose concretizations indicate to their bearer how to realize them in a process.” [2] (see Ontological basis: Information entities). Contrast process and data-item, consider plan-or-process for ambiguous cases.