Short answer: No, that would be using an database antipattern - the main problem being the lack of referential integrity, because you won't be able to define foreign keys on that table.
Long answer: The name of what you want to do is "polymorphic association". There are a few approaches to this:
Solution A) have two nullable columns: product_id and user_id
That is better than just having an entry_id, because you can define foreign keys. Your application only has to ensure that one (and only one) of those columns is NULL for every row in the image_batches table.
Solution B) have two intermediate tables: product_image_batches and user_image_batches which each reference your image_id
This will take the burdon of maintaining integrety off your application, and move it to your database, but introduces two new tables.