Slot: had_input_entity

The slot to specify the Entity that was used as an input of an Activity that is to be changed, consumed or transformed.

URI: prov:used Alias: had_input_entity

Inheritance

• had_input_entity
  • adsorption_gas
  • used_starting_material
  • used_reactant
  • evaluated_entity

Applicable Classes

Name	Description	Modifies Slot
CatalysisDataGeneratingActivity	A CoreMeta4Cat specialization of DCAT-AP-PLUS's DataGeneratingActivity that adds a type designator (activity_designator). Synthesis, Characterization, and Simulation all specialize this class instead of DataGeneratingActivity directly, so that when one of them is nested inside CatalysisDataset.was_generated_by, the LinkML Python loader can tell which concrete subclass a given entry is meant to be and keep its subclass-specific fields (e.g. Characterization.realized_plan) rather than falling back to DataGeneratingActivity's own generic slot definitions. activity_designator is filled in automatically by LinkML when a class is instantiated directly (e.g. loading a standalone Synthesis-NNN.yaml file) -- it does not need to be set by hand there. It only needs to be set explicitly in the source data when a Synthesis/Characterization/ Simulation instance is nested inside another object's was_generated_by list (e.g. in a combined CatalysisDataset file), so the loader knows which of the three to construct.	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
DataAnalysis	An Activity that evaluates the data produced by another Activity.	no
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.	yes
DataGeneratingActivity	An Activity (process) that has the objective to produce information (in form of a dataset) about another Activity or Entity.	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
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
Activity	See DCAT-AP specs:Activity	yes
CatalyticReaction	A ChemicalReaction (chemdcat-ap) specialization representing the catalytic reaction being studied. Inherits the generic reaction slots (starting materials, reactants, products, catalyst, solvent, reactor, temperature, pressure, yield, reaction steps) from ChemicalReaction and adds catalysis-specific operating-condition slots. Reaction is NOT a DataGeneratingActivity — it is the catalytic process being observed, not the process that generates the dataset. A CatalysisDataset is linked to the Reaction it is about via is_about_activity. For operando experiments (e.g. in-situ XRD during a reaction), the dataset carries both: was_generated_by: Characterization (the measurement producing data) is_about_activity: Reaction (the catalytic process being monitored) The reactor is linked via the inherited used_reactor slot (is_a: carried_out_by), narrowed here to require a ChemicalReactor instance rather than touching the generic carried_out_by relation directly. Reactants are linked via the inherited used_reactant slot (range: Reagent) -- CatalyticReaction does not declare its own reactant slot. The type of catalytic reaction (e.g. ammonia synthesis, CO oxidation) is expressed via rdf_type using a voc4cat or ChemO term.	no
EvaluatedActivity	An activity or process that is being evaluated in a DataGeneratingActivity.	no
ChemicalReaction	A process that leads to the transformation of one set of chemical substances to another and that is the subject matter of a DataGeneratingActivity.	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

Properties

• Range: Entity

• Multivalued: True

• Recommended: True

Identifier and Mapping Information

Schema Source

• from schema: https://w3id.org/nfdi4cat/coremeta4cat

Mappings

Mapping Type	Mapped Value
self	prov:used
native	coremeta4cat:had_input_entity

LinkML Source

name: had_input_entity
description: The slot to specify the Entity that was used as an input of an Activity
  that is to be changed, consumed or transformed.
in_subset:
- domain_agnostic_core
from_schema: https://w3id.org/nfdi4cat/coremeta4cat
rank: 1000
slot_uri: prov:used
alias: had_input_entity
domain_of:
- Activity
range: Entity
recommended: true
multivalued: true
inlined: true
inlined_as_list: true