From what I understand of Python 3, the type type is the meta-class that is used to create Class objects, so type is to object as "Car" is to "Jaguar", through a process of calling its __call__ method which then calls the class's __new__ and __init__ methods, returning the instance of the class itself.
At the normal level, the relation between type and object makes perfect sense; everything is an object (subclasses object), and everything has a type; the type of the object 5 is int, and int's type is type itself. Hence isinstance(5, int) and isinstance(int, type) are true. However, isinstance(5, type) is not true since 5 is not a class object, it's an instance of a class.
This article: http://www.cafepy.com/article/python_types_and_objects/python_types_and_objects.html#object-type-example
Hence defines an object as having exactly one type. But at the very primitive level, of the classes type and object themselves, the relationship between them confuses me. type is a subclass of object, as seen in its __bases__, but object itself is an instance of type. 
If describing something like 5 can be split into "meat" and "bones", where "meat" represents the actual creation of it in memory and assigning values to it, and "bones" the definition of how it should be, of its legal range of values and behaviours, does this mean that, at the very core, type is responsible for creating the "meat" of class objects, and object is responsible for defining the "bones"? If so, what is the "meat" equivalent of creating an instance of a class, if the "bones", in this case, is the class int?


objectis really just the common set of properties all objects in Python support, so I would call object the "bare bones" of an instance/class/metaclass. A class (likeint) is really just an extension of type one level down.typedictates what you can and cannot do with a class while the class dictates what you can and cannot do with an instance.