From eb64b5e91b4e8364dc7c8ec401a5f36d145efa25 Mon Sep 17 00:00:00 2001
From: chencc33
+ Authors: Adarsh Pyarelal, Rebecca Sharp
+
+ Agent version: {agent_version}
+
+ Document generation timestamp (UTC): {date}
+
+ This is automatically generated documentation of the different entities and
+ events being extracted by the University of Arizona [Dialog
+ Agent](https://github.com/clulab/tomcat-text).
+
+ The extractions are listed below.
+
+ The full path to the leaf node in the taxonomy is represented in a hierarchical
+ structure, with each level indented from a new line. If the extraction is only
+ output as an argument of another extraction, rather than as a standalone
+ extraction, the name of the extraction is wrapped in square brackets ([]).
+
+ The argument of an extraction, if any, is listed below the extraction. If the
+ the argument is optional, the name is enclosed in square brackets, it is an
+ optional argument. The possible labels that can be assigned to the argument
+ come next, enclosed in parentheses and separated by the | character.
+ Finally, the third component of the argument line is a list of quantifiers,
+ separated by commas, and enclosed in
+ parentheses.
+
+ [Odin](https://github.com/clulab/processors) arguments can be quantified in
+ several ways. First, they may be optional (`?`), meaning that if they can be
+ added, given a particular sentence, they will be, but if not the Mention can
+ still be found. Further, they can be allowed to match multiple arguments. For
+ example, in the sentence Ferdinand ate ice cream and pop tarts., if you made a
+ rule to extract eating events and used a `+` quantifier with the food argument
+ `(food: Food+ = ...)`, then the Mention would have two separate arguments (ice
+ cream and pop tarts). The quantifiers you may see are:
+
+ ASIST Extraction Schemas
+ Format
+
+
+
+ Take for example the following block: +
+ The full path to the leaf node in the taxonomy is `Concept/LeafNode`. The + extraction has two arguments, `arg1` and `arg2`, with `arg2` being optional. + The 'arg1' argument can be labeled as either `LeafNode1` or `LeafNode2` (we + elide the full taxonomy paths here for clarity). Additionally, `arg2` has an + optional quantifier. + + The extractions are documented in the following section. +
+ ++ Authors: Adarsh Pyarelal, Rebecca Sharp + + Agent version: {agent_version} + + Document generation timestamp (UTC): {date} + + This is automatically generated documentation of the different entities and + events being extracted by the University of Arizona [Dialog + Agent](https://github.com/clulab/tomcat-text). +
++ The extractions are listed below. + + The full path to the leaf node in the taxonomy is represented in a hierarchical + structure, with each level indented from a new line. If the extraction is only + output as an argument of another extraction, rather than as a standalone + extraction, the name of the extraction is wrapped in square brackets ([]). + + The argument of an extraction, if any, is listed below the extraction. If the + the argument is optional, the name is enclosed in square brackets, it is an + optional argument. The possible labels that can be assigned to the argument + come next, enclosed in parentheses and separated by the | character. + Finally, the third component of the argument line is a list of quantifiers, + separated by commas, and enclosed in + parentheses. + + [Odin](https://github.com/clulab/processors) arguments can be quantified in + several ways. First, they may be optional (`?`), meaning that if they can be + added, given a particular sentence, they will be, but if not the Mention can + still be found. Further, they can be allowed to match multiple arguments. For + example, in the sentence Ferdinand ate ice cream and pop tarts., if you made a + rule to extract eating events and used a `+` quantifier with the food argument + `(food: Food+ = ...)`, then the Mention would have two separate arguments (ice + cream and pop tarts). The quantifiers you may see are: +
++
+ Take for example the following block: +
+ The full path to the leaf node in the taxonomy is `Concept/LeafNode`. The + extraction has two arguments, `arg1` and `arg2`, with `arg2` being optional. + The 'arg1' argument can be labeled as either `LeafNode1` or `LeafNode2` (we + elide the full taxonomy paths here for clarity). Additionally, `arg2` has an + optional quantifier. + + The extractions are documented in the following section. +
+ +- Authors: Adarsh Pyarelal, Rebecca Sharp - - Agent version: {agent_version} - - Document generation timestamp (UTC): {date} - - This is automatically generated documentation of the different entities and - events being extracted by the University of Arizona [Dialog - Agent](https://github.com/clulab/tomcat-text). -
-- The extractions are listed below. - - The full path to the leaf node in the taxonomy is represented in a hierarchical - structure, with each level indented from a new line. If the extraction is only - output as an argument of another extraction, rather than as a standalone - extraction, the name of the extraction is wrapped in square brackets ([]). - - The argument of an extraction, if any, is listed below the extraction. If the - the argument is optional, the name is enclosed in square brackets, it is an - optional argument. The possible labels that can be assigned to the argument - come next, enclosed in parentheses and separated by the | character. - Finally, the third component of the argument line is a list of quantifiers, - separated by commas, and enclosed in - parentheses. - - [Odin](https://github.com/clulab/processors) arguments can be quantified in - several ways. First, they may be optional (`?`), meaning that if they can be - added, given a particular sentence, they will be, but if not the Mention can - still be found. Further, they can be allowed to match multiple arguments. For - example, in the sentence Ferdinand ate ice cream and pop tarts., if you made a - rule to extract eating events and used a `+` quantifier with the food argument - `(food: Food+ = ...)`, then the Mention would have two separate arguments (ice - cream and pop tarts). The quantifiers you may see are: -
--
- Take for example the following block: -
- The full path to the leaf node in the taxonomy is `Concept/LeafNode`. The - extraction has two arguments, `arg1` and `arg2`, with `arg2` being optional. - The 'arg1' argument can be labeled as either `LeafNode1` or `LeafNode2` (we - elide the full taxonomy paths here for clarity). Additionally, `arg2` has an - optional quantifier. + Authors: Adarsh Pyarelal, Rebecca Sharp - The extractions are documented in the following section. + Agent version: {agent_version} + + Document generation timestamp (UTC): {date} + + This is automatically generated documentation of the different entities and + events being extracted by the University of Arizona [Dialog + Agent](https://github.com/clulab/tomcat-text). +
++ The extractions are listed below. + + The full path to the leaf node in the taxonomy is represented in a hierarchical + structure, with each level indented from a new line. If the extraction is only + output as an argument of another extraction, rather than as a standalone + extraction, the name of the extraction is wrapped in square brackets ([]). + + The argument of an extraction, if any, is listed below the extraction. If the + the argument is optional, the name is enclosed in square brackets, it is an + optional argument. The possible labels that can be assigned to the argument + come next, enclosed in parentheses and separated by the | character. + Finally, the third component of the argument line is a list of quantifiers, + separated by commas, and enclosed in + parentheses. + + [Odin](https://github.com/clulab/processors) arguments can be quantified in + several ways. First, they may be optional (`?`), meaning that if they can be + added, given a particular sentence, they will be, but if not the Mention can + still be found. Further, they can be allowed to match multiple arguments. For + example, in the sentence Ferdinand ate ice cream and pop tarts., if you made a + rule to extract eating events and used a `+` quantifier with the food argument + `(food: Food+ = ...)`, then the Mention would have two separate arguments (ice + cream and pop tarts). The quantifiers you may see are:
- -+
+ Take for example the following block: +
+ The full path to the leaf node in the taxonomy is `Concept/LeafNode`. The + extraction has two arguments, `arg1` and `arg2`, with `arg2` being optional. + The 'arg1' argument can be labeled as either `LeafNode1` or `LeafNode2` (we + elide the full taxonomy paths here for clarity). Additionally, `arg2` has an + optional quantifier. + + The extractions are documented in the following section. +
+ +- Authors: Adarsh Pyarelal, Rebecca Sharp - - Agent version: {agent_version} - - Document generation timestamp (UTC): {date} - - This is automatically generated documentation of the different entities and - events being extracted by the University of Arizona [Dialog - Agent](https://github.com/clulab/tomcat-text). -
-- The extractions are listed below. - - The full path to the leaf node in the taxonomy is represented in a hierarchical - structure, with each level indented from a new line. If the extraction is only - output as an argument of another extraction, rather than as a standalone - extraction, the name of the extraction is wrapped in square brackets ([]). - - The argument of an extraction, if any, is listed below the extraction. If the - the argument is optional, the name is enclosed in square brackets, it is an - optional argument. The possible labels that can be assigned to the argument - come next, enclosed in parentheses and separated by the | character. - Finally, the third component of the argument line is a list of quantifiers, - separated by commas, and enclosed in - parentheses. - - [Odin](https://github.com/clulab/processors) arguments can be quantified in - several ways. First, they may be optional (`?`), meaning that if they can be - added, given a particular sentence, they will be, but if not the Mention can - still be found. Further, they can be allowed to match multiple arguments. For - example, in the sentence Ferdinand ate ice cream and pop tarts., if you made a - rule to extract eating events and used a `+` quantifier with the food argument - `(food: Food+ = ...)`, then the Mention would have two separate arguments (ice - cream and pop tarts). The quantifiers you may see are: -
--
- Take for example the following block: -
- The full path to the leaf node in the taxonomy is `Concept/LeafNode`. The - extraction has two arguments, `arg1` and `arg2`, with `arg2` being optional. - The 'arg1' argument can be labeled as either `LeafNode1` or `LeafNode2` (we - elide the full taxonomy paths here for clarity). Additionally, `arg2` has an - optional quantifier. - - The extractions are documented in the following section. + The extractions are listed below.
- -+ The full path to the leaf node in the taxonomy is represented in a hierarchical + structure, with each level indented from a new line. If the extraction is only + output as an argument of another extraction, rather than as a standalone + extraction, the name of the extraction is wrapped in square brackets ([]). +
++ The argument of an extraction, if any, is listed below the extraction. If the + the argument is optional, the name is enclosed in square brackets, it is an + optional argument. The possible labels that can be assigned to the argument + come next, enclosed in parentheses and separated by the | character. + Finally, the third component of the argument line is a list of quantifiers, + separated by commas, and enclosed in + parentheses. +
++ Odin arguments can be quantified in + several ways. First, they may be optional (?), meaning that if they can be + added, given a particular sentence, they will be, but if not the Mention can + still be found. Further, they can be allowed to match multiple arguments. For + example, in the sentence Ferdinand ate ice cream and pop tarts., if you made a + rule to extract eating events and used a + quantifier with the food argument + (food: Food+ = ...), then the Mention would have two separate arguments (ice + cream and pop tarts). The quantifiers you may see are: +
+ ++
+ Take for example the following block: +
+ The full path to the leaf node in the taxonomy is Concept/LeafNode. The + extraction has two arguments, arg1 and arg2, with arg2 being optional. + The arg1 argument can be labeled as either LeafNode1 or LeafNode2 (we + elide the full taxonomy paths here for clarity). Additionally, arg2 has an + optional quantifier. + + The extractions are documented in the following section. +
+ +Note: '+' denotes the presence of child nodes; '-' indicates that the node is a leaf node with no child nodes.
""" html_code_part2 = write_tree_dict_html(tree_dict, level=0) From 7edb7c65f07576479565b3cb9c9f3a43ae6ebacc Mon Sep 17 00:00:00 2001 From: chencc33+ The extractions are listed below. +
++ The full path to the leaf node in the taxonomy is represented in a hierarchical + structure, with each level indented from a new line. If the extraction is only + output as an argument of another extraction, rather than as a standalone + extraction, the name of the extraction is wrapped in square brackets ([]). +
++ The argument of an extraction, if any, is listed below the extraction. If the + the argument is optional, the name is enclosed in square brackets, it is an + optional argument. The possible labels that can be assigned to the argument + come next, enclosed in parentheses and separated by the | character. + Finally, the third component of the argument line is a list of quantifiers, + separated by commas, and enclosed in + parentheses. +
++ Odin arguments can be quantified in + several ways. First, they may be optional (?), meaning that if they can be + added, given a particular sentence, they will be, but if not the Mention can + still be found. Further, they can be allowed to match multiple arguments. For + example, in the sentence "Ferdinand ate ice cream and pop tarts."", if you made a + rule to extract eating events and used a + quantifier with the food argument + (food: Food+ = ...), then the Mention would have two separate arguments (ice + cream and pop tarts). The quantifiers you may see are: +
++
+ Take for example the following block: +
+ The full path to the leaf node in the taxonomy is Concept/LeafNode. + The extraction has two arguments, + arg1 and arg2, + with arg2 being optional. + The arg1 argument can be labeled as either + LeafNode1 or LeafNode2 (we + elide the full taxonomy paths here for clarity). Additionally, arg2 has an + optional quantifier. + + The extractions are documented in the following section. +
+ +Note: '+' denotes the presence of child nodes; '-' indicates that the node is a leaf node with no child nodes.
+ +