My suggestions:

  1. AI is often the best tool if the tabular data is not formatted. I tested this with Overture to OSM a lot, to get predicted tags. It was okay, not great. I manually cleaned it up and now have this category to tag dict.

  2. Static key approaches get super hard of course, and you have some solutions like Placekey or GERS that could be inspiration or used directly. I think the way Wikidata IDs are generated (which has open source tools reusable for any dataset) can also be quite interesting. I think POIs need to be represented perhaps by using some kind of graph database logic, similar to OSM changesets and history but maybe with differences, not totally sure.

  3. Osmose is a good idea for how to get data provider feedback, maybe–Osmose stores outside of OSM some conflicts in OSM that an editor can overlay. It would be interesting to allow data providers to submit feedback on map data without making an edit, kind of an OSM note. Then people can reference that you are more skilled editors. Some notes go unresolved for years though, so some of these cases also may be the same. Often the data provider has the best incentive to edit, but only needs to do so skillfully, which sometimes is UX problem.

But I wouldn’t say that imports should be considered for this. It’s too important to have a human review everything than to mass import businesses. A criticism of Overture data quality might be linked to exactly this, that it’s a big global dataset that hasn’t been added changeset by changeset, over a wide scale of space and time. If you want to do OSM right you generally have to go slow if you want to keep a quality standard, and even then you may need to check every user edit that comes in, which OSM doesn’t have capacity to do, though Google Maps might.