IASO Knowledge Graph

The Antibiotic KG, which is currently published in the system, centers on antibiotics and consists of common antibiotics, diseases, pathogens, infection sites, complications, symptoms, types of symptoms and their relationships, totaling more than 450,000 entities and nearly 6,000 relationships. Researchers can now obtain entities, relationships and query entity-centered micro-knowledge maps in the "Antibiotic KG" by calling API provided by the system.
Read carefully before using Dataset download protocol.

View Knowledge Graph View tutorial

Data Set Usage Protocol

You (hereinafter referred to as "Researcher") are requesting the IASO Open Source System to grant you the right to access, download and use data sets (hereinafter referred to as "data sets"). As a condition for obtaining such authorization, you agree to abide by the following terms:

1. Researchers agree to use data sets only for non-commercial scientific research or classroom teaching purposes. It is strictly forbidden to use data sets for clinical diagnosis and not for any commercial purposes.
2. We do not enjoy the intellectual property rights of pictures, audio, text and other contents used in data sets, and do not guarantee the aforementioned contents, including, but not limited to, infringement of the intellectual property rights of others or the use of the aforementioned contents for any specific purpose;
3. We are not liable for any form of loss or damage caused by the use of data sets, and will not be liable for any legal consequences arising from the use of data sets.
4. Any legal liability related to the use of data sets shall be borne by researchers. If the use of data sets by researchers or their employees, agents or branches causes reputation or economic losses to us, researchers shall be liable for compensation.
5. Researchers may authorize their assistants, colleagues or other partners to access and use data sets, but they shall ensure that the aforementioned persons have carefully read and agree to be bound by this Agreement.
6. If a researcher is employed by a profit-making business entity, he or she shall ensure that data sets are used only for non-commercial purposes and that his or her employer is also bound by this Agreement. The researcher confirms that he or she has obtained sufficient authorization from the employer before signing this Agreement.
7. We have the right to revoke or withdraw the authorization of researchers to use datasets at any time, and to request researchers to delete downloaded datasets.


The system API design refers to RESTful API design principles, and now completes the query (read resources) operation.
A KG is composed of several elements. Through RESTful API, IASO displays the KG components that the user could discern the information effortlessly, and are the following:

Taxonomy Query

The presentation of the taxonomy on which the knowledge graph is based is significant for understanding the inheritance relations between classes. Our system provides a holistic view of this taxonomy, in a hierarchical representation. The partial views that allow the user to focus on a portion of other relationships, are achieved through the aspects shown below.

Entity Facts Query

The visualization system displays all the knowledge graph classes, at the request of the user, providing the name and other information, in an intelligible manner. As shown in Figure 1, our aim is to extract knowledge related to Amoxicillin from the KG. The corresponding information, such as an ID, a name, a drug type, a description, as well as the drug indication information, are the actual data and in most cases what the user is actually interested in. This disambiguated information can aid the user to look up known information.

At present, antibiotic, bacteria, complication, disease, infection_site, symptom and symptom_type are provided for seven types of entity queries. The query results are returned in JSON format.

API calls: [GET] /api/{entity_type}/{entity_name}
{entity_type} the optional values are: antibiotics, bacterias, complications, diseases, infection_sites, symptoms, symptom_types
{entiry_name} is entity name for user query


Query antibiotic Amoxycillin [GET] /api/antibiotics/Amoxycillin
The results are as follows,


Entity Relation Query

The extraction process starts with a set of triples for a given relation. For example, (diphtheria, disease_bacteria, corynebacterium) would be a valid triple for the disease_bacteria relation. The input entity is processed to recognize and match with the KG concept (see Figure 2). When an entity matches a KG concept, a subgraph will be returned to present all its connected entities, the relation type and the relation direction from head entity to tail entity. Any other entity which does not appear in the KG has no relationship with the input entity. There may be a variety of relationships when an entity belongs to different entity types.

At present, there are seven types of entity relationship queries for antibiotics, pathogens, complications, diseases, infection sites, symptoms and symptom types. The results of the query are returned in JSON format. The content of the query covers entity relationship types and the direction of the relationship. There may be phenomena that the same name entity belongs to different types of entity, and the returned results cover multiple relationships.

API calls: [GET] /api/relations/{entity1}/{entity2}
{entity1}, {entiry2}are entity names for user query.


Query the relationship of Diphtheria and Corynebacterium [GET] /api/relations/Corynebacterium/Diphtheria
The results are as follows,

Subgraph Query

Taxonomy and entity relations are two types of links that transform the knowledge graph from a hierarchy to a graph. When receiving an entity queried by user, IASO returns a subgraph composed of this entity and the entities that it is directly related to (see Figure 3). For example, “ear” is considered as an infectious site in infectious disease diagnosis. Its pathogenic bacteria include enterobacteriaceae, Haemophilus influenzae, moraexlla, proteus, etc. Apart from the link that should be visible, a label with the link name (effectively, the relation type) is also displayed.

At present, sub-graph (micro knowledge map) query is provided. The sub-graph is composed of Central entity (query entity provided by caller) and its relationship and entity directly associated with the central entity. There may be the phenomenon that the same-name entity belongs to different types of entity, and the returned result covers multiple sub-graphs.

API calls:[GET] /api/subgraphs/{entity_name}
{entiry_name} is entity name for user query


Query the subgraph of the entity ear [GET] /api/subgraphs/Ear
The results are as follows,