All children of a pattern are a group.
If you know the name you can use Lookfor set to Feature, Lookby probably set to Feature, and Attribute Name using HOLE* as the argument, and comparison as equals.
I notice that under feature I left the Lookby as <several> Probably ran out of time or had more pressing things to get to. Anyway, there could be some Lookby in there that applies.
My typical setup attaches searches to layers to put all datum planes on the datum_planes layer AND not datum planes that are on the xsection layer AND not on the construction layer. So, if I add a datum plane that is a section or is part of construction geometry, the plane is automatically not eligible to be on the datum plane layer anymore.
I mention the above as it is an example of compounding the criteria to select from many candidates and use OR to join otherwise disjoint sets, and AND with negatives to reject some of those candidates that are otherwise included in the initial sets.
Check out the number of places one can extract a Note from.
Not missing really, but not available is the ability to cascade - looking for the parent of child of a selected item. You can do the forward operation, select the parent or child of an item, but you can't, for example, select all the notes the belong to the parents of an edge. Programming wise - only an initial level of indirection, not recursive. Maybe I'm looking at it wrong and it is possible. I'll be pleasanly surprised.
