Class: ChemicalToChemicalDerivationAssociation

A causal relationship between two chemical entities, where the subject represents the upstream entity and the object represents the downstream. For any such association there is an implicit reaction: IF R has-input C1 AND R has-output C2 AND R enabled-by P AND R type Reaction THEN C1 derives-into C2 «catalyst qualifier P»

URI: biolink:ChemicalToChemicalDerivationAssociation



  • is_a: ChemicalToChemicalAssociation - A relationship between two chemical entities. This can encompass actual interactions as well as temporal causal edges, e.g. one chemical converted to another.

Referenced by class



Inherited from association:

  • subject 1..1
    • Description: connects an association to the subject of the association. For example, in a gene-to-phenotype association, the gene is subject and phenotype is object.
    • Range: NamedThing
  • predicate 1..1
    • Description: A high-level grouping for the relationship type. AKA minimal predicate. This is analogous to category for nodes.
    • Range: PredicateType
  • object 1..1
    • Description: connects an association to the object of the association. For example, in a gene-to-phenotype association, the gene is subject and phenotype is object.
    • Range: NamedThing
  • relation 0..1
  • negated 0..1
    • Description: if set to true, then the association is negated i.e. is not true
    • Range: Boolean
  • qualifiers 0..*
    • Description: connects an association to qualifiers that modify or qualify the meaning of that association
    • Range: OntologyClass
  • publications 0..*
    • Description: connects an association to publications supporting the association
    • Range: Publication
  • association➞type 0..1
    • Description: rdf:type of biolink:Association should be fixed at rdf:Statement
    • Range: String
  • association➞category 0..*

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

Domain for slot: