Tuesday 15 April 2014

The Guess List: a study in /t/ elision

The BBC is airing a new game show on Saturday nights hosted by the wonderful Rob Brydon and amusingly entitled The Guess List. You can read the Independent newspaper's less than glowing review of it here.

Why amusing?

This plays on a phrase, the guest list, which is a list of people invited to an event, i.e., a list of guests. No surprise there.

What amuses me is that it is an example of how the process of alveolar plosive elision can result in homophones in English - in this instance, a homophonic phrase.

When one produces the phrase the guest list in rapid speech, it is normal to leave out the /t/ sound at the end of /ɡest/.  This process is called /t/ (or /d/) elision.  The rules for when this can take place are as follows:
  1. The /t/ or /d/ must be in the syllable coda;
  2. It must be surrounded by other consonants;
  3. The consonant preceding the alveolar plosive must agree in voicing with it - so if the plosive is a /t/ it must be preceded by a voiceless consonant and, if it's /d/, it must be preceded by a voiced one.
  4. The consonant following cannot be /h/.
So, in guest list, which can be transcribed phonemically as /ɡest lɪst/, we can elide the /t/ at the end of /ɡest/ because it meets the requirements listed above.  This results in /ɡes lɪst/, which means guest list and guess list are homophonous.

There is, as far as I know, no such thing as guess list as a phrase in English. If one types it into Google, for example, it redirects you to guest list.

Other notable examples of homophones resulting from connected speech processes include handbag /hændbæɡ/ becoming homophonous with ham bag /hæmbæɡ/. There are two processes going on here: /d/ elision and assimilation.

Assimilation is a process by which sounds at word boundaries - often alveolar consonants - become more similar to each other in rapid speech. Here's a diagram showing consonants at word boundaries:

_ _ Cf | Ci _ _

Cf = final consonant; Ci = initial consonant

In English, we tend to get regressive assimilation, which means the initial consonant (Ci) at the beginning of the next word has a backwards effect on the final consonant (Cf) of the preceding word. As I mentioned above, this tends to affect alveolar consonants, and more often than not it will affect the place of articulation of Cf, i.e., it will not be produced as an alveolar consonant but will have the same place of articulation as the Ci of the next word.

In handbag /hændbaɡ/, the alveolar plosive /d/ is elided and the alveolar nasal /n/ is produced as a bilabial consonant because the following word - bag - begins with a bilabial consonant, /b/.  This results in the production /hæmbæɡ/, which is homophonous with ham bag. But of course, a lady wouldn't normally take a bag of ham out with her when she went shopping, and we can usually retrieve the real meaning from the context.

I should add a caveat in that this is a very brief overview of the theory of these two processes. In very rapid speech, all sorts of sounds get elided and / or assimilated, so analysing spontaneous speech can be a real challenge.

Another issue which arises from connected speech processes such as elision and assimilation is that they can make speech less intelligible or the message more difficult to understand.  Emilio's comment below led me to this example, spoken by Elizabeth Taylor and Richard Burton in Who's Afraid of Virginia Woolf? In it, there is /t/ elision in the word guests, which is perfectly legal. You can see how Burton's character doesn't understand Taylor's character until she repeats the word guests with the /t/ in it - although what "We've got guess" (as opposed to "We've got guests") might mean is difficult to ascertain.  There are obvious issues for speech intelligibility here in English as an international lingua franca.

Watch from 04:04 right near the end.  And thank you, Emilio!



I'd recommend the following books by way of introduction if you are interested in connected speech processes in English:

Lecumberri, M L G & Maidment, J. 2000. English Transcription Course. London: Arnold.

Roach, P. 2009. English Phonetics and Phonology: A practical course. Cambridge: Cambridge University Press.



