Deliverables depend entirely on what you are building. You may find it best to start by stating the end result of the project then work backwards to find the interim deliverables. In the case of a house, these may be something like: complete interior fit-out, complete the roof, complete the walls, complete the foundations, prepare the site, obtain building permissions, draw up plans, appoint a contractor, appoint an architect. Then break these down further if necessary. The tasks are the activities required to get from one deliverable to another, so again, these are specific to your project.
People who should be able to help with the WBS will include: the system architect, technical leads, team leaders, system designers, technicians. Get them all to review the plan at the start, and ask if they agree with the tasks and deliverables. However, don't be surprised if they disagree with what you have put down as your draft plan: what seems logical to you may be completely meaningless from a technical perspective.
Rather than trying to find standards for the phases of a project, your organisation may have some generic milestones or phases that you are expected to adhere to. If you do have these, they may well be "gates" that you have to pass through by completing certain documents or gaining certain sign-offs, such that without these documents or sign-offs you can't progress to the next phase of your project. If this is the case, then these documents or sign-offs should also be deliverables, and the action of developing or obtaining them are tasks for your WBS too.