Menu and taxonomy overview
The two forms every site administers a tree with, built with the properties core sets, in the same places and with the same values: the links table of a menu and the terms table of a vocabulary. They are not the same table -- a vocabulary prints the state of a term in words, leaves the parent field visible, writes the depth back and is paged, so its table also holds the rows either side of this page, a second button and a pager. The trees are made up and nothing is saved.
Menu links
The table of /admin/structure/menu/manage/main, without the title, the summary and the machine name of the menu above it. Six columns wide although the header names four of them, because the two hidden fields tabledrag writes a new position into are cells of their own; the check box in the second column is whether the link is shown, not whether the row is picked; and a disabled link says so twice, once in the check box and once in the cell beside it.
Vocabulary terms
The table of /admin/structure/taxonomy/manage/topics/overview, with the help text over it and the pager under it. Four columns and three hidden fields, all three inside the first cell rather than beside it. The first and last rows belong to the pages either side of this one: they are printed so that a term can be dragged onto them, they carry a class saying so, and the rows across the join from them carry another. A vocabulary short enough to fit on one page has none of that, which is why it is so easily missed.