In fact, in you need to format sql at your convenience, as mojarrell said, see
http://www.hibernate.org/hib_docs/v3/re ... erysql-cud
If you want to do batch insert, then see :
http://www.hibernate.org/hib_docs/v3/re ... ch-inserts
But I'd ask myself of the interest of loading these sql statement as objects... If you are not sure of the qualities of these insert queries (null fields, or else), then maybe it could be an idea. But if you know these queries are ok, then don't load them as object : throw them directly against the db using the underlying jdbc connection.
What are these queries designed for ? Do you have to execute it regularly or only once after the creation of the db. If second choice, then it's another argument no to try and load them as entities. If it's designed to be called many times and/or change sometimes, then in fact it could be a good idea to load them as objects before saving it...