Class: MicroRNA
URI: biolink:MicroRNA
Identifier prefixes
- MIR
- HGNC
- WormBase
Parents
- is_a: NoncodingRNAProduct
Attributes
Inherited from chemical entity:
- trade name 0..1
- Range: ChemicalEntity
- available from 0..*
- Range: DrugAvailabilityEnum
- max tolerated dose 0..1
- Description: The highest dose of a drug or treatment that does not cause unacceptable side effects. The maximum tolerated dose is determined in clinical trials by testing increasing doses on different groups of people until the highest dose with acceptable side effects is found. Also called MTD.
- Range: String
- is toxic 0..1
- Range: Boolean
- has chemical role 0..*
- Description: A role is particular behaviour which a chemical entity may exhibit.
- Range: ChemicalRole
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 featuref
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}- Range: CategoryType
- in subsets: (translator_minimal)
- type 0..*
- Range: String
- 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 epigenomic entity:
- has biological sequence 0..1
- Description: connects a genomic feature to its sequence
- Range: BiologicalSequence
Inherited from gene product mixin:
- xref 0..*
- Description: A database cross reference or alternative identifier for a NamedThing or edge between two NamedThings. This property should point to a database record or webpage that supports the existence of the edge, or gives more detail about the edge. This property can be used on a node or edge to provide multiple URIs or CURIE cross references.
- 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 molecular entity:
- is metabolite 0..1
- Description: indicates whether a molecular entity is a metabolite
- Range: Boolean
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 featuref
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}- Range: CategoryType
- in subsets: (translator_minimal)
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)
- in taxon label 0..1
- Description: The human readable scientific name for the taxon of the entity.
- Range: LabelType
- in subsets: (translator_minimal)
Other properties
In Subsets: | model_organism_database | |
Exact Mappings: | SO:0000276 | |
SIO:001397 | ||
WIKIDATA:Q310899 |