= Solution
\b[A <monophyletic group> includes an ancestor and all its descendants; a <paraphyletic group> includes an ancestor but excludes some descendants; a <polyphyletic group> combines separate lineages while excluding their relevant common ancestry.] The distinction concerns how membership relates to a <phylogenetic tree>, rather than how many visible similarities the members possess.
Consider a simplified tree of living <amniotes>: <mammals> form one branch, while the other contains <lepidosaurs>, <turtles> and <archosaurs>; living <archosaurs> comprise <crocodilians> and <birds>. Within the latter branch, <birds> are surviving <dinosaurs>. The tree below omits extinct branches and most living diversity, and its branch lengths represent neither age nor quantity of evolutionary change. It illustrates three choices of group on the same ancestry.
\Image[/past-exam-of-the-zoology-course-of-the-university-of-cambridge/2025/paper-zm1-classification.png]
{title=Three ways to select vertebrate groups on one schematic phylogenetic tree}
{description=Original schematic. Green selects the archosaur ancestor and all sampled descendants. Orange retains the sauropsid ancestry and nonavian branches while excluding birds. Blue selects independently endothermic terminal lineages while their connecting ancestry remains outside the functional group. Extinct branches are omitted.}
A <monophyletic group> is a <clade>. <Archosauria> includes the last common ancestor of <birds> and <crocodilians> and every descendant, including extinct <dinosaurs> and other extinct branches. In the simplified figure, selecting their shared node and both descendant tips gives the corresponding complete subtree. <Sarcopterygii>, with <tetrapods> included, is another example. A <clade> need not be recognized by a feature that remains visibly unchanged in every descendant: subsequent modification and loss are permitted. It also need not have a particular taxonomic rank.
A familiar <paraphyletic group> is the traditional assemblage “reptiles” when it includes <turtles>, lizards, snakes and <crocodilians> but explicitly excludes <birds>. The latter descend from within the ancestry otherwise assigned to that assemblage. The selected ancestry is therefore cut short at one of its own branches. Similarly, conventional “fish” that include finned <sarcopterygians> but exclude <tetrapods> form an evolutionary grade rather than a complete <clade>. These examples require the stated usage: <Reptilia> or <Sauropsida> can instead be defined as a <clade> that includes <birds>. The everyday word does not irrevocably determine the phylogenetic status of every technical definition bearing that name.
For <polyphyly>, consider assembling <mammals> and <birds> solely as the familiar independently evolved examples of sustained high metabolic heat production, while omitting their intervening ancestors and other descendants. This physiological grouping can be useful for comparing <endothermy>, but it does not identify one exclusive historical lineage. Their last common ancestor also has descendants such as <lepidosaurs> and <crocodilians>. On the usual inference of independent elaboration of the relevant physiology, the selected resemblance involves <convergent evolution>. Calling the assemblage “warm-blooded <vertebrates>” must not turn a selected physiological trait into evidence that <birds> are closer to <mammals> than to <crocodilians>. Moreover, <endothermy> and constant body <temperature> are not identical properties, and living taxon sampling does not locate every thermophysiological transition in extinct lineages.
There is a subtle distinction between the last two cases. A diagram of selected terminal tips alone can show that a group is not a <clade>, but does not always uniquely distinguish <paraphyly> from <polyphyly>. One must state which ancestors are included and the historical interpretation of the defining character. In the orange example, the ancestral reptile lineage is retained and one descendant branch excluded. In the blue example, similar functional outcomes are assembled from separate branches without including the connecting ancestry. The highlighted internal paths in the figure make that difference explicit.
<clades> are particularly suitable for discussing <vertebrate> <evolution> because their nested membership directly expresses <common descent>. They permit consistent statements such as “<birds> are <dinosaurs>” and “<humans> are <sarcopterygians>”, while allowing substantial changes in form and function. Shared derived characters, or <synapomorphies>, provide evidence for branches; shared ancestral states do not uniquely diagnose the smaller groups inheriting them, and independently acquired similarities require separate explanation. This framework makes character transformations testable against a branching history instead of arranging animals in a ladder of increasing complexity.
In practice the <phylogenetic tree> remains a hypothesis. More characters, better <fossils> or different evolutionary models can change inferred relationships. Naming a <clade> with an explicit ancestry-based definition helps keep the statement intelligible when that happens, but does not make the inference immune to error. Anatomical and molecular characters need <biological homology> assessment, appropriate taxon sampling and uncertainty estimates. For example, genome-scale data and stem-turtle <anatomy> independently address whether <turtles> lie near <archosaurs>, rather than treating one <skull> condition as sufficient to define the tree.<More than 1000 ultraconserved elements provide evidence that turtles are the sister group of archosaurs by Nicholas G. Crawford and others>[Taxon sampling and phylogenomic support for turtle placement]{ref}
\b[Use <monophyletic groups> to express ancestry, and identify ecological or anatomical grades explicitly when they serve another purpose.] <paraphyletic groups> can summarize retained ancestral organization, and <polyphyletic groups> can support functional comparisons, but neither should silently substitute for a complete lineage.
Back to article page
