This is what I meant above by a Collection type, since here you define that this prov:Collection is a fs:stat_measures collection type.

I'm wondering if it makes sens to have nested Collections here... In some ways you could really just have one collection, where all the fs:stat_header properties could simply be properties of the collection. So something like:

<http://nidm.nidash.org/iri/1152fb70d3b911e28ae7001e4fb1404c> a fs:stat_measures, prov:Collection, prov:Entity ;
    ... all of the fs:stat_header properites
    fs:AnnotationFile "../label/rh.aparc.a2009s.annot" ;
    fs:NTableCols "10" ;
    ...
    ... followed by all of the members below

What do you think? From the query perspective would this approach be easier or harder?