Can't format former Boot Camp partition

You must erase the hard drive and start over. Make a backup first. Format your HDD to 1 partition (MacOS Extended (Journaled))

Never use DU to do anything to a Boot Camp partition.

You may have a lingering MBR problem, since the GPT was modified but not the corresponding MBR. Bootcamp Windows uses a Hybrid MBR, if you did not install Windows using EFI boot. What version of Windows did you have before delete was executed?

Please post the output of the following commands from OS X Terminal. Enter your password as necessary.

diskutil list

sudo gpt -vv -r show /dev/disk0

sudo fdisk /dev/disk0

Run Internet Recovery (Command+Opt+R) and then run Disk Utility. Do you see an internal disk at all? If you erase just the Macintosh HD, it does nothing to any other partitions and cleaning up the lingering partition is what you want to achieve. You need to have a full backup of OS X and all your data, and erase the entire drive, not just a single volume.

Click on the disk and format it as a single partition and Mac OS X Extended Journaled and restore from the latest TM backup.

You are running Beta OS, as indicated by the "Logical Volume" at the bottom of the screen. The LVG has no LVs in it. To verify quit Disk Utility and start OS X Terminal and post the output of diskutil cs list.

If you are trying to re-install Mavericks on this setup, it will not work. You will need to delete the LVG using diskutil cs commands from OS X Terminal. Here is the Man page of diskutil coreStorage

diskutil cs

Usage: diskutil [quiet] coreStorage|CS <verb> <options>,

where <verb> is as follows:

list (Show status of CoreStorage volumes)

info[rmation] (Get CoreStorage information by UUID or disk)

convert (Convert a volume into a CoreStorage volume)

revert (Revert a CoreStorage volume to its native type)

create (Create a new CoreStorage logical volume group)

delete (Delete a CoreStorage logical volume group)

rename (Rename a CoreStorage logical volume group)

createVolume (Create a new CoreStorage logical volume)

deleteVolume (Delete a volume from a logical volume group)

encryptVolume (Encrypt a CoreStorage logical volume)

decryptVolume (Decrypt a CoreStorage logical volume)

unlockVolume (Attach/mount a locked CoreStorage logical volume)

changeVolumePassphrase (Change a CoreStorage logical volume's passphrase)

diskutil coreStorage <verb> with no options will provide help on that verb

Are you trying to install Mavericks on the disk, or are you planning to re-install Beta OS?

If you notice you have no Logical Volume in your LVG. I suggest you delete the LVG, which should show you the underlying disk.

This is how you can delete the LVG. I am using the LVG UUID that came from your output...

diskutil cs delete 892BA2E0-214C-40F2-AB50-4B7F6272053E

Here is the man page entry

diskutil cs delete

Usage: diskutil coreStorage delete lvgUUID|lvgName

Delete a CoreStorage logical volume group. All logical volumes will be removed.

Ownership of the affected disks is required.

Here is an example of a working CS setup...

diskutil cs list

CoreStorage logical volume groups (1 found)

|

+-- Logical Volume Group 57578357-3715-48A5-AB8A-4107AF12F7FB

=========================================================

Name: OSY-MBP13

Status: Online

Size: 128200753152 B (128.2 GB)

Free Space: 1424523264 B (1.4 GB)

|

+-< Physical Volume 4D897085-0793-48CC-A00F-58572A56B043

| ----------------------------------------------------

| Index: 0

| Disk: disk0s2

| Status: Online

| Size: 128200753152 B (128.2 GB)

|

+-> Logical Volume Family 11EBF920-AA4B-4EC6-AC7F-7CC70E69883C

----------------------------------------------------------

Encryption Status: Unlocked

Encryption Type: None

Conversion Status: NoConversion

Conversion Direction: -none-

Has Encrypted Extents: No

Fully Secure: No

Passphrase Required: No

|

+-> Logical Volume 8A0116D5-7E1E-44D8-B2A0-8D4E4D48298D

---------------------------------------------------

Disk: disk1

Status: Online

Size (Total): 126423908352 B (126.4 GB)

Conversion Progress: -none-

Revertible: Yes (no decryption required)

LV Name: OSY-MBP13

Volume Name: OSY-MBP13

Content Hint: Apple_HFS

You can run diskutil list.

From the Disk Utility, you can create volumes, but you should not need to. Did you try restoring your TM backup? Do you get an error when you do?

If you are restoring a full TM backup, it will erase and restore the entire disk. Please try and post if you get any errors when you attempt a restore. If you want to test whether it works or not...

You can erase the disk using...

diskutil eraseDisk

Usage: diskutil eraseDisk format name [APM[Format]|MBR[Format]|GPT[Format]]

MountPoint|DiskIdentifier|DeviceNode

Completely erase an existing whole disk. All volumes on this disk will be

destroyed. Ownership of the affected disk is required.

Format is the specific file system name you want to erase it as (HFS+, etc.).

Name is the (new) volume name (subject to file system naming restrictions),

or can be specified as %noformat% to skip initialization (newfs).

You cannot erase the boot disk.

Example: diskutil eraseDisk JHFS+ UntitledUFS disk3

You can format the disk using...

diskutil reformat

Usage: diskutil reformat MountPoint|DiskIdentifier|DeviceNode

Completely erase an existing volume with the same name and format as the

original. Ownership of the affected disk is required.

You cannot erase the boot volume, nor can you reformat any device which

does not have a valid file system (instead use diskutil eraseVolume).