Keep in mind that Core Data is not primarily an object persistence framework, as I understand Hibernate et al. to be. Rather, it is an object graph management framework (it maintains relationships and changed state for objects subject to the model constraints), though it is not a dependency injection framework (like Groovy or Springs). It just so happens that it can persist this object graph to disk using one of several back-end formats (including SQLite). Core Data is also not meant for multi-user systems, as was the original Enterprise Object Framework. It is meant specifically for single-user desktop applications and automates much of the work of writing a Model layer for that type of app. For anything else, it's probably not a good fit.
What are you considering Core Data for? Perhaps we can provide a more specific answer if you give us a more specific use case.