I find the notion of types and tokens useful in these cases.
A type is a class and a token is an instance of the class. (If that is unintuitive, try this: A type is a set, and a token is a member of that set.) A type can itself be a token of another, higher-order type. (So green and verde are tokens of green (type), which is itself a token of colors (type).) We can put these ideas to work in Obsidian with links, embeds, and the backlinks panel.
You could do a whole type/token hierarchical thing in Obsidian and link your notes to that, or your could add Such-and-Such (Type) records as needed with a list of links or embeds to the records with notes and have them serve as the “tokens” in this relationship. In your case, I might do something like this:
Green (Type)
Maybe a definition or color swatches.
New notes go here
Embed green here
Embed verde here
Now you can read everything in one place without messing with links on other notes. Still, after following a link to one of those embedded notes I might forget to check its backlinks panel for type/token relationships. I want to make sure that I follow links all the way to the merged note. So, let’s add some links to green and verde.
Green
Instance of (or token of, or member of): Green (Type) (Takes me to the merged note.)
Existing notes here, as well as any new notes about green that aren’t really about verde. Or you can just notes to green and verde respectively however you do today.
Verde
Token of Green (Type)
etc.
The relationships between your notes and these ideas will still be pretty apparent from the Graph View.