Link Search Menu Expand Document

Class: OntologyClass

a concept or class in an ontology, vocabulary or thesaurus. Note that nodes in a biolink compatible KG can be considered both instances of biolink classes, and OWL classes in their own right. In general you should not need to use this class directly. Instead, use the appropriate biolink class. For example, for the GO concept of endocytosis (GO:0006897), use bl:BiologicalProcess as the type.

URI: biolink:OntologyClass


Identifier prefixes

  • MESH
  • UMLS


  • RelationshipType - An OWL property used as an edge label
  • TaxonomicRank - A descriptor for the rank within a taxonomic classification. Example instance: TAXRANK:0000017 (kingdom)

Mixin for

  • Attribute (mixin) - A property or characteristic of an entity. For example, an apple may have properties such as color, shape, age, crispiness. An environmental sample may have attributes such as depth, lat, long, material.
  • Behavior (mixin)
  • BiologicalProcess (mixin) - One or more causally connected executions of molecular functions
  • BiologicalProcessOrActivity (mixin) - Either an individual molecular activity, or a collection of causally connected molecular activities in a biological system.
  • Drug (mixin) - A substance intended for use in the diagnosis, cure, mitigation, treatment, or prevention of disease
  • Gene (mixin) - A region (or regions) that includes all of the sequence elements necessary to encode a functional transcript. A gene locus may include regulatory regions, transcribed regions and/or other functional sequence regions.
  • Genome (mixin) - A genome is the sum of genetic material within a cell or virion.
  • GenomicBackgroundExposure (mixin) - A genomic background exposure is where an individual’s specific genomic background of genes, sequence variants or other pre-existing genomic conditions constitute a kind of ‘exposure’ to the organism, leading to or influencing an outcome.
  • Genotype (mixin) - An information content entity that describes a genome by specifying the total variation in genomic sequence and/or gene expression, relative to some established background
  • Haplotype (mixin) - A set of zero or more Alleles on a single instance of a Sequence[VMC]
  • MolecularActivity (mixin) - An execution of a molecular function carried out by a gene product or macromolecular complex.
  • NucleicAcidEntity (mixin) - A nucleic acid entity is a molecular entity characterized by availability in gene databases of nucleotide-based sequence representations of its precise sequence; for convenience of representation, partial sequences of various kinds are included.
  • Pathway (mixin)
  • PhysiologicalProcess (mixin)
  • ReagentTargetedGene (mixin) - A gene altered in its expression level in the context of some experiment as a result of being targeted by gene-knockdown reagent(s) such as a morpholino or RNAi.
  • SequenceVariant (mixin) - An allele that varies in its sequence from what is considered the reference allele at that locus.

Referenced by class


Inherited from entity:

  • id 1..1
    • Description: A unique identifier for an entity. Must be either a CURIE shorthand for a URI or a complete URI
    • Range: String
    • in subsets: (translator_minimal)
  • iri 0..1
    • Description: An IRI for an entity. This is determined by the id using expansion rules.
    • Range: IriType
    • in subsets: (translator_minimal,samples)
  • category 0..*
    • Description: Name of the high level ontology class in which this entity is categorized. Corresponds to the label for the biolink entity type class.
  • In a neo4j database this MAY correspond to the neo4j label tag.
  • In an RDF database it should be a biolink model class URI. This field is multi-valued. It should include values for ancestors of the biolink class; for example, a protein such as Shh would have category values biolink:Protein, biolink:GeneProduct, biolink:MolecularEntity, … In an RDF database, nodes will typically have an rdf:type triples. This can be to the most specific biolink class, or potentially to a class more specific than something in biolink. For example, a sequence feature f may have a rdf:type assertion to a SO class such as TF_binding_site, which is more specific than anything in biolink. Here we would have categories {biolink:GenomicEntity, biolink:MolecularEntity, biolink:NamedThing}
  • type 0..1
  • description 0..1
    • Description: a human-readable description of an entity
    • Range: NarrativeText
    • in subsets: (translator_minimal)
  • source 0..1
  • has attribute 0..*
    • Description: connects any entity to an attribute
    • Range: Attribute
    • in subsets: (samples)

Other properties

Comments:   This is modeled as a mixin. ‘ontology class’ should not be the primary type of a node in the KG. Instead you should use an informative bioloink category, such as AnatomicalEntity (for Uberon classes), ChemicalSubstance (for CHEBI or CHEMBL), etc
    Note that formally this is a metaclass. Instances of this class are instances in the graph, but can be the object of ‘type’ edges. For example, if we had a node in the graph representing a specific brain of a specific patient (e.g brain001), this could have a category of bl:Sample, and by typed more specifically with an ontology class UBERON:nnn, which has as category bl:AnatomicalEntity
Examples:   Example(value=’UBERON:0000955’, description=”the class ‘brain’ from the Uberon anatomy ontology”)
See also:
Exact Mappings:   owl:Class