Link

Class: Phenomenon

a fact or situation that is observed to exist or happen, especially one whose cause or explanation is in question

URI: biolink:Phenomenon

UMLSSG:PHEN

UMLSSC:T034

UMLSST:lbtr

UMLSSC:T038

UMLSST:biof

UMLSSC:T067

UMLSST:phpr

UMLSSC:T068

UMLSST:hcpp

UMLSSC:T069

UMLSST:eehu

UMLSSC:T070

UMLSST:npop


img


Parents

Attributes

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)

Inherited from named thing:

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

Other properties

     
Mappings:   UMLSSG:PHEN
    UMLSSC:T034
    UMLSST:lbtr
    UMLSSC:T038
    UMLSST:biof
    UMLSSC:T067
    UMLSST:phpr
    UMLSSC:T068
    UMLSST:hcpp
    UMLSSC:T069
    UMLSST:eehu
    UMLSSC:T070
    UMLSST:npop