You are correct, most of the social media vendors support SAML for access to their own applications (using a third-party IdP). You can use APM SAML as an IdP for Google, Facebook, and Salesforce. As for the IdP itself, it really depends on where the users are.
I highly recommend this (free) book from Microsoft (A Guide to Claims-based Identity and Access Control, Second Edition) as an excellent primer:
http://www.microsoft.com/en-us/download/details.aspx?id=28362
It talks about using Azure ACS as a connector to Facebook and others (which do actually assert claims) for social media authentication. Here's another interesting stackoverflow post that points to API references for various "social login" options.
http://stackoverflow.com/questions/6235735/how-to-add-social-login-services-from-google-facebook-yahoo-etc-to-my-website
Now, to tie this all back to F5 APM, you still need a connector like ACS for protocol transformation, which then asserts a claim back to your APM SP, or optionally to your APM IdP as a relying party (for additional claims assertion) before forwarding to the SP.