Currently, name of generated classes depends on KiePMMLModel name that, in turns, depends on (original) Model name.
This name may be missing (it is auto-generated) but it seems the same model name could be used inside different models in the same PMML file, at least inside nested Segments of MiningModel.
This lead to class clashes at evaluation time.
The current workaround is to ensure no models share the same model name (but this is not needed in jpmml).
To allow unique name generation, KiePMMLModel name must be created out of original file name and a different identifier strategy (index ?).