biolink-model

Class: PhysicalEntity

An entity that has material reality (a.k.a. physical essence).

URI: biolink:PhysicalEntity

---

---

Parents

• is_a: NamedThing - a databased entity or concept/class

Uses Mixins

• mixin: PhysicalEssence - Semantic mixin concept. Pertains to entities that have physical properties such as mass, volume, or charge.

Children

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

Referenced by class

• BiologicalProcessOrActivity enabled by _0..* PhysicalEntity

Attributes

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}
  • 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 gene product mixin:

• synonym _0..*
  • Description: Alternate human-readable names for a thing
  • Range: LabelType
  • in subsets: (translator_minimal)
• 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 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
• full name _0..1
  • Description: a long-form human readable name for a thing
  • Range: LabelType
• 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}
  • Range: CategoryType
  • in subsets: (translator_minimal)

Other properties

Exact Mappings:		STY:T072
Narrow Mappings:		STY:T073

This site is open source. Improve this page.