OpenEars isn’t moving it around, so this should be solvable by troubleshooting. I’d start by just peeking at what’s in the Simulator bundle when you run, as a sanity check.
OELanguageModelGenerator tries to abstract away the path management because it’s a common stumbling block for new developers, so my guess is the issue is coming up for you because you’re comfortable with dealing with the device file system and the way OELanguageModelGenerator tries to conceal it is making things more complex than necessary for you. I’d just start by eyeballing the container contents and I expect you’ll see whatever the issue is.