Ha, yup. I think a good corollary is prefix vs. infix notation in programing languages. With prefix (or RPN) notation, it's impossible to be led down the garden path. The rules are simple and unambiguous.
For example, 4+5×3 is a garden path, where reading left-to-right you may think to yourself, "four plus five is nine, then nine times... wait, I have to backtrack and handle five times three first..."
Whereas + 4 × 5 3 can't be confused. (Or 4 5 3 × + in RPN)
I'm not a (good) speaker of any other language than English, but I can see how adjective/verb/noun ordering in different languages can prevent this problem.
Argh! You're right; I got the words out of order. It should be:
The girl the boy the dog bit hit cried.
I tried parenthesising it; I tried Lisp syntax (you're right; it's the mix of direct and indirect objects that complicates things); nothing worked. It's a diabolical sentence. The best I could come up with was this:
To say that it exists in all languages is perhaps a bit strong, but, yes, most do. However, there are difference in the degree to which ambiguities occur. German, for example, has many morphological cues that allow the comprehender to rule out alternative interpretations. The price is that German tends to be slightly more verbose.
I don't think that's an example of a garden path sentence though. My initial parse is "whether or not suffering in the mind is nobler". "In the mind" is an adverbial phrase that modifies "to suffer". Am I missing anything?
Maybe I've misunderstood all this time, but I thought "in the mind" meant to think about suffering, not literally suffer in the mind. That is to say, more like "whether or not one thinks suffering is nobler".
The name "garden path" reminds me that during my Turbo Pascal loving 80s I played with making “fog” from markov chains. The idea was to computer-generate reasonable-reading nonsense text and I'm sure you've all tried it as kids too! :)
Of course my naive approach suffered from lack of corpus; if it picked a rare word, it’d get railroaded into using the very limited set of words that follow that rare word and so on.
I remember running it - this was before the internet days, so I can’t imagine where I got the input text from - and getting back a page-full of gobbledygook. And there right in the middle, somehow drawing the eye like a magnet, was one of those railroaded sentences:
herbaceous
Well when your random roulette picks the word herbaceous, its likely only seen it once or so in its learning text, so there aren’t so many words it can pick next:
But it turns out all of those are you. Does your computer beep every time somebody posts about markov chains, so that you can go post this comment? Do you have it saved on your machine, ready for copy paste?
Heh, I think it's actually useful. Cross-posting is sort of a form of intellectual cross-pollination; some people are allergic, but others appreciate the second chances. I don't read those other forums, so I'd have missed out on that little nugget.
And I tried to make that last sentence a garden path one, to keep the comment on topic, but jeez it's hard to break the habit of avoiding them. I suspect it's deeply ingrained in me to an instinctual level by my 11th grade rhetoric teacher. (Her whole goal was to, and I quote, "make our insides scrunch when we saw a comma splice." Most who took her class would agree her curriculum was a resounding success, even after she also taught us to break the rules.)
I think in real-world situations speakers would prefer "fruit flies like bananas", which may also be a garden path sentence, but its resolution seems much easier to me.
Do native speakers concur?
Is there any research whether speakers do prefer utterances like my example in practice due to this property?
The sidebar shows two other languages for this Lemma, the Dutch one is interesting:
* Intuinzinnen, From the Dutch proverbs "ergens intuinen" of "om de tuin geleid worden". Literally: To "be gardened into something", or "to be led around the garden." Both meaning the same as "lead someone down the garden path"
Seams the proverb is nearly similar in both languages. Which makes me wonder whether they originated from the same word. After all, Dutch and English (And German, Danish and Swedish) have the same common ancestor.
Or whether they describe the same, in the past generally known effect of garden paths leading to unexpected dead ends.
No. 'tuin' etymologically is 'town'. Both originally described an enclosure (around a piece of ground). From there, it became the piece of ground within in both languages (http://www.etymonline.com/index.php?term=town)
Garden is from French (jardin)
Back to the proverb: the dutch one seems to be about "keeping someone from that what is important/the truth" by not letting them in.
Nah, this just means that language did not evolve to be written. In spoken language, these ambiguities are not a problem because of prosodic cues. Also, non-recursive languages are not necessarily unambiguous, which shows that this problem is not tied to recursion.
As a native British English speaker I didn't actually have any trouble parsing any of the sentences save for the "The horse raced past the barn fell" because it was written without the customary punctuational scaffolding.
'The old man the boat' seemed fine to me too, not sure why.
I'd be interested to hear if other British English folks had much trouble with these sentences. Perhaps it's a by product of being exposed to too many 'dad jokes' (Fruit flies like a banana) but perhaps it's a more general condition of British English humour that made me feel familiar with this type of sentence structure.
Nice examples. "Old man" is a much more common adjective/noun construct than "wet tear", "crooked defect", and maybe even "quick pace", though, so I think these are slightly easier to parse. But "hot lead" is excellent :-)
I don't know whether "the hot lead the cold" and "the wet tear off their clothes" are made easier, or harder, to parse by the fact that when one (or at least I) reads them, one assigns a pronunciation to the 3rd word en passant. (I picked correctly, as it turned out, so don't know how hard it is to overcome the effect of a wrong choice.)
I'm not sure I would add pauses when saying "the horse raced past the barn died"... mainly because in real life there'd be enough context to parse it properly. These sentences are just very artificial examples.
But that changes the meaning. Consider a situation where you have two horses. One of them has been raced past the barn; the other never has. This matters because inside the barn there is an alien artefact emitting radiation that weakens the muscles. But that was yesterday. Today you have sent both horses out for another canter -- and one of them has suffered a fall. Tell me, Igor, which one was it? Did the radiation from the alien artefact cause the trouble? "The horse raced past the barn fell."
But the version with the commas is only applicable when (1) you already know which horse is being referred to and (2) the fall happens in racing past the barn or at least as an immediate consequence, it seems to me.
A similar phenomenon, at least in English, is that you can (technically) infinitely embed subclauses without using complementisers ("that", "who" and "which"). So you get unparsable things like:
The dog the cat the mouse feared loathed barked.
...punctuated and complementised makes it slightly better:
The dog, who the cat, who the mouse feared, loathed, barked.
...unwound makes it readable, but changes the semantics subtly but significantly:
The mouse feared the cat, who loathed the dog who barked.
I say "technically" because there's nothing stopping you from doing this, but in reality, even one level of embedding can be borderline nonsensical (e.g., the "The horse raced past the barn fell" example).
There's no rulebook when it comes to syntax (grammar), unless you're a prescriptivist. There is plenty of precedent for embedding subclauses (e.g., "Here is a sentence, that I just made up, which has an embedded subclause."), but -- beyond anecdotal data -- there is no hard cut-off point to how many times you are permitted to embed. Empirically, most people don't like more than one level, but plenty of people allow it; thus it becomes more a function of cerebral load than it does an argument of permitted structures.
If you're arguing over technicalities, you are inherently adopting a prescriptivist approach.
There are two possible approaches to your sentence and neither renders it grammatically correct. A prescriptivist would dismiss it as not being allowed by any rules while a descriptivist would point out that it defies both common usage and intelligibility.
I would argue there's a large grey zone. It isn't binary, I'd say it is more of a spectrum between prescriptivism and descriptivism. After all, grammar and syntax isn't fully randomized even if largely arbitary. We make certain choices (even if we aren't aware of it) prescriptively which we try to teach each other (even if we aren't aware of it), and the mixing and noise creates a set of choices in the language actively in use that simply needs to be described for what it is. There's recurring patterns of various sources.
And if they allow one sentence to be understood by members of the intended audience that knows the common rules and context and usage well, then that's as valid as it gets. Even if only very few can understand it, the fact that it is possible is enough.
A bit like HTML in browsers - there's the written rules and there's what browsers do anyway, and what's valid in real life is whatever gets the point across.
A prescriptivist would say it follows allowed grammar rules but is still unintelligible.
A descriptivist would say it follows common usage patterns but takes it to such an extreme as to be unintelligible.
You see this pattern more often with proper names:
- That's the house Jack built.
- That's the woman the house Jack built fell on.
- That's the lawyer the woman the house Jack built fell on hired.
- That's the briefcase the lawyer the woman the house Jack built fell on hired carried.
At what point does it become "incorrect"? When it becomes unintelligible to most native speakers?
It's also worth noting these sentences seem much stranger in writing than they do when heard. In writing, most sane people will use punctuation in the examples above. But in speaking, our tone of voice conveys enough context to use more streamlined structures.
Can you point me to the rule disallowing arbitrary nesting? I'm not aware of a rule existing in either direction, besides vague guidelines to write clearly.
Also, which example is 1 level of nesting? I think "That's the woman the house Jack built fell on." is 2 levels nesting, and I frequently hear constructs like that – in speaking. I agree it's rarer in writing though.
For example:
What server is that?
That's the server the consultant Jack brought in set up.
I'd never write that, because it's confusing. But I will naturally say things like that, without any problem in clarity, because you have more granular control over grouping and pausing, etc. If I said a sentence like that, you might hear it more as "That's the server the-consultant-Jack-brought-in set up."
Anyway, sorry if I misread your tone. It just came across very much as "I know what's right, and you're wrong." That might have been me projecting though. :)
By and large, the rules I learned in various English and grammar classes, beyond the initial sentence structure, were prohibitive rather than permissive; there's no rule explicitly _allowing_ arbitrary nesting, because why would need a rule to specify that, but there's also no rule that I'm aware of that _prohibits_ arbitrary nesting.
In fact, the "rule" that matters here is general sentence structure. It's fine to embed a single secondary clause inside a primary clause:
That's the woman [the house Jack built] fell on.
The structure of the inner clause has no further restrictions on it than the structure of the outer clause. Thus, the entire above sentence is perfectly valid as an inner clause to a new outer clause:
That's the lawyer [the woman <the house Jack built> fell on] hired.
There's nothing in any grammar book that I'm aware of explicitly prohibiting infinite nesting of this sort; it's just silly and quickly becomes unintelligible. Though I definitely take Tenhundfeld's point that this sort of structure is a lot more common in spoken language, and in fact it's a lot more easily comprehensible with the aid of vocal cues and tones.
Saying it stops at level 1 implies the valid rule of embedding is a special case itself of an invalid general rule, rather than it being a general rule itself. If the special case is the most common case, does that really imply only the special case is valid? Why?
There's empirical work on this [1] (alas, paywalled): multiple center embedding in speech is rare but exists. It is more common in writing.
There are examples of 2 levels of center-embedding which are clearly grammatical and not hard to understand:
> Anyone [who saw the woman [who committed the crime] at any point] should be questioned.
Others are very hard to understand:
> Anyone [who the man [who the woman shot] killed] should be questioned.
There are many factors that make a sentence hard to understand, not just degree of embedding. Some degree 2 sentences can be easy, and some degree 1 sentences can be hard (e.g. "the horse [raced past the barn] fell", which has only 1 level of embedding).
So if you want to describe English with the rule "no embedding beyond 1 level" then you're going to miss a lot of valid sentences while also failing to rule out lots of invalid ones.
Contrast this with a valid descriptive rule of English, such as "determiners such as 'the' always come before the nouns they modify". I can say "the man died", but "man the died" is never comprehensible under any circumstances and cannot be made better.
No one would say that a sentence with 10 levels of embedding is perfectly fine English. But descriptively, you have the problem that there is no non-arbitrary upper bound on embedding degree: it's not clear when one more level of embedding takes you from grammatical to ungrammatical, and furthermore it depends on the contents of the embedded clauses.
There is also some work I'm aware of, currently in prep for publication, showing that the extent to which people can understand multiply-embedded sentences strongly correlates with IQ (measured by Raven's matrices).
All this suggests that the simplest descriptive rule is to say that English allows center-embedding recursively, but that there are human processing limitations on sentences that create very deep stacks. The "human processing limitations" part is basically the whole field of psycholinguistics: many details have been worked out, but many details are still sketchy.
Thanks for sharing the research, it's fascinating that there has actually been serious investigation of this.
That being said, I still think the rule of 1 level still makes sense (not that all 1 level embeds are valid or easy, but that all embeds beyond 1 level are invalid).
> Anyone [who saw [the woman who committed the crime] at any point] should be questioned.
That sentence has two complementisers, which the OP's sentence specifically did not. Introducing complementisers completely changes the rules and I think makes embedding much more possible.
This is called center embedding, and it's actually the subject of quite a lot of research. Some of this research has led to a distinction between grammatical (which a sentence like "The cat the rat the dog bit chased escaped" may be) and acceptable (which such a sentence is not). Other research has deemed it agrammatical and unacceptable.
My guess is when the parse tree exhausts short term memory. I have no problem reading the sentence with a single nested clause ("the cat the mouse..."), but the one with a doubly nested clause is unreadable ("the dog the cat the mouse..."). Greater nesting levels might be grammatical in an abstract sense but is extremely difficult for people to understand, much like how it's possible to come up with legal C code that results in indeterminate behavior.
I meant "unparsable" in the same sense as garden path sentences are unparsable; in that, they are parsable, but you'll probably have to give it a few tries before you get it.
I love that example! But I don't think it won any awards, because it's fairly easy to extend.
> What did you take the car driving the man who brought the book that I didn't want to be read to out of up away in for?
Almost-untangled form:
> For what reason did you take in the car driven away by the man who brought up the book that I did not want anyone to read words out of [the book] to me?
Although if you are being very specific, I think some syntacticians might treat the "out" in "out of" and the "up" in "bring up" as a different word classes than normal prepositions (the "out" is modifying another preposition's direction, and the "up" is a particle in a phrasal verb [1]). And I think that's one of the reasons the original form is so compelling is that you have some variance in form giving you clues -- the directional modifier, the question-inversion/wh-fronting, the salience of "bring up" -- that make it tantalizingly close to natural. Whereas mine just becomes a churn of words, at least in my reading.
86 comments
[ 4.5 ms ] story [ 120 ms ] threadFor example, 4+5×3 is a garden path, where reading left-to-right you may think to yourself, "four plus five is nine, then nine times... wait, I have to backtrack and handle five times three first..."
Whereas + 4 × 5 3 can't be confused. (Or 4 5 3 × + in RPN)
I'm not a (good) speaker of any other language than English, but I can see how adjective/verb/noun ordering in different languages can prevent this problem.
Some of those verbs are binary operators (transitive), others are unary (intransitive).
In step 1, the dog bit the boy.
In step 2, the boy hit the girl.
In step 3, the girl cried.
The details of the grammar of the languages makes the methods one can use to achieve the initially ambiguous parse different, though.
Of course my naive approach suffered from lack of corpus; if it picked a rare word, it’d get railroaded into using the very limited set of words that follow that rare word and so on.
I remember running it - this was before the internet days, so I can’t imagine where I got the input text from - and getting back a page-full of gobbledygook. And there right in the middle, somehow drawing the eye like a magnet, was one of those railroaded sentences:
herbaceous
Well when your random roulette picks the word herbaceous, its likely only seen it once or so in its learning text, so there aren’t so many words it can pick next:
herbaceous border
So far so good. But where does this lead next?
herbaceous border disputes
Love it!
Or is it a meme by now? Google finds four results of this phrase:
http://williamedwardscoder.tumblr.com/post/13292744100/the-s...
https://www.reddit.com/r/programming/comments/sgght/comparin...?
https://www.reddit.com/comments/108q4b/markov_chain_poem_tra...
http://encode.ru/threads/2225-A-jackhammer-it-doesn%E2%80%99...
But it turns out all of those are you. Does your computer beep every time somebody posts about markov chains, so that you can go post this comment? Do you have it saved on your machine, ready for copy paste?
I feel like I'm in an XKCD strip right now.
So sorry it offends you.
And I tried to make that last sentence a garden path one, to keep the comment on topic, but jeez it's hard to break the habit of avoiding them. I suspect it's deeply ingrained in me to an instinctual level by my 11th grade rhetoric teacher. (Her whole goal was to, and I quote, "make our insides scrunch when we saw a comma splice." Most who took her class would agree her curriculum was a resounding success, even after she also taught us to break the rules.)
herbaceous border disputes has become one of my favourite stories about markov chains. It's part of internet lore for me :)
Anyway, no harm in sharing willvarfar. First time I've seen your comment!
The guy who had told the story before who had told the guy who had told the story before had forgotten had forgotten.
> Does your computer beep every time somebody posts about markov chains
I haven't done any actual counting, but I'm like 80% sure Markov Chains have been mentioned more than 4 times on the internet.
Do native speakers concur?
Is there any research whether speakers do prefer utterances like my example in practice due to this property?
The second sentence, in a paragraph of its own, would explain what just happened.
I doubt this would ever get past the serious folks at the 'pedia.
But if it did... That would be the difference between awesome and mundane.
* Intuinzinnen, From the Dutch proverbs "ergens intuinen" of "om de tuin geleid worden". Literally: To "be gardened into something", or "to be led around the garden." Both meaning the same as "lead someone down the garden path"
Seams the proverb is nearly similar in both languages. Which makes me wonder whether they originated from the same word. After all, Dutch and English (And German, Danish and Swedish) have the same common ancestor.
Or whether they describe the same, in the past generally known effect of garden paths leading to unexpected dead ends.
Garden is from French (jardin)
Back to the proverb: the dutch one seems to be about "keeping someone from that what is important/the truth" by not letting them in.
Worth reading just for that little bit of precision.
As a native British English speaker I didn't actually have any trouble parsing any of the sentences save for the "The horse raced past the barn fell" because it was written without the customary punctuational scaffolding.
'The old man the boat' seemed fine to me too, not sure why.
I'd be interested to hear if other British English folks had much trouble with these sentences. Perhaps it's a by product of being exposed to too many 'dad jokes' (Fruit flies like a banana) but perhaps it's a more general condition of British English humour that made me feel familiar with this type of sentence structure.
The crooked defect home.
The hot lead the cold.
The quick pace themselves.
The wet tear off their wet clothes.
In my view it's as valid as something like:
which would never be written Just because it's not easy to parse doesn't mean there's a hard-and-fast rule about adding punctuation.But that changes the meaning. Consider a situation where you have two horses. One of them has been raced past the barn; the other never has. This matters because inside the barn there is an alien artefact emitting radiation that weakens the muscles. But that was yesterday. Today you have sent both horses out for another canter -- and one of them has suffered a fall. Tell me, Igor, which one was it? Did the radiation from the alien artefact cause the trouble? "The horse raced past the barn fell."
But the version with the commas is only applicable when (1) you already know which horse is being referred to and (2) the fall happens in racing past the barn or at least as an immediate consequence, it seems to me.
When spoken aloud, this is easier to understand. A fluent English speaker will be able to put the emphasis in the proper places.
> > The horse raced past the barn fell
> should never be written like that.
Surely it can, and must, be so written if the thing past which the horse raced was, as Wikipedia mentions, "the fell by or at the barn"?
There are two possible approaches to your sentence and neither renders it grammatically correct. A prescriptivist would dismiss it as not being allowed by any rules while a descriptivist would point out that it defies both common usage and intelligibility.
And if they allow one sentence to be understood by members of the intended audience that knows the common rules and context and usage well, then that's as valid as it gets. Even if only very few can understand it, the fact that it is possible is enough.
A bit like HTML in browsers - there's the written rules and there's what browsers do anyway, and what's valid in real life is whatever gets the point across.
A prescriptivist would say it follows allowed grammar rules but is still unintelligible.
A descriptivist would say it follows common usage patterns but takes it to such an extreme as to be unintelligible.
You see this pattern more often with proper names:
- That's the house Jack built.
- That's the woman the house Jack built fell on.
- That's the lawyer the woman the house Jack built fell on hired.
- That's the briefcase the lawyer the woman the house Jack built fell on hired carried.
At what point does it become "incorrect"? When it becomes unintelligible to most native speakers?
It's also worth noting these sentences seem much stranger in writing than they do when heard. In writing, most sane people will use punctuation in the examples above. But in speaking, our tone of voice conveys enough context to use more streamlined structures.
Beyond 1 level of nesting. There's no rule allowing arbitrary nesting, nor do people commonly nest beyond 1 level.
I'm not sure where you saw hostility in my comment.
Also, which example is 1 level of nesting? I think "That's the woman the house Jack built fell on." is 2 levels nesting, and I frequently hear constructs like that – in speaking. I agree it's rarer in writing though.
For example: What server is that? That's the server the consultant Jack brought in set up.
I'd never write that, because it's confusing. But I will naturally say things like that, without any problem in clarity, because you have more granular control over grouping and pausing, etc. If I said a sentence like that, you might hear it more as "That's the server the-consultant-Jack-brought-in set up."
Anyway, sorry if I misread your tone. It just came across very much as "I know what's right, and you're wrong." That might have been me projecting though. :)
In fact, the "rule" that matters here is general sentence structure. It's fine to embed a single secondary clause inside a primary clause:
The structure of the inner clause has no further restrictions on it than the structure of the outer clause. Thus, the entire above sentence is perfectly valid as an inner clause to a new outer clause: There's nothing in any grammar book that I'm aware of explicitly prohibiting infinite nesting of this sort; it's just silly and quickly becomes unintelligible. Though I definitely take Tenhundfeld's point that this sort of structure is a lot more common in spoken language, and in fact it's a lot more easily comprehensible with the aid of vocal cues and tones.There are examples of 2 levels of center-embedding which are clearly grammatical and not hard to understand:
> Anyone [who saw the woman [who committed the crime] at any point] should be questioned.
Others are very hard to understand:
> Anyone [who the man [who the woman shot] killed] should be questioned.
There are many factors that make a sentence hard to understand, not just degree of embedding. Some degree 2 sentences can be easy, and some degree 1 sentences can be hard (e.g. "the horse [raced past the barn] fell", which has only 1 level of embedding).
So if you want to describe English with the rule "no embedding beyond 1 level" then you're going to miss a lot of valid sentences while also failing to rule out lots of invalid ones.
Contrast this with a valid descriptive rule of English, such as "determiners such as 'the' always come before the nouns they modify". I can say "the man died", but "man the died" is never comprehensible under any circumstances and cannot be made better.
No one would say that a sentence with 10 levels of embedding is perfectly fine English. But descriptively, you have the problem that there is no non-arbitrary upper bound on embedding degree: it's not clear when one more level of embedding takes you from grammatical to ungrammatical, and furthermore it depends on the contents of the embedded clauses.
There is also some work I'm aware of, currently in prep for publication, showing that the extent to which people can understand multiply-embedded sentences strongly correlates with IQ (measured by Raven's matrices).
All this suggests that the simplest descriptive rule is to say that English allows center-embedding recursively, but that there are human processing limitations on sentences that create very deep stacks. The "human processing limitations" part is basically the whole field of psycholinguistics: many details have been worked out, but many details are still sketchy.
[1] Karlsson (2007): http://journals.cambridge.org/action/displayAbstract?fromPag...
That being said, I still think the rule of 1 level still makes sense (not that all 1 level embeds are valid or easy, but that all embeds beyond 1 level are invalid).
> Anyone [who saw [the woman who committed the crime] at any point] should be questioned.
That sentence has two complementisers, which the OP's sentence specifically did not. Introducing complementisers completely changes the rules and I think makes embedding much more possible.
Even with the brackets, I don't understand this one. Anyone killed by the man should be questioned?
(Also, shouldn't they both be 'whom'?)
How so? Surely there is room for debate within descriptivism as to what constitutes evidence of something being used?
And no two prescriptivists can agree on which rulebook to use!
Here's a helpful presentation summarizing some of this research: https://depts.washington.edu/lingconf/slides/Bader&Haeussler...
The sentence the comment the user replied to included parsed with difficulty.
"The cat meowed"
to
"The cat the mouse feared meowed"
If your claim is that nesting to arbitrary depths is not allowed, what is the maximum depth that is "legal"?
If it's not parseable, then surely you can't.
Here's a toy Python parser I wrote many years ago actually listing out all valid parses of this sentence: https://github.com/taliesinb/chartreuse/blob/master/README.m...
Or even simpler:
Come to think of it, this reminds me somewhat of tail-recursion optimization.> What did you take the car driving the man who brought the book that I didn't want to be read to out of up away in for?
Almost-untangled form:
> For what reason did you take in the car driven away by the man who brought up the book that I did not want anyone to read words out of [the book] to me?
Although if you are being very specific, I think some syntacticians might treat the "out" in "out of" and the "up" in "bring up" as a different word classes than normal prepositions (the "out" is modifying another preposition's direction, and the "up" is a particle in a phrasal verb [1]). And I think that's one of the reasons the original form is so compelling is that you have some variance in form giving you clues -- the directional modifier, the question-inversion/wh-fronting, the salience of "bring up" -- that make it tantalizingly close to natural. Whereas mine just becomes a churn of words, at least in my reading.
[1] https://en.wikipedia.org/wiki/Phrasal_verb#Examples_of_Phras... (see the notes on distinguishing between particle & prepositional phrasals)