No, you need to get the IRepository<T> from the workcontext. The IRepository has the Create method which allows you to save the record.
The advantage of doing it like that is you only resolve the ones you need for any given operation (rather than injecting all 10 every time).
You could also consider splitting your class into smaller components rather than having to inject 10 different repositories.
I can't really imagine what architecture would call for 10 different tables in a single service; there's probably a neater way to set things up and avoid that altogether, if you show us what the 10 tables actually are someone might be able to suggest an