A workflow that (maybe) works for me for georeferencing verbatim ces might look something like this:
<placemark>
<name>1234</name>
<description>5000</description>
<lookat>
<longitude>-78.05350864897217</longitude>
<latitude>35.27158232210429</latitude>
<altitude>0</altitude>
<range>704786.0138216279</range>
<tilt>0</tilt>
<heading>-9.456134403076727e-06</heading>
<altitudemode>relativeToGround</altitudemode>
<gx:altitudemode>relativeToSeaFloor</gx:altitudemode>
</lookat>
<styleurl>#msn_ylw-pushpin</styleurl>
<point>
<coordinates>-76.53922967354748,34.85845799227256,0</coordinates>
</point>
</placemark>
This KML could then be batch uploaded to mx, and the verbatim ces could get their predicted lat/long, altitude, and error.
Maybe this would speed things up? I currently use resources like Google Earth to estimate lat/longs anyway, but the process of adding the info from one app to another is inefficient.