Lexical access in bilingual speakers

What's the (hard) problem?

Matthew Finkbeiner*, Tamar H. Gollan, Alfonso Caramazza

*Corresponding author for this work

Research output: Contribution to journalArticle

115 Citations (Scopus)
149 Downloads (Pure)

Abstract

Models of bilingual speech production generally assume that translation equivalent lexical nodes share a common semantic representation. Though this type of architecture is highly desirable on both theoretical and empirical grounds, it could create difficulty at the point of lexical selection. If two translation equivalent lexical nodes are activated to roughly equal levels every time that their shared semantic representation becomes activated, the lexical selection mechanism should find it difficult to "decide" between the two (the "hard problem") - yet in some cases bilinguals benefit from the presence of a translation equivalent "competitor". In this article, we review three models that have been proposed as solutions to the hard problem. Each of these models has difficulty accounting for the full range of findings in the literature but we suggest that these shortcomings stem from their acceptance of the assumption that lexical selection is competitive. We argue that without this assumption each proposal is able to provide a full account of the empirical findings. We conclude by suggesting that the simplest of these proposals should be rejected before more complicated models are considered.

Original languageEnglish
Pages (from-to)153-166
Number of pages14
JournalBilingualism
Volume9
Issue number2
DOIs
Publication statusPublished - Jul 2006
Externally publishedYes

Bibliographical note

Copyright 2006 Cambridge University Press. Article originally published in Bilingualism : Language and Cognition, Volume 9, Issue 2, pp. 153-166. The original article can be found at http://dx.doi.org/10.1017/S1366728906002501.

Fingerprint Dive into the research topics of 'Lexical access in bilingual speakers: What's the (hard) problem?'. Together they form a unique fingerprint.

Cite this