Skip to content

Slot: occurred_in

The slot to specify the Surrounding in which an Activity took place.

URI: prov:atLocation Alias: occurred_in

Applicable Classes

Name Description Modifies Slot
Synthesis A DataGeneratingActivity in which a catalyst is prepared.

The preparation protocol is linked via realized_plan using a
PreparationMethod instance. Input materials (Precursors) are linked via
had_input_entity. The resulting catalyst (CatalystSample) is linked via
had_output_entity.

The type of synthesis is further specified via rdf_type using an ontology
term (e.g. a VOC4CAT preparation method term), following DCAT-AP-PLUS
Pattern 3.		 no
Simulation A DataGeneratingActivity in which a catalyst, catalytic material, or
catalytic process is modelled computationally.

The simulation software is linked via carried_out_by as a Software agent.
The simulation method (protocol) is linked via realized_plan using a
SimulationMethod instance. The catalyst model or reaction being simulated
is linked via evaluated_entity or evaluated_activity.

The specific simulation type is expressed via rdf_type (e.g. coremeta4cat:DFT,
NCIT:C18097 for molecular dynamics), following DCAT-AP-PLUS Pattern 3.		 no
ReactionMonitoring A DataGeneratingActivity that produces data about a ChemicalReaction, such as reaction monitoring, experimental documentation, or a combined recording-and-evaluation workflow. This is a coarse-grained convenience shape that does not distinguish between raw experimental recording and subsequent data evaluation. Domain-specific sub-profiles that need this distinction should define their own DataGeneratingActivity subclasses and use the DCAT-AP+ DataAnalysis chain to separate raw data from derived results. no
Characterization A DataGeneratingActivity in which a catalyst sample or catalytic material
is characterized using an analytical technique.

The catalyst sample being characterized is linked via evaluated_entity.
The analytical protocol is linked via realized_plan using a
CharacterizationTechnique instance. The instrument used is linked via
carried_out_by as a Device.

The specific technique type is expressed via rdf_type using an ontology
term (e.g. CHMO:0000158 for powder XRD, CHMO:0000404 for XPS),
following DCAT-AP-PLUS Pattern 3 — exactly as NMRSpectroscopy uses
rdf_type: CHMO:0000613.		 no
SubstanceSampleCharacterization A DataGeneratingActivity that produces data about a SubstanceSample, such as a spectroscopic measurement, a physical property determination, or a combined measurement-and-analysis workflow. This is a coarse-grained convenience shape that does not distinguish between raw data acquisition and subsequent data processing or analysis. Domain-specific sub-profiles that need this distinction should define their own DataGeneratingActivity subclasses and use the DCAT-AP+ DataAnalysis chain to separate raw measurement from derived results. no
DataGeneratingActivity An Activity (process) that has the objective to produce information (in form of a dataset) about another Activity or Entity. no
DataAnalysis An Activity that evaluates the data produced by another Activity. no

Properties

Identifier and Mapping Information

Schema Source

Mappings

Mapping Type Mapped Value
self prov:atLocation
native coremeta4cat:occurred_in

LinkML Source

name: occurred_in
description: The slot to specify the Surrounding in which an Activity took place.
in_subset:
- domain_agnostic_core
from_schema: https://w3id.org/nfdi4cat/coremeta4cat
rank: 1000
slot_uri: prov:atLocation
alias: occurred_in
domain_of:
- DataGeneratingActivity
range: Surrounding