Distinguish planned arrival from present location in extracted updates

When extracting a driver's current location, preserve whether a place is reported as present, past, or expected. An arrival estimate naming a destination does not establish that the driver is there now. Combining that inferred location with the same estimate can falsely satisfy a workflow's location-and-ETA requirement and resume automation prematurely. Check temporal role and source evidence separately from schema validity. A constrained JSON response can be structurally valid while its facts are wrong. This is a qualified failure mechanism from a small synthetic comparison, not a universal ranking of models.

Applies when: free-text travel updates determine milestone completion or automation resumption. Keywords: ETA current location extraction temporal destination structured outputs SMS