You can use multiple relationships in a tagset, but a list of relationships is static I.e., the choice of relationships is not dependent on the items you are connecting. As I understand it, you are wanting different relationships depending on the type of items you are connecting.
Further, auto classification will always use a single relationship. What we typically do is run a set of rules, post classification, to transform this single relationship into different relationships reflecting the type of connected items. For example, if there is a tagging link between an agency and a function, a rule could generate ex:activity link between them.
Having said this, the auto classification algorithm is about tagging documents (content) with the most relevant concepts, based on the document text. I am not sure where is the content in the agency and function example. Rule processing I have described is typically used where tagging concepts are of different type and a relationship between a document and a tag would differ, depending on the type of a tag e.g., if it is a Geo Concept, relationship may be ‘location’, if it is a business, relationship may be ‘organization’, etc.
Once generated, you will be able to easily see these links in the default view of the Tagset editor if these relationships are amongst the possible tagging relationships. Otherwise, you would need to use a different view to see them.
Similarly, for manual tagging, you will be able to use these relationships if they are on the list of possible tagging relationships.
For crosswalks, the links created through the built-in auto-mapping algorithm will always use a single selected predicate. There is a way to plug in custom mapping algorithms. The default UI (crosswalk table), will only show side by side items connected by the currently selected mapping predicate. Again, you would need to use an alternative layout to see items connected by any predicate.
Sent from my iPhone