Provides input for
Overview and Scope of Use
- This relation is used in GO-CAMs but not in standard annotation extensions.
- This relation is intended to connect successive activities, i.e. where the product (output) of the upstream activity is the substrate (input) for the downstream activity, and the product is a macromolecule.
- When the output molecule of the upstream activity is available in ChEBI, curators should not use this relation, and should instead connect the successive activities via the output molecule: [upstream activity] has_output [ChEBI] is_input [downstream activity].
- When the output molecule is not available (usually a modified protein or RNA), use: [upstream activity] provides_input_for [downstream activity].
- The 'provides input for' relation is used to relate two GO Molecular Functions when:
- The upstream and downstream activities succeed one another directly
- The output of the first activity is an input of the second activity.
- The output of the first activity is not available in ChEBI.
Annotation Usage Guidelines
- What to capture
- Upstream activities that provide a macromolecular input for a downstream activity.
- What not to capture
- Causal connections between molecular activities in which all inputs and outputs are described in ChEBI; instead, connect the successive activities via the output molecule: [upstream] has_output [ChEBI] is_input [downstream], for an example see GO-CAM model with inputs and outputs.
Examples
For example, AKT1 phosphorylates RAC1, creating p-RAC1 (which is not in ChEBI); p-RAC1 is then the input (target) for FBXL19, the substrate adaptor for ubiquitination and degradation of RAC1.
Ontology Usage Guidelines
This relation is not used in the ontology.
Cross Reference to the Relation Ontology (RO)
Review Status
Last reviewed: February 8, 2023
Reviewed by: Cristina Casals, Marc Feuermann, Pascale Gaudet, David Hill, Patrick Masson, Paul Thomas, Kimberly Van Auken