Class: BiologicalProcess

One or more causally connected executions of molecular functions

GO:0008150

SIO:000006

WIKIDATA:Q2996394

Identifier prefixes

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

MacromolecularMachineToBiologicalProcessAssociation macromolecular machine to biological process association➞object _REQ BiologicalProcess

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)

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)

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}
- range: CategoryType
- in subsets: (translator_minimal)