Lazy geometries are not another kind of geometry. This only describes how Geodjango manages to load, instantiate and use geometry objects, and is pretty much like lazy loading in an O/R mapping framework.
If you access a whole bunch of geometry data (lets say from a table), geodjango loads them in text based "Well known text" (WKT) format. If you then pick one of them and want to calculate the area of a polygon for example, Geodjango instantiates a GEOS object for you and calculates the area on it.
So "lazy" refers to GeoDjangos behaviour to do costly things only when they are really needed.
Its also described in the GeoDjango Tutorial