Link Search Menu Expand Document

Class: NamedThing

a databased entity or concept/class

URI: biolink:NamedThing

img

Parents

  • is_a: Entity - Root Biolink Model class for all things and informational relationships, real or imagined.

Children

  • Activity - An activity is something that occurs over a period of time and acts upon or with entities; it may include consuming, processing, transforming, modifying, relocating, using, or generating entities.
  • AdministrativeEntity
  • Attribute - A property or characteristic of an entity. For example, an apple may have properties such as color, shape, age, crispiness. An environmental sample may have attributes such as depth, lat, long, material.
  • BiologicalEntity
  • ChemicalEntity - A chemical entity is a physical entity that pertains to chemistry or biochemistry.
  • ClinicalEntity - Any entity or process that exists in the clinical domain and outside the biological realm. Diseases are placed under biological entities
  • Device - A thing made or adapted for a particular purpose, especially a piece of mechanical or electronic equipment
  • Event - Something that happens at a given place and time.
  • ExposureEvent - A (possibly time bounded) incidence of a feature of the environment of an organism that influences one or more phenotypic features of that organism, potentially mediated by genes
  • InformationContentEntity - a piece of information that typically describes some topic of discourse or is used as support.
  • OrganismTaxon - A classification of a set of organisms. Example instances: NCBITaxon:9606 (Homo sapiens), NCBITaxon:2 (Bacteria). Can also be used to represent strains or subspecies.
  • Phenomenon - a fact or situation that is observed to exist or happen, especially one whose cause or explanation is in question
  • PhysicalEntity - An entity that has material reality (a.k.a. physical essence).
  • PlanetaryEntity - Any entity or process that exists at the level of the whole planet
  • Procedure - A series of actions conducted in a certain order or manner
  • Treatment - A treatment is targeted at a disease or phenotype and may involve multiple drug ‘exposures’, medical devices and/or procedures

Referenced by class

Attributes

Own

  • 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}
  • 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

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
  • 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)

Domain for slot:

  • 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}
  • 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
  • xref 0..*
    • Description: Alternate CURIEs for a thing
    • Range: Uriorcurie
    • in subsets: (translator_minimal)

Other properties

     
Exact Mappings:   BFO:0000001
    WIKIDATA:Q35120
    UMLSSG:OBJC
    STY:T071
    dcid:Thing