This is a very interesting idea. I think aliases are very helpful and important when you are trying to manage knowledge rather than just build a databased based tool.
CIDOC-CRM, an ontology that is used for cultural heritage, has an entity called appellation which I always found very interesting an instructive since not only does it allow different names to be associated with the same entity, but it also allows for more context for how that name applies, things like the language/context/place where the name is used, the period that name was in use, … . This is a very specific application of a knowledge graph. We had some discussions on this here:
While not exactly the same thing, I think being able to describe relationships between entities in the system that are basically fragments of the same thing (e.g. a contact in CRM, an employee in HR database and a user in the authentication database contain fragments of information about the same person):