I know this is years later, but I recently tried to do this in model bulider, and am not able to use the dataset as you described in step 3. If I try to connect the feature class, it only allows me to use that as input for environment variables. Has something perhaps changed since you wrote this or is this just not possible in model builder?
Steve, thank you for responding, but my input data set would be an intermediate (and managed) feature class developed by earlier steps in the model process. So would you say my only option would then be to save that intermediate data set to a permanent file geodatabase just so it can be referenced by the Create Geostatistical Layer tool?
Because of the dynamic nature of a geostatistical layer the input datasets control is made up of a dataset (or many in the case of cokriging for example) and a field(s). So, you could persist your features using CopyFeatures or you could look into creating a script tool (submodel) that uses the GeostatisticalDatasets class.
You could also not use Modelbuilder and create a Python script tool.
Retrieving data ...