ELI5 version>
Let's put it this way:
Imagine you are a Slavemaster and you there is some work that needs to be done.
You have a two slaves - Igor and Andy... You also have whip and a drum, because whips and drummers are cool.
The amount of work done is heavily influenced by the frequency you beat your drum /aka - the frequency or tact the poor fellows must work by/ and their own skill /aka - the amount of instructions they can do per one beat - IPC/. Slave Igor can do about 5 things in a beat while slave Andy only 3. Also their different upbringing /aka the architecture/ helps Igor to rely on himself /single-thread/ and helps Andy to work in team, because that is what he preffers /multi-thread/.
Thus you need to whip slave Andy faster, so he can do the same amount of work as Igor.
This is why Igor has the single task /single-thread/ advantage over Andy.
NOW... let's think...
Now, you got the bright idea to tie two Andys together /aka - the philosophy of an AMD module/, so the work goes faster.
You can imagine what happened - even two Andys can not beat a single Igor if there is not heavy work that can be split evenly between them /aka - well threaded multi-threaded applications/. When there was heavy work involved two tied-together slaves were better than one.
But now, the poor Igor was be left in the dust.
But you, as a great Slavemaster, noticed that Igor has two arms. You ordered him to take two things at the same time if his second arm is idle /aka - Intel Hyper-Threading/. Igor has now better work results as Andy, because there is only a tiny speck of hard work that really needs two people. What is mostly done can be done either by one person /single-thread/ or needs a little help from the other /light multi-thread/.
And don't forget, Mr. Slavemaster: the faster and harder your slave work, the more food they require and the more they sweat - so unless you want them to collapse, you need to keep them cool and well fed