Does PMBoK have a project phases structure (stage names)?

do you speak french?

I studied in a French school (Colleges Des Freres) but that was long time ago so I forgot a lot but I can still speak (Intermediate) and I mostly understand everything I hear or read but writing not that good anymore although I am practicing.

You have to read the PMBOK and all your answers are there. PMBOK is a guide to apply project management best practices. The method and the phases (project life cycles) to use is up to you.

I would agree with Mounir Ajam on this and would like to point you in another direction. PRINCE2 defines the lifecycles and phases in a even better way, but naturally not in conflict with PMBOK Guide. They have three lifecycles running in parallel in a project, project management, technical and administrative. Project management and Technical phases can still have some overlaps but administrative phases are surgically separated even breaking and dividing the project management ad technical phases. You still have the freedom to have as many phases in your project and name them accordingly. I would say number of phases in any project should and could not be in double figures or it will make the project impossibly complex. I will go for 3-7 phases in a project with their names closely resembling the technical work done in each. PMBOK Guide also explains the same concept but not in so many words, but if you want to understand the whole story, you have to refer to material outside of PMBOK Guide.

Hi Sylvain,
let me make a clarification: PMI and PMBOK don't define a methodology by a body of knowledge that are needed for a excellent Pm practice.
The fundamental concept is the tailoring: you are not supposed to apply all element indicated in the PMBOK but only these ones which are needed for your project. In other words for little projects the project management could be simplified respect a bigger one; they can have phases or not, this is not the matter.
The most important issue is that you should work in the five process areas DURING the project life cycle. Process areas are "iterative elements" which you should consider and use during the project for adjusting it to the new elements known regardless the project is divided in phases or not

No problem. I am here to learn from others so a challenge is welcome.
1-Is the definition of what a BOK is. Each BOK you read (BABOK, PMBOK, SEBOK, EABOK, etc) is a subset of knowledge generally recognized as best practices. See point 1.1 inside the PMBOK but you will find the same definition into each BOK you take.
2-when you say "do not understand it", in what context? PMBOK is easy to understand. The problem is people do not understand that you have to separate the approach (agile, lean, etc) from the life cycle (waterfall, V, Spiral, etc) and from the guide or principles you will use (PMBOK, IPMA, GPM, etc).
There is a hugh missunderstanding. Unfortunatelly. And let me say: more and more a project manager will add value to organizations when really understand the above separation of concerns each time is assigned to a new initiative.