The process is straightforward. If you query the help information for the TypeName parameter of Remove-TypeData, you would notice that it accepts the type name accepts input via the pipeline by property value as well as the property name. Recall the recipe, Understanding pipeline-enabled parameters, and look at the object returned by Get-TypeData, for more insight.

The Remove-TypeData cmdlet removes the type data from the current session. This removal is as ephemeral as the type addition is. Therefore, the default types and formats are not permanently removed by the cmdlet; the reason why you can run this within PowerShell, without administrator privileges. Also remember that the underlying XML files are not deleted either: custom or stock.