Based on my reading of the paper, I assume you could generate a "join key" that included both types of prefix tokens - say user names and birth date information, along with a "join type" field.
Then in the GroupBy step you'd use both the join key and the join type fields, so that you're not mixing apples & oranges when applying the principle of "at least one token in the join key prefix must match, for two records to be similar".
-- Ken
--------------------------
Ken Krugler
custom big data solutions & training
Hadoop, Cascading, Mahout & Solr