Parsing with CCGs - lambda partHelp with syntax treesWhy is dependency parsing so much faster than constituency parsing?Is lambda calculus only applicable if syntax trees are binary branching?Representing prepositions in lambda calculus/logic notationCan syntax be part of semantics?Representing knowledge extracted from output of dependency parsingSemantic parsing vs Propositional RepresentationParsing a sentence with the noun as the PredicatorHow does one deal with sentences starting with a connective?Converting types into lambda notation and set notation
Was Unix ever a single-user OS?
Stark VS Thanos
Is it appropriate to refer to God as "It"?
What does air vanishing on contact sound like?
Is this homebrew race based on the Draco Volans lizard species balanced?
Any examples of headwear for races with animal ears?
What happens if I start too many background jobs?
Airbnb - host wants to reduce rooms, can we get refund?
Does it look bad as a candidate if I apply to two post-doctoral positions at the same national research laboratory?
How to reply this mail from potential PhD professor?
Survey Confirmation - Emphasize the question or the answer?
Parsing with CCGs - lambda part
Is it the same airport YUL and YMQ in Canada?
Why is Thanos so tough at the beginning of "Avengers: Endgame"?
Can a cyclic Amine form an Amide?
I lost my Irish passport. Can I travel to Thailand and back from the UK using my US passport?
What is the word which sounds like "shtrass"?
LT Spice Voltage Output
Surprising behavior of Part[ ]
How to get SEEK accessing converted ID via view
How did Arya manage to disguise herself?
Is balancing necessary on a full-wheel change?
Why was the pattern string not followed in this code?
What is the most remote airport from the center of the city it supposedly serves?
Parsing with CCGs - lambda part
Help with syntax treesWhy is dependency parsing so much faster than constituency parsing?Is lambda calculus only applicable if syntax trees are binary branching?Representing prepositions in lambda calculus/logic notationCan syntax be part of semantics?Representing knowledge extracted from output of dependency parsingSemantic parsing vs Propositional RepresentationParsing a sentence with the noun as the PredicatorHow does one deal with sentences starting with a connective?Converting types into lambda notation and set notation
I am following this video tutorial, starting 6th minute
I would like to parse the following sentence
square blue or round yellow pillow.
For now I am interested in only how square and blue are combined.
In particular with start with the following representation
square -> ADJ: lambda x. square(x)
blue -> ADJ: lambda x. blue(x)
Next step is we raise types:
square -> N/N: lambda f. lambda x. f(x) / square (x)
blue -> N/N: lambda f. lambda x. f(x) / blue (x)
Now we create representation for square blue. I indicate substitution by brackets
lambda x. [ lambda f. lambda x. f(x) / blue (x) ] (x) / square (x)
Next I simply substitute z for x everywhere outside of square brackets, so that we do not confuse different xs.
lambda z. [ lambda f. lambda x. f(x) / blue (x) ] (z) / square (z)
Next I push z into square brackets
lambda z. lambda x. z(x) / blue (x) / square (z)
This is different from what stated in the lecture:
lambda z. lambda x. z(x) / square (x) / blue (x)
Where did I make a mistake?
semantics syntax-trees lambda-calculus ccg
add a comment |
I am following this video tutorial, starting 6th minute
I would like to parse the following sentence
square blue or round yellow pillow.
For now I am interested in only how square and blue are combined.
In particular with start with the following representation
square -> ADJ: lambda x. square(x)
blue -> ADJ: lambda x. blue(x)
Next step is we raise types:
square -> N/N: lambda f. lambda x. f(x) / square (x)
blue -> N/N: lambda f. lambda x. f(x) / blue (x)
Now we create representation for square blue. I indicate substitution by brackets
lambda x. [ lambda f. lambda x. f(x) / blue (x) ] (x) / square (x)
Next I simply substitute z for x everywhere outside of square brackets, so that we do not confuse different xs.
lambda z. [ lambda f. lambda x. f(x) / blue (x) ] (z) / square (z)
Next I push z into square brackets
lambda z. lambda x. z(x) / blue (x) / square (z)
This is different from what stated in the lecture:
lambda z. lambda x. z(x) / square (x) / blue (x)
Where did I make a mistake?
semantics syntax-trees lambda-calculus ccg
add a comment |
I am following this video tutorial, starting 6th minute
I would like to parse the following sentence
square blue or round yellow pillow.
For now I am interested in only how square and blue are combined.
In particular with start with the following representation
square -> ADJ: lambda x. square(x)
blue -> ADJ: lambda x. blue(x)
Next step is we raise types:
square -> N/N: lambda f. lambda x. f(x) / square (x)
blue -> N/N: lambda f. lambda x. f(x) / blue (x)
Now we create representation for square blue. I indicate substitution by brackets
lambda x. [ lambda f. lambda x. f(x) / blue (x) ] (x) / square (x)
Next I simply substitute z for x everywhere outside of square brackets, so that we do not confuse different xs.
lambda z. [ lambda f. lambda x. f(x) / blue (x) ] (z) / square (z)
Next I push z into square brackets
lambda z. lambda x. z(x) / blue (x) / square (z)
This is different from what stated in the lecture:
lambda z. lambda x. z(x) / square (x) / blue (x)
Where did I make a mistake?
semantics syntax-trees lambda-calculus ccg
I am following this video tutorial, starting 6th minute
I would like to parse the following sentence
square blue or round yellow pillow.
For now I am interested in only how square and blue are combined.
In particular with start with the following representation
square -> ADJ: lambda x. square(x)
blue -> ADJ: lambda x. blue(x)
Next step is we raise types:
square -> N/N: lambda f. lambda x. f(x) / square (x)
blue -> N/N: lambda f. lambda x. f(x) / blue (x)
Now we create representation for square blue. I indicate substitution by brackets
lambda x. [ lambda f. lambda x. f(x) / blue (x) ] (x) / square (x)
Next I simply substitute z for x everywhere outside of square brackets, so that we do not confuse different xs.
lambda z. [ lambda f. lambda x. f(x) / blue (x) ] (z) / square (z)
Next I push z into square brackets
lambda z. lambda x. z(x) / blue (x) / square (z)
This is different from what stated in the lecture:
lambda z. lambda x. z(x) / square (x) / blue (x)
Where did I make a mistake?
semantics syntax-trees lambda-calculus ccg
semantics syntax-trees lambda-calculus ccg
edited 3 hours ago
lemontree♦
4,85731030
4,85731030
asked 5 hours ago
user1700890user1700890
1678
1678
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
I'll leave the lambdas to you, but you might like to know the syntactic structure. It is a RNR (right node-raising) construction, with "pillow" the raised node. The intonation I think makes that obvious. Thus:
[square blue GAP or round yellow GAP] (pillow), where the noun "pillow" fills the GAP.
"square", "blue", "round", "yellow" are adjectives which modify nouns or modified nouns.
add a comment |
If I am not mistaken, your computation is correct, and the video simply shows the wrong result.
The order square(x) ^ blue(x) comes from the fact that squared is applied to blue where blue will be substituted for f in the term f(x), which comes before square(x) in the conjunction.
To change the order in which the terms will appear in the conjunction without changing the order in which the terms are applied to each other (of course you could also do the backward composition blue square so square goes in for f in blue, but that wouldn't be in line with the intended forward composition), one could simply change the order of the expressions in the definition of square to
square -> N/N: lambda f. lambda x. square (x) ^ f(x)
which changes the rule for type raising to
lambda x. g(x) -> lambda f. lambda x. g(x) ^ f(x)
Edit:
I might at a total loss, but it actually looks like the computation in the video doesn't work out at all:
(λf.[λx.[f(x) ^ square(x)]])(λf.[λy.[f(y) ^ blue(y)]]) reduces to(λx.[(λf.[λy.[f(y) ^ blue(y)]])(x) ^ square(x)]) which reduces to(λx.[(λy.[x(y) ^ blue(y)]) ^ square(x)]),
not (λf.[λx.[f(x) ^ square (x) ^ blue (x)]]).
I have no idea how they arrive at this result, it must be a mistake.
Thank you for reply. Also I believe type raising is not very accurate. It should go from ADJ to NP/N. Even in simplest caseblue pillowwe applyblueto nounpillowand end up with noun phrase.
– user1700890
3 hours ago
1
@user1700890 No, I the type N/N is okay.blue pillowshould only be an N because the corredponding NP would bethe blue pillow. Otherweise, you wouldn't be able to combine the result with more adjectives (in theory, you can append an unlimited number of adjectives) or determiners likethe, both of which require an input of type N. In general, it is the inherent property of modifiers (which adjectives belong to) that they don't change the syntactic status of the element they combine with, and are therefore always of type X/X: A noun goes in, a noun comes out.
– lemontree♦
3 hours ago
But see the edit to my post on the lambda computation.
– lemontree♦
3 hours ago
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "312"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2flinguistics.stackexchange.com%2fquestions%2f31298%2fparsing-with-ccgs-lambda-part%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
I'll leave the lambdas to you, but you might like to know the syntactic structure. It is a RNR (right node-raising) construction, with "pillow" the raised node. The intonation I think makes that obvious. Thus:
[square blue GAP or round yellow GAP] (pillow), where the noun "pillow" fills the GAP.
"square", "blue", "round", "yellow" are adjectives which modify nouns or modified nouns.
add a comment |
I'll leave the lambdas to you, but you might like to know the syntactic structure. It is a RNR (right node-raising) construction, with "pillow" the raised node. The intonation I think makes that obvious. Thus:
[square blue GAP or round yellow GAP] (pillow), where the noun "pillow" fills the GAP.
"square", "blue", "round", "yellow" are adjectives which modify nouns or modified nouns.
add a comment |
I'll leave the lambdas to you, but you might like to know the syntactic structure. It is a RNR (right node-raising) construction, with "pillow" the raised node. The intonation I think makes that obvious. Thus:
[square blue GAP or round yellow GAP] (pillow), where the noun "pillow" fills the GAP.
"square", "blue", "round", "yellow" are adjectives which modify nouns or modified nouns.
I'll leave the lambdas to you, but you might like to know the syntactic structure. It is a RNR (right node-raising) construction, with "pillow" the raised node. The intonation I think makes that obvious. Thus:
[square blue GAP or round yellow GAP] (pillow), where the noun "pillow" fills the GAP.
"square", "blue", "round", "yellow" are adjectives which modify nouns or modified nouns.
answered 2 hours ago
Greg LeeGreg Lee
9,52511023
9,52511023
add a comment |
add a comment |
If I am not mistaken, your computation is correct, and the video simply shows the wrong result.
The order square(x) ^ blue(x) comes from the fact that squared is applied to blue where blue will be substituted for f in the term f(x), which comes before square(x) in the conjunction.
To change the order in which the terms will appear in the conjunction without changing the order in which the terms are applied to each other (of course you could also do the backward composition blue square so square goes in for f in blue, but that wouldn't be in line with the intended forward composition), one could simply change the order of the expressions in the definition of square to
square -> N/N: lambda f. lambda x. square (x) ^ f(x)
which changes the rule for type raising to
lambda x. g(x) -> lambda f. lambda x. g(x) ^ f(x)
Edit:
I might at a total loss, but it actually looks like the computation in the video doesn't work out at all:
(λf.[λx.[f(x) ^ square(x)]])(λf.[λy.[f(y) ^ blue(y)]]) reduces to(λx.[(λf.[λy.[f(y) ^ blue(y)]])(x) ^ square(x)]) which reduces to(λx.[(λy.[x(y) ^ blue(y)]) ^ square(x)]),
not (λf.[λx.[f(x) ^ square (x) ^ blue (x)]]).
I have no idea how they arrive at this result, it must be a mistake.
Thank you for reply. Also I believe type raising is not very accurate. It should go from ADJ to NP/N. Even in simplest caseblue pillowwe applyblueto nounpillowand end up with noun phrase.
– user1700890
3 hours ago
1
@user1700890 No, I the type N/N is okay.blue pillowshould only be an N because the corredponding NP would bethe blue pillow. Otherweise, you wouldn't be able to combine the result with more adjectives (in theory, you can append an unlimited number of adjectives) or determiners likethe, both of which require an input of type N. In general, it is the inherent property of modifiers (which adjectives belong to) that they don't change the syntactic status of the element they combine with, and are therefore always of type X/X: A noun goes in, a noun comes out.
– lemontree♦
3 hours ago
But see the edit to my post on the lambda computation.
– lemontree♦
3 hours ago
add a comment |
If I am not mistaken, your computation is correct, and the video simply shows the wrong result.
The order square(x) ^ blue(x) comes from the fact that squared is applied to blue where blue will be substituted for f in the term f(x), which comes before square(x) in the conjunction.
To change the order in which the terms will appear in the conjunction without changing the order in which the terms are applied to each other (of course you could also do the backward composition blue square so square goes in for f in blue, but that wouldn't be in line with the intended forward composition), one could simply change the order of the expressions in the definition of square to
square -> N/N: lambda f. lambda x. square (x) ^ f(x)
which changes the rule for type raising to
lambda x. g(x) -> lambda f. lambda x. g(x) ^ f(x)
Edit:
I might at a total loss, but it actually looks like the computation in the video doesn't work out at all:
(λf.[λx.[f(x) ^ square(x)]])(λf.[λy.[f(y) ^ blue(y)]]) reduces to(λx.[(λf.[λy.[f(y) ^ blue(y)]])(x) ^ square(x)]) which reduces to(λx.[(λy.[x(y) ^ blue(y)]) ^ square(x)]),
not (λf.[λx.[f(x) ^ square (x) ^ blue (x)]]).
I have no idea how they arrive at this result, it must be a mistake.
Thank you for reply. Also I believe type raising is not very accurate. It should go from ADJ to NP/N. Even in simplest caseblue pillowwe applyblueto nounpillowand end up with noun phrase.
– user1700890
3 hours ago
1
@user1700890 No, I the type N/N is okay.blue pillowshould only be an N because the corredponding NP would bethe blue pillow. Otherweise, you wouldn't be able to combine the result with more adjectives (in theory, you can append an unlimited number of adjectives) or determiners likethe, both of which require an input of type N. In general, it is the inherent property of modifiers (which adjectives belong to) that they don't change the syntactic status of the element they combine with, and are therefore always of type X/X: A noun goes in, a noun comes out.
– lemontree♦
3 hours ago
But see the edit to my post on the lambda computation.
– lemontree♦
3 hours ago
add a comment |
If I am not mistaken, your computation is correct, and the video simply shows the wrong result.
The order square(x) ^ blue(x) comes from the fact that squared is applied to blue where blue will be substituted for f in the term f(x), which comes before square(x) in the conjunction.
To change the order in which the terms will appear in the conjunction without changing the order in which the terms are applied to each other (of course you could also do the backward composition blue square so square goes in for f in blue, but that wouldn't be in line with the intended forward composition), one could simply change the order of the expressions in the definition of square to
square -> N/N: lambda f. lambda x. square (x) ^ f(x)
which changes the rule for type raising to
lambda x. g(x) -> lambda f. lambda x. g(x) ^ f(x)
Edit:
I might at a total loss, but it actually looks like the computation in the video doesn't work out at all:
(λf.[λx.[f(x) ^ square(x)]])(λf.[λy.[f(y) ^ blue(y)]]) reduces to(λx.[(λf.[λy.[f(y) ^ blue(y)]])(x) ^ square(x)]) which reduces to(λx.[(λy.[x(y) ^ blue(y)]) ^ square(x)]),
not (λf.[λx.[f(x) ^ square (x) ^ blue (x)]]).
I have no idea how they arrive at this result, it must be a mistake.
If I am not mistaken, your computation is correct, and the video simply shows the wrong result.
The order square(x) ^ blue(x) comes from the fact that squared is applied to blue where blue will be substituted for f in the term f(x), which comes before square(x) in the conjunction.
To change the order in which the terms will appear in the conjunction without changing the order in which the terms are applied to each other (of course you could also do the backward composition blue square so square goes in for f in blue, but that wouldn't be in line with the intended forward composition), one could simply change the order of the expressions in the definition of square to
square -> N/N: lambda f. lambda x. square (x) ^ f(x)
which changes the rule for type raising to
lambda x. g(x) -> lambda f. lambda x. g(x) ^ f(x)
Edit:
I might at a total loss, but it actually looks like the computation in the video doesn't work out at all:
(λf.[λx.[f(x) ^ square(x)]])(λf.[λy.[f(y) ^ blue(y)]]) reduces to(λx.[(λf.[λy.[f(y) ^ blue(y)]])(x) ^ square(x)]) which reduces to(λx.[(λy.[x(y) ^ blue(y)]) ^ square(x)]),
not (λf.[λx.[f(x) ^ square (x) ^ blue (x)]]).
I have no idea how they arrive at this result, it must be a mistake.
edited 2 hours ago
answered 3 hours ago
lemontree♦lemontree
4,85731030
4,85731030
Thank you for reply. Also I believe type raising is not very accurate. It should go from ADJ to NP/N. Even in simplest caseblue pillowwe applyblueto nounpillowand end up with noun phrase.
– user1700890
3 hours ago
1
@user1700890 No, I the type N/N is okay.blue pillowshould only be an N because the corredponding NP would bethe blue pillow. Otherweise, you wouldn't be able to combine the result with more adjectives (in theory, you can append an unlimited number of adjectives) or determiners likethe, both of which require an input of type N. In general, it is the inherent property of modifiers (which adjectives belong to) that they don't change the syntactic status of the element they combine with, and are therefore always of type X/X: A noun goes in, a noun comes out.
– lemontree♦
3 hours ago
But see the edit to my post on the lambda computation.
– lemontree♦
3 hours ago
add a comment |
Thank you for reply. Also I believe type raising is not very accurate. It should go from ADJ to NP/N. Even in simplest caseblue pillowwe applyblueto nounpillowand end up with noun phrase.
– user1700890
3 hours ago
1
@user1700890 No, I the type N/N is okay.blue pillowshould only be an N because the corredponding NP would bethe blue pillow. Otherweise, you wouldn't be able to combine the result with more adjectives (in theory, you can append an unlimited number of adjectives) or determiners likethe, both of which require an input of type N. In general, it is the inherent property of modifiers (which adjectives belong to) that they don't change the syntactic status of the element they combine with, and are therefore always of type X/X: A noun goes in, a noun comes out.
– lemontree♦
3 hours ago
But see the edit to my post on the lambda computation.
– lemontree♦
3 hours ago
Thank you for reply. Also I believe type raising is not very accurate. It should go from ADJ to NP/N. Even in simplest case
blue pillow we apply blue to noun pillow and end up with noun phrase.– user1700890
3 hours ago
Thank you for reply. Also I believe type raising is not very accurate. It should go from ADJ to NP/N. Even in simplest case
blue pillow we apply blue to noun pillow and end up with noun phrase.– user1700890
3 hours ago
1
1
@user1700890 No, I the type N/N is okay.
blue pillow should only be an N because the corredponding NP would be the blue pillow. Otherweise, you wouldn't be able to combine the result with more adjectives (in theory, you can append an unlimited number of adjectives) or determiners like the, both of which require an input of type N. In general, it is the inherent property of modifiers (which adjectives belong to) that they don't change the syntactic status of the element they combine with, and are therefore always of type X/X: A noun goes in, a noun comes out.– lemontree♦
3 hours ago
@user1700890 No, I the type N/N is okay.
blue pillow should only be an N because the corredponding NP would be the blue pillow. Otherweise, you wouldn't be able to combine the result with more adjectives (in theory, you can append an unlimited number of adjectives) or determiners like the, both of which require an input of type N. In general, it is the inherent property of modifiers (which adjectives belong to) that they don't change the syntactic status of the element they combine with, and are therefore always of type X/X: A noun goes in, a noun comes out.– lemontree♦
3 hours ago
But see the edit to my post on the lambda computation.
– lemontree♦
3 hours ago
But see the edit to my post on the lambda computation.
– lemontree♦
3 hours ago
add a comment |
Thanks for contributing an answer to Linguistics Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2flinguistics.stackexchange.com%2fquestions%2f31298%2fparsing-with-ccgs-lambda-part%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown