Link

Class: NamedThing

a databased entity or concept/class

URI: biolink:NamedThing

WIKIDATA:Q35120

UMLSSG:OBJC

UMLSSC:T071

UMLSST:enty

UMLSSC:T072

UMLSST:phob

UMLSSC:T073

UMLSST:mnob

UMLSSC:T168

UMLSST:food


img


Children

  • AdministrativeEntity
  • BiologicalEntity
  • ClinicalEntity - Any entity or process that exists in the clinical domain and outside the biological realm. Diseases are placed under biological entities
  • DataFile
  • DataSet
  • Device - A thing made or adapted for a particular purpose, especially a piece of mechanical or electronic equipment
  • InformationContentEntity - a piece of information that typically describes some piece of biology or is used as support.
  • MaterialSample - A sample is a limited quantity of something (e.g. an individual or set of individuals from a population, or a portion of a substance) to be used for testing, analysis, inspection, investigation, demonstration, or trial use. [SIO]
  • Occurrent - A processual entity
  • OntologyClass - a concept or class in an ontology, vocabulary or thesaurus
  • PhysicalEntity - An entity that has physical properties such as mass, volume, or charge
  • PlanetaryEntity - Any entity or process that exists at the level of the whole planet

Referenced by class

Attributes

Own

  • category 1..*
    • 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 bl:Protein, bl:GeneProduct, bl: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 {bl:GenomicEntity, bl:MolecularEntity, bl:NamedThing}

Inherited from gene product:

  • id REQ
    • Description: A unique identifier for a thing. Must be either a CURIE shorthand for a URI or a complete URI
    • range: String
    • in subsets: (translator_minimal)
  • name REQ
    • Description: A human-readable name for a thing
    • range: LabelType
    • in subsets: (translator_minimal)

Domain for slot:

  • category 1..*
    • 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 bl:Protein, bl:GeneProduct, bl: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 {bl:GenomicEntity, bl:MolecularEntity, bl:NamedThing}
  • id REQ
    • Description: A unique identifier for a thing. Must be either a CURIE shorthand for a URI or a complete URI
    • range: String
    • in subsets: (translator_minimal)
  • name REQ
    • Description: A human-readable name for a thing
    • range: LabelType
    • in subsets: (translator_minimal)

Other properties

     
Mappings:   WIKIDATA:Q35120
    UMLSSG:OBJC
    UMLSSC:T071
    UMLSST:enty
    UMLSSC:T072
    UMLSST:phob
    UMLSSC:T073
    UMLSST:mnob
    UMLSSC:T168
    UMLSST:food