Traps are not really supposed to be transformed into something that looks like the English language, they're really designed to be consumed by computers.
if you read the MIB then it will explain the meaning of various fields. In this case whatever you are monitoring is making use of the RFC event MIB to indicate an interface had gone over a threshold.
grab your ascii table and decide this as:
188.8.131.52.184.108.40.206.102 = s i n g l e _ v f
220.127.116.11.48. = G i 0 / 0
I'd have expected the Target and Context name to have been filled in with some useful value.
Anyway, without knowing anything about what sent in this trap, I'm going to hazzard a guess this is some alert from an IPS indicating the bandwidth on a 100Mbps interface Gi0/0 reached 99% ?
I agree and disagree with you. I found something in Solarwinds that can make these OIDs english but you do have to pay for it. It is in the Solarwinds Engineering ToolSet. Once I have an actual and final answer I will post it so everyone can make use of it and how I changed it to say something that people who did not study SNMP can use.
the challenge of snmp indexes is that they are trap-specific, for example there is nothing that prevents mteHotOID ending with (say) 0.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.39.18.104.22.168.0.0.0.101.0.0.0.0.0.26.203
which might be used for an event cause by an IPv6-related event (for example the number of BGP prefixes exceeding a limit), and in that case has no textual equivalent (it does have an IPv6 equivalent)
For Internet-standard MIBS especially one gets into the (various) vendor interpretation of what was intended.