Class: BiologicalProcess

One or more causally connected executions of molecular functions

URI: biolink:BiologicalProcess





Identifier prefixes

  • GO
  • MetaCyc
  • KEGG


  • is_a: BiologicalProcessOrActivity - Either an individual molecular activity, or a collection of causally connected molecular activities

Uses Mixins


Referenced by class


Inherited from biological process or activity:

  • enabled by 0..*
    • Description: holds between a process and a physical entity, where the physical entity executes the process
    • range: PhysicalEntity
    • in subsets: (translator_minimal)

Inherited from gene product:

  • id REQ
    • Description: A unique identifier for a thing. Must be either a CURIE shorthand for a URI or a complete URI
    • range: String
    • in subsets: (translator_minimal)
  • name REQ
    • Description: A human-readable name for a thing
    • range: LabelType
    • in subsets: (translator_minimal)

Inherited from named thing:

  • category 1..*
    • 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 bl:Protein, bl:GeneProduct, bl: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 {bl:GenomicEntity, bl:MolecularEntity, bl:NamedThing}

Other properties

Mappings:   GO:0008150