| Literature DB >> 18426553 |
Ai Kawazoe1, Hutchatai Chanlekha, Mika Shigematsu, Nigel Collier.
Abstract
BACKGROUND: This paper describes the design of an event ontology being developed for application in the machine understanding of infectious disease-related events reported in natural language text. This event ontology is designed to support timely detection of disease outbreaks and rapid judgment of their alerting status by 1) bridging a gap between layman's language used in disease outbreak reports and public health experts' deep knowledge, and 2) making multi-lingual information available. CONSTRUCTION AND CONTENT: This event ontology integrates a model of experts' knowledge for disease surveillance, and at the same time sets of linguistic expressions which denote disease-related events, and formal definitions of events. In this ontology, rather general event classes, which are suitable for application to language-oriented tasks such as recognition of event expressions, are placed on the upper-level, and more specific events of the experts' interest are in the lower level. Each class is related to other classes which represent participants of events, and linked with multi-lingual synonym sets and axioms.Entities:
Mesh:
Year: 2008 PMID: 18426553 PMCID: PMC2352865 DOI: 10.1186/1471-2105-9-S3-S8
Source DB: PubMed Journal: BMC Bioinformatics ISSN: 1471-2105 Impact factor: 3.169
Figure 1An overview of the BioCaster disease surveillance system. The system downloads news articles from online news feeds every few hours and filters out irrelevant topics. On the filtered articles, mentions to important concepts (disease cases, pathogens, time, location, etc) are recognized, and structured event information will then be retrieved. The information will be translated into other languages if necessary, and ranked according to its urgency and seriousness.
Figure 2Basic design of the BioCaster Event Ontology
Figure 3Top-level classification of event classes
Figure 4Event classes immediately under Eventive occurrences, Process and State.
Figure 5A closer look at an event class