In reply to Coppola:
From cookbook:
Specific sequences can be overridden via their “path” in the UVM testbench component hierarchy. For
uvm_components, the path is defined as part of the build process via the name and parent arguments to the create
method. However, sequences are uvm_objects and only use a name argument in their constructor and are not linked
into the uvm_component hierarchy. The solution for creating a path for a sequence is to use two further arguments to
the create method. The third argument passed to the sequence can be populated by the results of a get_full_name()
call, or it can be any arbitrary string. The instance override then uses this string concatenated with the instance name
field of the sequence to recreate the “instance path” of the sequence. For obvious reasons this means that a sequence
instance override has to be pre-meditated as part of a sequences architecture.