Link Search Menu Expand Document

Class: Pathway

URI: biolink:Pathway


img


Identifier prefixes

  • GO
  • REACT
  • KEGG
  • SMPDB
  • MSigDB
  • PHARMGKB.PATHWAYS
  • WIKIPATHWAYS
  • FB
  • PANTHER.PATHWAY
  • KEGG.PATHWAY
  • ncats.bioplanet

Parents

  • is_a: BiologicalProcess - One or more causally connected executions of molecular functions

Uses Mixins

  • mixin: 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.

Referenced by class

Attributes

Inherited from biological process or activity:

  • has input 0..*
    • Description: holds between a process and a continuant, where the continuant is an input into the process
    • Range: Occurrent
    • in subsets: (translator_minimal)
  • has output 0..*
    • Description: holds between a process and a continuant, where the continuant is an output of the process
    • Range: Occurrent
    • in subsets: (translator_minimal)
  • 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 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)
  • has attribute 0..*
    • Description: connects any entity to an attribute
    • Range: Attribute
    • in subsets: (samples)

Inherited from gene product mixin:

  • xref 0..*
    • Description: Alternate CURIEs for a thing
    • Range: Uriorcurie
    • in subsets: (translator_minimal)

Inherited from macromolecular machine mixin:

  • name 0..1
    • Description: A human-readable name for an attribute or entity.
    • Range: LabelType
    • in subsets: (translator_minimal,samples)

Inherited from named thing:

  • provided by 0..*
    • Description: 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.
    • Range: String
  • 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}

Inherited from thing with taxon:

  • in taxon 0..*
    • Description: connects an entity to its taxonomic classification. Only certain kinds of entities can be taxonomically classified; see ‘thing with taxon’
    • Range: OrganismTaxon
    • in subsets: (translator_minimal)

Other properties

     
Exact Mappings:   PW:0000001
    WIKIDATA:Q4915012
Narrow Mappings:   SIO:010526
    GO:0007165