Location Priority: Real Location versus a Known-As Location

I have been experimenting with geolocation, and the geolocation API, and I ran into a strange issue that I have not been able to work around other than to use a different provider (Yandex in this case because it too does not require an API key). I was encoding about 60 named locations in the format "city state", such as "buffalo new york", and ran into a problem. For the places I was encoding, the few I verified appeared to be correct when referencing the first returned geolocation record except for a place called "Middleville, New York". Middleville, New York is a village in upstate New York, in the county of Herkimer with a ZIP code of 13406. However, the first record returned from the OpenStreetMaps.org web site and the geolocation is API is for a small place here on Long Island that is named "Middleville" but is really in Fort Solonga, NY with a ZIP code of 11768. If I were to send mail to Middleville, NY it would go to upstate New York not here on Long Island.

My question is why does OpenStreetMaps give priority to a non-postal location over and official postal location? When I check Google, Bing and Mapquest for Middleville, NY, the first record returned if the official postal location. When I go to OpenStreetMaps.org, the first location returned is the Fort Solonga location here on Long Island. Is there any way to alter the priority of the returned data when only the city and state are queried?