Hi Christine,
That time will also be the creation time, but only while you're on the original timeflow, if you refresh or rewind the VDB, then the timeflow name will change to reflect that, and the timstamp will refer to that time instead of when the VDB was actually created. If the timeflow name starts with "DB_PROVISION" then it can be read as creation time.
On my test server (running 5.0.3.0) I get these first few lines, creation date is listed on 4th line:
type: OracleDatabaseContainer
name: vdb1
contentType: NON_CDB
creationTime: 2016-05-25T09:53:50.973Z
crossPlatformReady: false
currentTimeflow: 'DB_PROVISION@2016-05-25T10:53:55'
databaseFraction: false ...
perhaps this changed in one of the releases, can you tell me which version you are running and I'll look into it?