50 comments:

  1. For me, at least, guest list has a glottal stop and guess list does not, because I glottalize coda /t/ even in lento speech. (I don't, however, make it a glottal stop altogether.)

    ReplyDelete
    Replies
    1. How interesting, John. This seems rather counter-intuitive from a speech production point of view as the point of CSPs is to make rapid speech more fluent. Is this a feature of your regional accent?

      Delete
    2. For me, a /t/ following /s/ can never become glottal. I always assumed that was true for other native speakers, too. And I can't make any sense of the claim "I don't ... make it a glottal stop altogether".

      Delete
  2. Nice game: Find homophones which result from assimilation!

    ReplyDelete
  3. I hope this is not very illegal, but if somebody wrote youtube.com/watch?v=mwmlxSevYXE in the appropriate space, then they would have the opportunity to listen to the following dialogue at 4:03:
    GIRL.- We’ve got gues(t)s.
    BOY.- The wha(t)?
    GIRL.- guest(s)! Gues-T-s.
    BOY.- Guests?
    GIRL.- Yeah, guest(s). People! We’ve got gues(t)s coming over.

    ReplyDelete
    Replies
    1. That's a nice example, Emilio! I'll add it into the blog post if I may. It shows how these processes can make speech less intelligible, even to native speakers of English!

      Delete
    2. Thank you, Jane (and also Liz and Richard)! :-)

      Delete
  4. Linking, more than elision, but I love it anyway:

    A: Whatime did you getup today?
    B: Got a potato day.

    Works in BrE.

    ReplyDelete
  5. This comment has been removed by a blog administrator.

    ReplyDelete
  6. This comment has been removed by a blog administrator.

    ReplyDelete
  7. This comment has been removed by a blog administrator.

    ReplyDelete
  8. This comment has been removed by a blog administrator.

    ReplyDelete
  9. This comment has been removed by a blog administrator.

    ReplyDelete
  10. This comment has been removed by a blog administrator.

    ReplyDelete
  11. This comment has been removed by a blog administrator.

    ReplyDelete
  12. This comment has been removed by a blog administrator.

    ReplyDelete
  13. This comment has been removed by a blog administrator.

    ReplyDelete
  14. This comment has been removed by a blog administrator.

    ReplyDelete
  15. This comment has been removed by a blog administrator.

    ReplyDelete
  16. This comment has been removed by a blog administrator.

    ReplyDelete
  17. This comment has been removed by a blog administrator.

    ReplyDelete
  18. This comment has been removed by a blog administrator.

    ReplyDelete
  19. This comment has been removed by a blog administrator.

    ReplyDelete
  20. This comment has been removed by a blog administrator.

    ReplyDelete
  21. This comment has been removed by a blog administrator.

    ReplyDelete
  22. This comment has been removed by a blog administrator.

    ReplyDelete
  23. This comment has been removed by a blog administrator.

    ReplyDelete
  24. This comment has been removed by a blog administrator.

    ReplyDelete
  25. This comment has been removed by a blog administrator.

    ReplyDelete
  26. This comment has been removed by a blog administrator.

    ReplyDelete
  27. This comment has been removed by a blog administrator.

    ReplyDelete
  28. This comment has been removed by a blog administrator.

    ReplyDelete
  29. This comment has been removed by a blog administrator.

    ReplyDelete
  30. This comment has been removed by a blog administrator.

    ReplyDelete
  31. This comment has been removed by a blog administrator.

    ReplyDelete
  32. This comment has been removed by a blog administrator.

    ReplyDelete
  33. This comment has been removed by a blog administrator.

    ReplyDelete
  34. This comment has been removed by a blog administrator.

    ReplyDelete
  35. This comment has been removed by a blog administrator.

    ReplyDelete
  36. This comment has been removed by a blog administrator.

    ReplyDelete
  37. This comment has been removed by a blog administrator.

    ReplyDelete
  38. This comment has been removed by a blog administrator.

    ReplyDelete
  39. This comment has been removed by a blog administrator.

    ReplyDelete
  40. This comment has been removed by a blog administrator.

    ReplyDelete
  41. This comment has been removed by a blog administrator.

    ReplyDelete
  42. This comment has been removed by a blog administrator.

    ReplyDelete
  43. This comment has been removed by a blog administrator.

    ReplyDelete
  44. This comment has been removed by the author.

    ReplyDelete