The question should be about binary trees (BTs) in general, not just binary search trees (BSTs), since the order of the data in the nodes has nothing to do with whether or not the tree is balanced. One place to start is https://en.wikipedia.org/wiki/Binary_tree, but it has some problems since it is a bit of a mish-mosh of various possible definitions, some from CS and some from graph theory. Probably the most useful, non-contradictory set of definitions is:
A BT is perfect or height-balanced if every leaf is at the same level, which is equivalent to every path from a given node to a leaf being the same length; it is full if every internal (non-leaf) node has 2 children; it is complete if it is perfect and full; it is almost complete or nearly complete if is perfect and all levels but the last are full, and in the last level leaves are as far left as possible (so any "vacancies" are to the right); it is degenerate if every non-leaf node has just one child (and as a graph it is a path from the root to the one leaf).
Using these definitions: your first tree is perfect but not full, so not complete--node [b] is missing a left child, and adding it would make the tree complete; your second tree is degenerate (a path); your third tree is full (every node but the leaves has two children) and 1-height-balanced but neither "perfectly balanced (= perfect?)" or "balanced (meaning 0-height-balanced)" as you claim, since not every path from the root to a leaf is the same length.
In your first tree, if [b] had two children but [p] had only a left child, then it would be almost complete (perfect and full except for some missing children in the last level and the vacancies as far right at possible)--and these are important for storing binary heaps in arrays.
Sergio's example is complete (perfect or height-balanced, and full). (And note that it's not nice and can only cause confusion to use "balanced" to mean "1-height-balanced", or "perfect" as a synonym for "complete".)
Something less strict than being perfect (or perfectly-balanced) is being k-height-balanced, which means that the lengths of all paths from a given node to a leaf differ by at most k, which is equivalent to the difference in height of each node's left- and right-subtrees being at most k. For example, an AVL tree is 1-height-balanced.
The reason "height" is needed in these definitions is that there is a different concept of "weight-balanced BT", which has various definitions depending upon the use, with one being that for each node the number of nodes in the left sub-tree is the same as in the right sub-tree, and another being that the number of nodes in the left sub-tree is at least half and at most twice the number of nodes in the right sub-tree.