Link

This site uses Just the Docs, a documentation theme for Jekyll.

Search

Class: ChemicalEntity

A chemical entity is a physical entity that pertains to chemistry or biochemistry.

URI: biolink:ChemicalEntity

img

Identifier prefixes

  • UNII
  • MESH
  • CAS

Parents

  • is_a: NamedThing - a databased entity or concept/class

Uses Mixins

  • mixin: PhysicalEssence - Semantic mixin concept. Pertains to entities that have physical properties such as mass, volume, or charge.
  • mixin: ChemicalOrDrugOrTreatment
  • mixin: ChemicalEntityOrGeneOrGeneProduct - A union of chemical entities and children, and gene or gene product. This mixin is helpful to use when searching across chemical entities that must include genes and their children as chemical entities.
  • mixin: ChemicalEntityOrProteinOrPolypeptide - A union of chemical entities and children, and protein and polypeptide. This mixin is helpful to use when searching across chemical entities that must include genes and their children as chemical entities.

Children

Referenced by class

Attributes

Own

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)
  • source 0..1
    • 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 0..1
    • 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:

Other properties

     
In Subsets:   translator_minimal
Exact Mappings:   CHEBI:24431
    SIO:010004
    WIKIDATA:Q79529
    STY:T103
Narrow Mappings:   WIKIDATA:Q43460564