When an actor plays himself...interesting edge case

When an actor plays himself in a film, the performance entry triggers the actor topic to be co-typed as:
- Film character
- Fictional character
- Film actor
- Person
OK, a little strange, but understandably so.

But the explosion of parallel and confusing properties that then appears on the actor's page becomes rather difficult to navigate:
- Gender, Place of Birth, Parents, Children, Siblings, Quotations, all appear twice (Person, Fictional Character)
- Married To (Fictional Character) vs. Spouse(s) (Person)
- Profession (Person) vs. Occupation (Fictional Character)
- Employment History (Person) vs. Employers (Fictional Character)

What amuses me is that the Person type has an Education property missing from Fictional Character, while Fictional Character has Powers or Abilities that we didn't give to Person. There are additional properties unique to each type.

This is an extreme case, but one problem is that it's hard to figure out which property belong to which type. Perhaps the actor himself is married with kids but plays a single version of himself on screen. And if he happens to have a brilliant line in the film (Quotation property), credit should be given to the writer as well. Perhaps a UI feature to indiate/group properties by type?

Another problem is duplicate properties (that belong to the same universe) that result from co-typing. But I guess the solution to that is at the schema level rather than any UI feature.