The 880 field is special, we would really need to check subfield 6 to see how it should be interpreted, but that information is not available in the URI generated by marc2bibframe2.
As a stopgap we could always generate Person (P) URIs from 880, as it's more likely that they represent persons than organizations, but the real solution is that the rewrite process should check the rdf:type of entities instead of parsing the marc2bibframe2-generated URIs for type information.
E.g. http://urn.fi/URN:NBN:fi:bib:me:O00000698301 generated from http://urn.fi/URN:NBN:fi:bib:me:000006983#Agent880-32
The 880 field is special, we would really need to check subfield 6 to see how it should be interpreted, but that information is not available in the URI generated by marc2bibframe2.
As a stopgap we could always generate Person (P) URIs from 880, as it's more likely that they represent persons than organizations, but the real solution is that the rewrite process should check the rdf:type of entities instead of parsing the marc2bibframe2-generated URIs for type information.