ACL-OCL / Base_JSON /prefixL /json /law /2021.law-1.11.json
Benjamin Aw
Add updated pkl file v3
6fa4bc9
{
"paper_id": "2021",
"header": {
"generated_with": "S2ORC 1.0.0",
"date_generated": "2023-01-19T12:11:08.567486Z"
},
"title": "Simplifying annotation of intersections in time normalization annotation: exploring syntactic and semantic validation",
"authors": [
{
"first": "Peiwen",
"middle": [],
"last": "Su",
"suffix": "",
"affiliation": {
"laboratory": "",
"institution": "University of Arizona Tucson",
"location": {
"region": "AZ",
"country": "USA"
}
},
"email": "[email protected]"
},
{
"first": "Steven",
"middle": [],
"last": "Bethard",
"suffix": "",
"affiliation": {
"laboratory": "",
"institution": "University of Arizona Tucson",
"location": {
"region": "AZ",
"country": "USA"
}
},
"email": "[email protected]"
}
],
"year": "",
"venue": null,
"identifiers": {},
"abstract": "While annotating normalized times in food security documents, we found that the semantically compositional annotation for time normalization (SCATE) scheme required several near-duplicate annotations to get the correct semantics for expressions like Nov. 7th to 11th 2021. To reduce this problem, we explored replacing SCATE's SUB-INTERVAL property with a SUPER-INTERVAL property, that is, making the smallest units (e.g., 7th and 11th) rather than the largest units (e.g., 2021) the heads of the intersection chains. To ensure that the semantics of annotated time intervals remained unaltered despite our changes to the syntax of the annotation scheme, we applied several different techniques to validate our changes. These validation techniques detected and allowed us to resolve several important bugs in our automated translation from SUB-INTERVAL to SUPER-INTERVAL syntax.",
"pdf_parse": {
"paper_id": "2021",
"_pdf_hash": "",
"abstract": [
{
"text": "While annotating normalized times in food security documents, we found that the semantically compositional annotation for time normalization (SCATE) scheme required several near-duplicate annotations to get the correct semantics for expressions like Nov. 7th to 11th 2021. To reduce this problem, we explored replacing SCATE's SUB-INTERVAL property with a SUPER-INTERVAL property, that is, making the smallest units (e.g., 7th and 11th) rather than the largest units (e.g., 2021) the heads of the intersection chains. To ensure that the semantics of annotated time intervals remained unaltered despite our changes to the syntax of the annotation scheme, we applied several different techniques to validate our changes. These validation techniques detected and allowed us to resolve several important bugs in our automated translation from SUB-INTERVAL to SUPER-INTERVAL syntax.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Abstract",
"sec_num": null
}
],
"body_text": [
{
"text": "Time normalization is the task of translating natural language expressions of time, e.g., three days ago, to computer-readable forms, e.g., 2021-11-04. Time normalization is an important component of applications like monitoring patient symptoms (Lin et al., 2015) , matching news events across languages (Vossen et al., 2016) , and studying datebased literature trends (Fischer and Str\u00f6tgen, 2015) . As part of a larger project studying the causes and effects of food insecurity, we were interested in annotating normalized times in this highly timesensitive domain.",
"cite_spans": [
{
"start": 246,
"end": 264,
"text": "(Lin et al., 2015)",
"ref_id": "BIBREF7"
},
{
"start": 305,
"end": 326,
"text": "(Vossen et al., 2016)",
"ref_id": "BIBREF10"
},
{
"start": 370,
"end": 398,
"text": "(Fischer and Str\u00f6tgen, 2015)",
"ref_id": "BIBREF3"
}
],
"ref_spans": [],
"eq_spans": [],
"section": "Introduction",
"sec_num": "1"
},
{
"text": "Several schemes have been proposed for annotating normalized times. TimeML (Pustejovsky et al., 2003; ISO, 2012) primarily focuses on times that can be described as a prefix of YYYY-MM-DDTHH:MM:SS, including relative time expressions like next Monday, but excluding time expressions like the past three summers that refer to more than one time interval. The semantically compositional annotation for time normalization (SCATE; Bethard and Parker, 2016) scheme breaks time expressions down into individual temporal operators like NEXT or BETWEEN, and can therefore cover a wider variety of time expressions than TimeML. The Time Event Ontology (TEO; Li et al., 2020) draws ideas from both TimeML and SCATE, to provide a simplified annotation scheme specifically targeted at clinical notes.",
"cite_spans": [
{
"start": 75,
"end": 101,
"text": "(Pustejovsky et al., 2003;",
"ref_id": "BIBREF9"
},
{
"start": 102,
"end": 112,
"text": "ISO, 2012)",
"ref_id": "BIBREF4"
},
{
"start": 427,
"end": 452,
"text": "Bethard and Parker, 2016)",
"ref_id": "BIBREF1"
},
{
"start": 649,
"end": 665,
"text": "Li et al., 2020)",
"ref_id": "BIBREF6"
}
],
"ref_spans": [],
"eq_spans": [],
"section": "Introduction",
"sec_num": "1"
},
{
"text": "Because the SCATE scheme covered the widest variety of time expressions, we selected this scheme for annotating normalized times in food security documents. We annotated 17 documents (22K words), producing 2305 time annotations, and achieved an acceptable inter-annotator agreement of 0.808 F1. However, during the process we noticed that to get the correct temporal semantics of expressions like Nov. 7th to 11th 2021, we had to add many near-duplicate annotations. Under the SCATE scheme, to get this expression interpreted correctly as [2021-11-07 00:00:00, 2021-11-12 00:00:00), two MONTH-OF-YEAR annotations are needed on Nov. and two YEAR annotations are needed on 2021, as shown in fig. 1 (top). These duplicate annotations are necessary because the BETWEEN needs two intervals, one for 2021-11-07 and one for 2021-11-11, and a YEAR with a chain of SUB-INTERVAL links can represent only a single interval. For example, the top-most YEAR in the figure, based on its chain of SUB-INTERVAL links, is interpreted as 2021-11-11.",
"cite_spans": [],
"ref_spans": [
{
"start": 689,
"end": 695,
"text": "fig. 1",
"ref_id": "FIGREF0"
}
],
"eq_spans": [],
"section": "Introduction",
"sec_num": "1"
},
{
"text": "Because these types of time expressions were common in our food security documents, we explored a possible change to the SCATE scheme which would replace SUB-INTERVAL links with SUPER-INTERVAL links. In essence, we would reverse the links in the chains, removing the need for the additional annotations, as shown in is linked to a different day and therefore cannot be shared, in the SUPER-INTERVAL version the MONTH-OF-YEAR can be shared because it is linked only to the YEAR, which is also shared.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Introduction",
"sec_num": "1"
},
{
"text": "Our proposed change to SCATE is purely syntactic; if implemented correctly, it should not change the semantics of any complete time expression. But SUB-INTERVAL is extremely common in SCATEannotated documents, such as the SemEval 2018 Task 6 annotated corpus Laparra et al. (2018) , so the conversion from SUB-INTERVAL to SUPER-INTERVAL would have to be automatic, not manual. We thus designed an automatic conversion tool, and a series of validations to ensure that our conversions behaved as expected.",
"cite_spans": [
{
"start": 259,
"end": 280,
"text": "Laparra et al. (2018)",
"ref_id": "BIBREF5"
}
],
"ref_spans": [],
"eq_spans": [],
"section": "Introduction",
"sec_num": "1"
},
{
"text": "Because SCATE, in addition to defining a set of annotations syntactically, also defines a formal semantics for each annotation, we were able to validate our tool in two different ways: syntactically, ensuring that the XML annotations were valid SCATE annotations and lost no information, and semantically, ensuring that the time intervals inferrable from the SCATE annotations were identical before and after the conversion.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Introduction",
"sec_num": "1"
},
{
"text": "2 Anafora XML to LabelStudio JSON SCATE was originally implemented in the XML format of the Anafora annotation tool (Chen and Styler, 2013) , but that tool has not been actively maintained since 2018. To allow easy visualiza-tion of our annotations, we translated the SCATE scheme into a LabelStudio 1 config, and a corresponding LabelStudio JSON format.",
"cite_spans": [
{
"start": 116,
"end": 139,
"text": "(Chen and Styler, 2013)",
"ref_id": "BIBREF2"
}
],
"ref_spans": [],
"eq_spans": [],
"section": "Introduction",
"sec_num": "1"
},
{
"text": "To convert between Anafora XML and Label-Studio JSON, we created an XML-to-JSON script that translated each <entity> into a JSON object for its <type> and a JSON object for each of its <properties>. The structure of these JSON objects follows the LabelStudio requirements. The objects for type and text-based properties have an id field, give the name via from_name, and give the span and value in the value sub-object. The objects for link-based properties have from_id and to_id fields and give the name via labels. Figure 2 shows a sample of the original Anafora XML and the corresponding LabelStudio JSON, as well as a screenshot of LabelStudio visualizing the SCATE annotations.",
"cite_spans": [],
"ref_spans": [
{
"start": 518,
"end": 526,
"text": "Figure 2",
"ref_id": "FIGREF1"
}
],
"eq_spans": [],
"section": "Introduction",
"sec_num": "1"
},
{
"text": "Before implementing the proposed SUB-INTERVAL to SUPER-INTERVAL conversion in the JSON files, we tested our Anafora XML to LabelStudio JSON conversion. We first implemented a JSON-to-XML script designed to be an inverse of the XML-to-JSON script described in section 2, which collected all JSON objects for each id and merged them into a single <entity>. We then tested that the composition of the two scripts (i.e., XML-to-JSON-to-<entity> <id>51@[email protected]@gold</id> <span>29,31</span> <type>Month-Of-Year</type> <parentsType>Repeating-Interval</parentsType> <properties> <Type>January</Type> <Sub-Interval>50@[email protected]@gold </Sub-Interval> </properties> </entity> { \"value\": { \"start\": 29, \"end\": 31, \"labels\": [\"Month-Of-Year\"]}, \"id\": \"51@[email protected]@gold\", \"from_name\": \"type\", }, { \"value\": { \"start\": 29, \"end\": 31, \"choices\": [\"January\"]}, \"id\": \"51@[email protected]@gold\", \"from_name\": \"Month-Of-Year-type\", }, { \"from_id\": \"51@[email protected]@gold\", \"to_id\": \"50@[email protected]@gold\", \"type\": \"relation\", \"labels\": [\"Sub-Interval\"] }, <id>571@e@ID159_clinic_470@gold</id> <span>6491,6495</span> <type>After</type> <parentsType>Operator</parentsType> <properties> <Semantics>Interval-Not-Included</Semantics> <Interval-Type>Link</Interval-Type> <Interval>326@e@ID159_clinic_470@gold</Interval> </properties> </entity> Figure 3 : An annotation error. No <entity> in the document has id 326@e@ID159_clinic_470@gold. The phrase Post spans the offsets 6491 to 6495 within the phrase Postoperative. It is likely that an annotation over the operative was lost in the original annotations. XML) produced Anafora XML that was equivalent to the original Anafora XML. Performing this type of syntactic validation revealed a number of errors.",
"cite_spans": [],
"ref_spans": [
{
"start": 1391,
"end": 1399,
"text": "Figure 3",
"ref_id": null
}
],
"eq_spans": [],
"section": "Validating XML-to-JSON",
"sec_num": "3"
},
{
"text": "Annotation errors We found 43 cases in the SemEval 2018 Task 6 annotated corpus where there were errors in the original Anafora XML. For example, fig. 3 shows an <entity> whose <Interval> appears to link to another entity, but the document contains no entity with id 326@e@ID159_clinic_470@gold. These were revealed as exceptions in the XML-to-JSON script when it attempted to look up the non-existing entity.",
"cite_spans": [],
"ref_spans": [
{
"start": 146,
"end": 152,
"text": "fig. 3",
"ref_id": null
}
],
"eq_spans": [],
"section": "Validating XML-to-JSON",
"sec_num": "3"
},
{
"text": "Properties with multiple values Almost all SCATE annotations allow only a single value for each property. However, our XML-to-JSON-to-XML validation revealed that a small number of annotations in the SemEval 2018 Task 6 corpus had properties with multiple values. For example, as shown in fig. 4 , and in the phrase Mondays and Tuesdays was annotated as a UNION with two <Repeating-Intervals> arguments, Mon-<entity> <id>130@[email protected]@gold</id> <span>934,937</span> <type>Union</type> <parentsType>Operator</parentsType> <properties> <Repeating-Intervals>111@[email protected]@gold </Repeating-Intervals> <Repeating-Intervals>112@[email protected]@gold </Repeating-Intervals> </properties> </entity> days and Tuesdays. Our original code assumed one value per property, resulting in missing links in the generated XML. We resolved the issue by ensuring that properties with multiple values resulted in multiple JSON objects instead of just one.",
"cite_spans": [],
"ref_spans": [
{
"start": 289,
"end": 295,
"text": "fig. 4",
"ref_id": "FIGREF2"
}
],
"eq_spans": [],
"section": "Validating XML-to-JSON",
"sec_num": "3"
},
{
"text": "Annotations with multiple spans Almost all SCATE annotations are over just a single, continuous span of text. However, our XML-to-JSONto-XML validation revealed that a small number of annotations in the SemEval 2018 Task 6 corpus had multiple spans. For example, in fig. 5 , the event status, stable (an event from a clinical note that describes the state of the patient) was annotated to exclude the comma and space characters. Similar problems arise in our food security data, where expressions like Kiremt 2016 rainy season needs a discontinuous span for the season Kiremt . . . rainy season. We resolved this issue by creating an extra JSON object for each additional span, where the ID is suffixed with continued to allow for easy reconstruction of the multi-span annotation. <entity> <id>66@e@ID017_clinic_049@gold</id> <span>748,754;756,762</span> <type>Event</type> <parentsType>Other</parentsType> </entity> Figure 5 : An annotation with multiple spans. The phrase status, stable spans the offsets 748 to 762, but the comma and space are excluded from the annotation.",
"cite_spans": [],
"ref_spans": [
{
"start": 266,
"end": 272,
"text": "fig. 5",
"ref_id": null
},
{
"start": 917,
"end": 925,
"text": "Figure 5",
"ref_id": null
}
],
"eq_spans": [],
"section": "Validating XML-to-JSON",
"sec_num": "3"
},
{
"text": "Having validated our XML-to-JSON conversion, we implemented our SUB-INTERVAL to SUPER-INTERVAL conversion. Our initial implementation simply changed the labels from Sub-Interval to Super-Interval and swapped the from_id and to_id fields.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Validating Sub-to-Super-Interval",
"sec_num": "4"
},
{
"text": "To perform semantic validation of this conversion, we took advantage of the interpretation API provided by Bethard and Parker (2016) 2 , which takes annotations as input and produces time intervals as output. For example, the BETWEEN annotation in fig. 1 would be interpreted as the interval [2021-11-07 00:00:00, 2021-11-12 00:00:00). Since the API requires Anafora XML, we used our JSON-to-XML script to convert our SUPER-INTERVAL JSON into SUPER-INTERVAL XML.",
"cite_spans": [
{
"start": 107,
"end": 132,
"text": "Bethard and Parker (2016)",
"ref_id": "BIBREF1"
}
],
"ref_spans": [
{
"start": 248,
"end": 254,
"text": "fig. 1",
"ref_id": "FIGREF0"
}
],
"eq_spans": [],
"section": "Validating Sub-to-Super-Interval",
"sec_num": "4"
},
{
"text": "To check if our syntactic changes to the annotation scheme maintained the intended semantics, we paired up each annotation in the original SUB-INTERVAL XML files with the corresponding annotation in the newly generated SUPER-INTERVAL XML files, and tested that the paired annotations both resulted in the same time intervals. Performing this type of semantic validation revealed a number of errors.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Validating Sub-to-Super-Interval",
"sec_num": "4"
},
{
"text": "Mid-chain entities The validation showed that the interpretation of entities in the middle of a SUB-INTERVAL chain changed with the SUPER-INTERVAL conversion. For example, the Nov. of fig. 1 (top) is intersected with 7th via its SUB-INTERVAL link, and is therefore interpreted as all November 7th intervals on the timeline. On the other hand, the Nov. of fig. 1 (bottom) is intersected with 2021 via its SUPER-INTERVAL link, and is therefore interpreted as the single interval November 2021. This was a desirable consequence of the conversion, since these partial interpretations are necessary to allow re-use of expressions like Nov. in Nov. 7th to 11th. We therefore changed 2 https://github.com/clulab/timenorm/ our semantic validation code to allow mismatches between mid-chain entities.",
"cite_spans": [],
"ref_spans": [
{
"start": 184,
"end": 196,
"text": "fig. 1 (top)",
"ref_id": "FIGREF0"
},
{
"start": 355,
"end": 370,
"text": "fig. 1 (bottom)",
"ref_id": "FIGREF0"
}
],
"eq_spans": [],
"section": "Validating Sub-to-Super-Interval",
"sec_num": "4"
},
{
"text": "Entities with chain arguments Our simple swapping of from_id and to_id turned out to be insufficent for entities that are not part of a SUB-INTERVAL chain, but take one as an argument. For example, the BETWEEN in fig. 1 (top) has chains as its START-INTERVAL and END-INTERVAL arguments. In the SUB-INTERVAL encoding, these chains are represented by YEARs, but in the SUPER-INTERVAL encoding, these chains are represented by DAY-OF-MONTHs. We resolved this issue by finding entities with chain arguments, and replacing the root of the SUB-INTERVAL chain (i.e., the largest time unit) with the root of the SUPER-INTERVAL chain (i.e., the smallest time unit).",
"cite_spans": [],
"ref_spans": [
{
"start": 213,
"end": 225,
"text": "fig. 1 (top)",
"ref_id": "FIGREF0"
}
],
"eq_spans": [],
"section": "Validating Sub-to-Super-Interval",
"sec_num": "4"
},
{
"text": "The change from SUB-INTERVAL to SUPER-INTERVAL achieved our primary goal, successfully removing 69 near-duplicate annotations in our food security corpus, without changing the semantics of any time expression. There was only one place where the switch caused a new nearduplicate annotation to be added: Meher 2016/17. The Meher here refers to two different seasons, May to September 2016 and May to September 2017. With SUB-INTERVALs, both 2016 and 17 could link to the same Meher SEASON-OF-YEAR, but with SUPER-INTERVALs, there must be two SEASON-OF-YEARs annotated, each pointing their SUPER-INTERVAL to exactly one of 2016 or 17. We nonetheless consider the experiment a success: 69 near-duplicates removed, at the cost of just 1 near-duplicate added.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Discussion",
"sec_num": "5"
},
{
"text": "In terms of validation strategies, we found it helpful to be working with an annotation scheme that had both a syntactic specification of how annotations should be applied to words in the text, and a formal semantic interpretation that converted the annotations to explicit intervals on the timeline. This allowed us to change the syntax of the annotation scheme, while making sure that we did not unintentionally change the semantics of the annotations. Having both a syntactic specification and a formal semantic interpretation is uncommon in annotation schemes. At one end of the spectrum are purely syntactic annotation schemes, like Universal Dependencies (UD; Nivre et al., 2020) , with no formal semantic interpretation at all. At the other end of the spectrum are purely semantic annota-tion schemes, like abstract meaning representation (AMR; Banarescu et al., 2013) where only the formal logic-like interpretation is annotated, with no explicit links to individual words of the original text. Our experience was that having both a syntactic and semantic specification made it easier to apply and validate improvements to the annotation scheme.",
"cite_spans": [
{
"start": 666,
"end": 685,
"text": "Nivre et al., 2020)",
"ref_id": "BIBREF8"
},
{
"start": 852,
"end": 875,
"text": "Banarescu et al., 2013)",
"ref_id": "BIBREF0"
}
],
"ref_spans": [],
"eq_spans": [],
"section": "Discussion",
"sec_num": "5"
},
{
"text": "All code produced during this work can be found at https://github.com/clulab/timenorm/.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Discussion",
"sec_num": "5"
},
{
"text": "https://labelstud.io/",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "",
"sec_num": null
}
],
"back_matter": [
{
"text": "Research reported in this publication was supported by the National Library of Medicine of the National Institutes of Health under Award Number R01LM010090. The content is solely the responsibility of the authors and does not necessarily represent the official views of the National Institutes of Health.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Acknowledgements",
"sec_num": null
},
{
"text": " Figure A1 shows an extended example of what SUB-INTERVAL chains look like in both Anafora XML and LabelStudio JSON. <entity> <id>50@[email protected]@gold</id> <span>31,33</span> <type>Day-Of-Month</type> <parentsType>Repeating-Interval</parentsType> <properties> <Value>14</Value> <Sub-Interval></Sub-Interval> <Number></Number> <Modifier></Modifier> </properties> </entity> <entity> <id>51@[email protected]@gold</id> <span>29,31</span> <type>Month-Of-Year</type> <parentsType>Repeating-Interval</parentsType> <properties> <Type>January</Type> <Sub-Interval>50@[email protected]@gold </Sub-Interval> <Number></Number> <Modifier></Modifier> </properties> </entity> <entity> <id>52@[email protected]@gold</id> <span>25,29</span> <type>Year</type> <parentsType>Interval</parentsType> <properties> <Value>1998</Value> <Sub-Interval>51@[email protected]@gold </Sub-Interval> <Modifier></Modifier> </properties> </entity> { \"value\": { \"start\": 31, \"end\": 33, \"labels\": [\"Day-Of-Month\"] }, \"id\": \"50@[email protected]@gold\", \"from_name\": \"type\", \"to_name\": \"text\", \"type\": \"labels\" }, { \"value\": { \"start\": 31, \"end\": 33, \"text\": [\"14\"] }, \"id\": \"50@[email protected]@gold\", \"from_name\": \"Day-Of-Month-value\", \"to_name\": \"text\", \"type\": \"textarea\" }, { \"value\": { \"start\": 29, \"end\": 31, \"labels\": [\"Month-Of-Year\"] }, \"id\": \"51@[email protected]@gold\", \"from_name\": \"type\", \"to_name\": \"text\", \"type\": \"labels\" }, { \"value\": { \"start\": 29, \"end\": 31, \"choices\": [\"January\"] }, \"id\": \"51@[email protected]@gold\", \"from_name\": \"Month-Of-Year-type\", \"to_name\": \"text\", \"type\": \"choices\" }, { \"from_id\": \"51@[email protected]@gold\", \"to_id\": \"50@[email protected]@gold\", \"type\": \"relation\", \"labels\": [\"Sub-Interval\"] }, { \"value\": { \"start\": 25, \"end\": 29, \"labels\": [\"Year\"] }, \"id\": \"52@[email protected]@gold\", \"from_name\": \"type\", \"to_name\": \"text\", \"type\": \"labels\" }, { \"value\": { \"start\": 25, \"end\": 29, \"text\": [\"1998\"] }, \"id\": \"52@[email protected]@gold\", \"from_name\": \"Year-value\", \"to_name\": \"text\", \"type\": \"textarea\" }, { \"from_id\": \"52@[email protected]@gold\", \"to_id\": \"51@[email protected]@gold\", \"type\": \"relation\", \"labels\": [\"Sub-Interval\"] } Figure A1 : Example Anafora XML format (left) and LabelStudio JSON format (right).",
"cite_spans": [],
"ref_spans": [
{
"start": 1,
"end": 10,
"text": "Figure A1",
"ref_id": null
},
{
"start": 2246,
"end": 2255,
"text": "Figure A1",
"ref_id": null
}
],
"eq_spans": [],
"section": "A Appendix",
"sec_num": null
}
],
"bib_entries": {
"BIBREF0": {
"ref_id": "b0",
"title": "Abstract Meaning Representation for sembanking",
"authors": [
{
"first": "Laura",
"middle": [],
"last": "Banarescu",
"suffix": ""
},
{
"first": "Claire",
"middle": [],
"last": "Bonial",
"suffix": ""
},
{
"first": "Shu",
"middle": [],
"last": "Cai",
"suffix": ""
},
{
"first": "Madalina",
"middle": [],
"last": "Georgescu",
"suffix": ""
},
{
"first": "Kira",
"middle": [],
"last": "Griffitt",
"suffix": ""
},
{
"first": "Ulf",
"middle": [],
"last": "Hermjakob",
"suffix": ""
},
{
"first": "Kevin",
"middle": [],
"last": "Knight",
"suffix": ""
},
{
"first": "Philipp",
"middle": [],
"last": "Koehn",
"suffix": ""
},
{
"first": "Martha",
"middle": [],
"last": "Palmer",
"suffix": ""
},
{
"first": "Nathan",
"middle": [],
"last": "Schneider",
"suffix": ""
}
],
"year": 2013,
"venue": "Proceedings of the 7th Linguistic Annotation Workshop and Interoperability with Discourse",
"volume": "",
"issue": "",
"pages": "178--186",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Laura Banarescu, Claire Bonial, Shu Cai, Madalina Georgescu, Kira Griffitt, Ulf Hermjakob, Kevin Knight, Philipp Koehn, Martha Palmer, and Nathan Schneider. 2013. Abstract Meaning Representation for sembanking. In Proceedings of the 7th Linguis- tic Annotation Workshop and Interoperability with Discourse, pages 178-186, Sofia, Bulgaria. Associa- tion for Computational Linguistics.",
"links": null
},
"BIBREF1": {
"ref_id": "b1",
"title": "A semantically compositional annotation scheme for time normalization",
"authors": [
{
"first": "Steven",
"middle": [],
"last": "Bethard",
"suffix": ""
},
{
"first": "Jonathan",
"middle": [],
"last": "Parker",
"suffix": ""
}
],
"year": 2016,
"venue": "Proceedings of the Tenth International Conference on Language Resources and Evaluation (LREC'16)",
"volume": "",
"issue": "",
"pages": "3779--3786",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Steven Bethard and Jonathan Parker. 2016. A seman- tically compositional annotation scheme for time normalization. In Proceedings of the Tenth Inter- national Conference on Language Resources and Evaluation (LREC'16), pages 3779-3786, Portoro\u017e, Slovenia. European Language Resources Associa- tion (ELRA).",
"links": null
},
"BIBREF2": {
"ref_id": "b2",
"title": "Anafora: A webbased general purpose annotation tool",
"authors": [
{
"first": "Wei-Te",
"middle": [],
"last": "Chen",
"suffix": ""
},
{
"first": "Will",
"middle": [],
"last": "Styler",
"suffix": ""
}
],
"year": 2013,
"venue": "Proceedings of the 2013 NAACL HLT Demonstration Session",
"volume": "",
"issue": "",
"pages": "14--19",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Wei-Te Chen and Will Styler. 2013. Anafora: A web- based general purpose annotation tool. In Proceed- ings of the 2013 NAACL HLT Demonstration Ses- sion, pages 14-19, Atlanta, Georgia. Association for Computational Linguistics.",
"links": null
},
"BIBREF3": {
"ref_id": "b3",
"title": "When Does (German) Literature Take Place? On the Analysis of Temporal Expressions in Large Corpora",
"authors": [
{
"first": "Frank",
"middle": [],
"last": "Fischer",
"suffix": ""
},
{
"first": "Jannik",
"middle": [],
"last": "Str\u00f6tgen",
"suffix": ""
}
],
"year": 2015,
"venue": "Proceedings of DH 2015: Annual Conference of the Alliance of Digital Humanities Organizations",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Frank Fischer and Jannik Str\u00f6tgen. 2015. When Does (German) Literature Take Place? On the Analysis of Temporal Expressions in Large Corpora. In Pro- ceedings of DH 2015: Annual Conference of the Alliance of Digital Humanities Organizations, vol- ume 6, Sydney, Australia.",
"links": null
},
"BIBREF4": {
"ref_id": "b4",
"title": "Language resource management -semantic annotation framework (semaf) -part 1: Time and events (semaf-time, iso-timeml)",
"authors": [
{
"first": "",
"middle": [],
"last": "Iso",
"suffix": ""
}
],
"year": 2012,
"venue": "",
"volume": "",
"issue": "",
"pages": "24617--24618",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "ISO. 2012. Language resource management -seman- tic annotation framework (semaf) -part 1: Time and events (semaf-time, iso-timeml). Technical report, ISO. 24617-1:2012.",
"links": null
},
"BIBREF5": {
"ref_id": "b5",
"title": "SemEval 2018 task 6: Parsing time normalizations",
"authors": [
{
"first": "Egoitz",
"middle": [],
"last": "Laparra",
"suffix": ""
},
{
"first": "Dongfang",
"middle": [],
"last": "Xu",
"suffix": ""
},
{
"first": "Ahmed",
"middle": [],
"last": "Elsayed",
"suffix": ""
},
{
"first": "Steven",
"middle": [],
"last": "Bethard",
"suffix": ""
},
{
"first": "Martha",
"middle": [],
"last": "Palmer",
"suffix": ""
}
],
"year": 2018,
"venue": "Proceedings of The 12th International Workshop on Semantic Evaluation",
"volume": "",
"issue": "",
"pages": "88--96",
"other_ids": {
"DOI": [
"10.18653/v1/S18-1011"
]
},
"num": null,
"urls": [],
"raw_text": "Egoitz Laparra, Dongfang Xu, Ahmed Elsayed, Steven Bethard, and Martha Palmer. 2018. SemEval 2018 task 6: Parsing time normalizations. In Proceedings of The 12th International Workshop on Semantic Evaluation, pages 88-96, New Orleans, Louisiana. Association for Computational Linguistics.",
"links": null
},
"BIBREF6": {
"ref_id": "b6",
"title": "Time event ontology (TEO): to support semantic representation and reasoning of complex temporal relations of clinical events",
"authors": [
{
"first": "Fang",
"middle": [],
"last": "Li",
"suffix": ""
},
{
"first": "Jingcheng",
"middle": [],
"last": "Du",
"suffix": ""
},
{
"first": "Yongqun",
"middle": [],
"last": "He",
"suffix": ""
},
{
"first": "Hsing-Yi",
"middle": [],
"last": "Song",
"suffix": ""
},
{
"first": "Mohcine",
"middle": [],
"last": "Madkour",
"suffix": ""
},
{
"first": "Guozheng",
"middle": [],
"last": "Rao",
"suffix": ""
},
{
"first": "Yang",
"middle": [],
"last": "Xiang",
"suffix": ""
},
{
"first": "Yi",
"middle": [],
"last": "Luo",
"suffix": ""
},
{
"first": "W",
"middle": [],
"last": "Henry",
"suffix": ""
},
{
"first": "Sijia",
"middle": [],
"last": "Chen",
"suffix": ""
},
{
"first": "Liwei",
"middle": [],
"last": "Liu",
"suffix": ""
},
{
"first": "Hongfang",
"middle": [],
"last": "Wang",
"suffix": ""
},
{
"first": "Hua",
"middle": [],
"last": "Liu",
"suffix": ""
},
{
"first": "Cui",
"middle": [],
"last": "Xu",
"suffix": ""
},
{
"first": "",
"middle": [],
"last": "Tao",
"suffix": ""
}
],
"year": 2020,
"venue": "Journal of the American Medical Informatics Association",
"volume": "27",
"issue": "7",
"pages": "1046--1056",
"other_ids": {
"DOI": [
"10.1093/jamia/ocaa058"
]
},
"num": null,
"urls": [],
"raw_text": "Fang Li, Jingcheng Du, Yongqun He, Hsing-Yi Song, Mohcine Madkour, Guozheng Rao, Yang Xiang, Yi Luo, Henry W Chen, Sijia Liu, Liwei Wang, Hongfang Liu, Hua Xu, and Cui Tao. 2020. Time event ontology (TEO): to support semantic represen- tation and reasoning of complex temporal relations of clinical events. Journal of the American Medical Informatics Association, 27(7):1046-1056.",
"links": null
},
"BIBREF7": {
"ref_id": "b7",
"title": "Automatic identification of methotrexate-induced liver toxicity in patients with rheumatoid arthritis from the electronic medical record",
"authors": [
{
"first": "Chen",
"middle": [],
"last": "Lin",
"suffix": ""
},
{
"first": "Elizabeth",
"middle": [
"W"
],
"last": "Karlson",
"suffix": ""
},
{
"first": "Dmitriy",
"middle": [],
"last": "Dligach",
"suffix": ""
},
{
"first": "Monica",
"middle": [
"P"
],
"last": "Ramirez",
"suffix": ""
},
{
"first": "Timothy",
"middle": [
"A"
],
"last": "Miller",
"suffix": ""
},
{
"first": "Huan",
"middle": [],
"last": "Mo",
"suffix": ""
},
{
"first": "Natalie",
"middle": [
"S"
],
"last": "Braggs",
"suffix": ""
},
{
"first": "Andrew",
"middle": [],
"last": "Cagan",
"suffix": ""
},
{
"first": "Vivian",
"middle": [
"S"
],
"last": "Gainer",
"suffix": ""
},
{
"first": "Joshua",
"middle": [
"C"
],
"last": "Denny",
"suffix": ""
},
{
"first": "Guergana",
"middle": [
"K"
],
"last": "Savova",
"suffix": ""
}
],
"year": 2015,
"venue": "Journal of the American Medical Informatics Association",
"volume": "22",
"issue": "e1",
"pages": "151--161",
"other_ids": {
"DOI": [
"10.1136/amiajnl-2014-002642"
]
},
"num": null,
"urls": [],
"raw_text": "Chen Lin, Elizabeth W. Karlson, Dmitriy Dligach, Monica P. Ramirez, Timothy A. Miller, Huan Mo, Natalie S. Braggs, Andrew Cagan, Vivian S. Gainer, Joshua C. Denny, and Guergana K. Savova. 2015. Automatic identification of methotrexate-induced liver toxicity in patients with rheumatoid arthri- tis from the electronic medical record. Journal of the American Medical Informatics Association, 22(e1):e151-e161.",
"links": null
},
"BIBREF8": {
"ref_id": "b8",
"title": "Universal Dependencies v2: An evergrowing multilingual treebank collection",
"authors": [
{
"first": "Joakim",
"middle": [],
"last": "Nivre",
"suffix": ""
},
{
"first": "Marie-Catherine",
"middle": [],
"last": "De Marneffe",
"suffix": ""
},
{
"first": "Filip",
"middle": [],
"last": "Ginter",
"suffix": ""
},
{
"first": "Jan",
"middle": [],
"last": "Haji\u010d",
"suffix": ""
},
{
"first": "Christopher",
"middle": [
"D"
],
"last": "Manning",
"suffix": ""
},
{
"first": "Sampo",
"middle": [],
"last": "Pyysalo",
"suffix": ""
},
{
"first": "Sebastian",
"middle": [],
"last": "Schuster",
"suffix": ""
},
{
"first": "Francis",
"middle": [],
"last": "Tyers",
"suffix": ""
},
{
"first": "Daniel",
"middle": [],
"last": "Zeman",
"suffix": ""
}
],
"year": 2020,
"venue": "Proceedings of the 12th Language Resources and Evaluation Conference",
"volume": "",
"issue": "",
"pages": "4034--4043",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Joakim Nivre, Marie-Catherine de Marneffe, Filip Gin- ter, Jan Haji\u010d, Christopher D. Manning, Sampo Pyysalo, Sebastian Schuster, Francis Tyers, and Daniel Zeman. 2020. Universal Dependencies v2: An evergrowing multilingual treebank collection. In Proceedings of the 12th Language Resources and Evaluation Conference, pages 4034-4043, Mar- seille, France. European Language Resources Asso- ciation.",
"links": null
},
"BIBREF9": {
"ref_id": "b9",
"title": "Timeml: Robust specification of event and temporal expressions in text",
"authors": [
{
"first": "James",
"middle": [],
"last": "Pustejovsky",
"suffix": ""
},
{
"first": "M",
"middle": [],
"last": "Jos\u00e9",
"suffix": ""
},
{
"first": "Robert",
"middle": [],
"last": "Casta\u00f1o",
"suffix": ""
},
{
"first": "Roser",
"middle": [],
"last": "Ingria",
"suffix": ""
},
{
"first": "Robert",
"middle": [
"J"
],
"last": "Saur\u00ed",
"suffix": ""
},
{
"first": "Andrea",
"middle": [],
"last": "Gaizauskas",
"suffix": ""
},
{
"first": "Graham",
"middle": [],
"last": "Setzer",
"suffix": ""
},
{
"first": "",
"middle": [],
"last": "Katz",
"suffix": ""
},
{
"first": "R",
"middle": [],
"last": "Dragomir",
"suffix": ""
},
{
"first": "",
"middle": [],
"last": "Radev",
"suffix": ""
}
],
"year": 2003,
"venue": "New Directions in Question Answering, Papers from 2003 AAAI Spring Symposium",
"volume": "",
"issue": "",
"pages": "28--34",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "James Pustejovsky, Jos\u00e9 M. Casta\u00f1o, Robert Ingria, Roser Saur\u00ed, Robert J. Gaizauskas, Andrea Set- zer, Graham Katz, and Dragomir R. Radev. 2003. Timeml: Robust specification of event and temporal expressions in text. In New Directions in Question Answering, Papers from 2003 AAAI Spring Sympo- sium, Stanford University, Stanford, CA, USA, pages 28-34. AAAI Press.",
"links": null
},
"BIBREF10": {
"ref_id": "b10",
"title": "NewsReader: Using knowledge resources in a cross-lingual reading machine to generate more knowledge from massive streams of news",
"authors": [
{
"first": "Piek",
"middle": [],
"last": "Vossen",
"suffix": ""
},
{
"first": "Rodrigo",
"middle": [],
"last": "Agerri",
"suffix": ""
},
{
"first": "Itziar",
"middle": [],
"last": "Aldabe",
"suffix": ""
},
{
"first": "Agata",
"middle": [],
"last": "Cybulska",
"suffix": ""
},
{
"first": "Antske",
"middle": [],
"last": "Marieke Van Erp",
"suffix": ""
},
{
"first": "Egoitz",
"middle": [],
"last": "Fokkens",
"suffix": ""
},
{
"first": "Anne-Lyse",
"middle": [],
"last": "Laparra",
"suffix": ""
},
{
"first": "Alessio",
"middle": [],
"last": "Minard",
"suffix": ""
},
{
"first": "German",
"middle": [],
"last": "Palmero Aprosio",
"suffix": ""
},
{
"first": "Marco",
"middle": [],
"last": "Rigau",
"suffix": ""
},
{
"first": "Roxane",
"middle": [],
"last": "Rospocher",
"suffix": ""
},
{
"first": "",
"middle": [],
"last": "Segers",
"suffix": ""
}
],
"year": 2016,
"venue": "",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {
"DOI": [
"dx.doi.org/10.1016/j.knosys.2016.07.013"
]
},
"num": null,
"urls": [],
"raw_text": "Piek Vossen, Rodrigo Agerri, Itziar Aldabe, Agata Cy- bulska, Marieke van Erp, Antske Fokkens, Egoitz Laparra, Anne-Lyse Minard, Alessio Palmero Apro- sio, German Rigau, Marco Rospocher, and Roxane Segers. 2016. NewsReader: Using knowledge re- sources in a cross-lingual reading machine to gener- ate more knowledge from massive streams of news. Special Issue Knowledge-Based Systems, Elsevier.",
"links": null
}
},
"ref_entries": {
"FIGREF0": {
"num": null,
"type_str": "figure",
"text": ". This works because while in the SUB-INTERVAL version each MONTH-OF-YEAR 106 SCATE representation of Nov. 7th to 11th 2021 using standard SUB-INTERVAL (top) and proposed SUPER-INTERVAL (bottom). Arrows of the same color are performing similar functions.",
"uris": null
},
"FIGREF1": {
"num": null,
"type_str": "figure",
"text": "Abbreviated example of Anafora XML format (top left), LabelStudio JSON format (right), and Label-Studio visualization (bottom left). See fig. A1 in appendix A for the complete SUB-INTERVAL chain.<entity>",
"uris": null
},
"FIGREF2": {
"num": null,
"type_str": "figure",
"text": "A <Repeating-Intervals> property with multiple values. The phrase and spans the offsets 934 to 937 in the phrase Mondays and Tuesdays. The first <Repeating-Intervals> is an annotation over Mondays and the second is an annotation over Tuesdays.",
"uris": null
}
}
}
}