Class: BiologicalProcess

One or more causally connected executions of molecular functions

URI: biolink:BiologicalProcess

---

---

Identifier prefixes

• GO
• REACT
• MetaCyc
• KEGG.MODULE

Parents

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

Uses Mixins

• mixin: Occurrent - A processual entity.

Children

• Behavior
• Death
• PathologicalProcess - A biologic function or a process having an abnormal or deleterious effect at the subcellular, cellular, multicellular, or organismal level.
• Pathway
• PhysiologicalProcess

Referenced by class

• MacromolecularMachineToBiologicalProcessAssociation macromolecular machine to biological process association➞object _REQ BiologicalProcess

Attributes

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 entity:

• id _REQ
  • 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 _OPT
  • Description: An IRI for an entity. This is determined by the id using expansion rules.
  • range: IriType
  • in subsets: (translator_minimal,samples)
• 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)
• type _OPT
  • range: String
• description _OPT
  • Description: a human-readable description of an entity
  • range: NarrativeText
  • in subsets: (translator_minimal)
• source _OPT
  • Description: a lightweight analog to the association class ‘has provider’ slot, which is the string name, or the authoritative (i.e. database) namespace, designating the origin of the entity to which the slot belongs.
  • range: LabelType
  • in subsets: (translator_minimal)
• provided by _0..*
  • Description: connects an association to the agent (person, organization or group) that provided it
  • range: Agent
• has attribute _0..*
  • Description: connects any entity to an attribute
  • range: Attribute
  • in subsets: (samples)

Inherited from macromolecular machine mixin:

• macromolecular machine mixin➞name _OPT
  • Description: genes are typically designated by a short symbol and a full name. We map the symbol to the default display name and use an additional slot for full name
  • range: SymbolType

Inherited from named thing:

• named thing➞category _1..*
  • range: NamedThing

Other properties