PhysiologicalProcess
None
classDiagram
OntologyClass <|-- PhysiologicalProcess
BiologicalProcess <|-- PhysiologicalProcess
PhysiologicalProcess : category
PhysiologicalProcess : description
PhysiologicalProcess : enabled_by
PhysiologicalProcess : has_attribute
PhysiologicalProcess : has_input
PhysiologicalProcess : has_output
PhysiologicalProcess : id
PhysiologicalProcess : in_taxon
PhysiologicalProcess : iri
PhysiologicalProcess : name
PhysiologicalProcess : provided_by
PhysiologicalProcess : source
PhysiologicalProcess : type
PhysiologicalProcess : xref
Parent Classes
- Entity
- NamedThing
- BiologicalEntity [ thing with taxon]
- BiologicalProcessOrActivity [ occurrent ontology class]
- BiologicalProcess [ occurrent ontology class]
- PhysiologicalProcess [ ontology class]
- BiologicalProcess [ occurrent ontology class]
- BiologicalProcessOrActivity [ occurrent ontology class]
- BiologicalEntity [ thing with taxon]
- NamedThing
Slots
Name | Description |
---|---|
category | 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 , etc. 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} |
description | a human-readable description of an entity |
enabled_by | holds between a process and a physical entity, where the physical entity executes the process |
has_attribute | connects any entity to an attribute |
has_input | holds between a process and a continuant, where the continuant is an input into the process |
has_output | holds between a process and a continuant, where the continuant is an output of the process |
id | A unique identifier for an entity. Must be either a CURIE shorthand for a URI or a complete URI |
in_taxon | connects an entity to its taxonomic classification. Only certain kinds of entities can be taxonomically classified; see 'thing with taxon' |
iri | An IRI for an entity. This is determined by the id using expansion rules. |
name | A human-readable name for an attribute or entity. |
provided_by | The value in this node property represents the knowledge provider that created or assembled the node and all of its attributes. Used internally to represent how a particular node made its way into a knowledge provider or graph. |
source | None |
type | None |
xref | Alternate CURIEs for a thing |
Mappings
Mapping Type | Mapped Value |
---|---|
self | ['https://w3id.org/biolink/biolink-model/:PhysiologicalProcess'] |
native | ['https://w3id.org/biolink/biolink-model/:PhysiologicalProcess'] |
exact | ['STY:T039', 'WIKIDATA:Q30892994'] |
narrow | ['STY:T040', 'STY:T042', 'STY:T043', 'STY:T045'] |