|Time||TuTh 4:15pm - 5:30pm|
|Location||200-205 (click for map)|
|All of us||(This address should be used for all course correspondence, including assignments.)|
Catalog description Machine understanding of human language. Computational semantics (determination of sense, event structure, thematic role, time, aspect, synonymy/meronymy, causation, compositional semantics, treatment of scopal operators), and computational pragmatics and discourse (coherence relations, anaphora resolution, information packaging, generation). Theoretical issues, online resources, and relevance to applications including question answering, summarization, and textual inference. Prerequisites: one of LING180, CS224N, CS224S; and knowledge of logic (LING130A or B, CS157, or PHIL159).
Attendance will be taken daily, with one point assigned for each class attended. Class will begin on time and end on time; we are obliged to finish on time, and you are obliged to arrive on time.
We would like everyone to ask questions, offer ideas, etc., in class. Questions and ideas sent via email to also count as participation, though we would prefer it if everyone got involved during our class meetings.
There are 13 short homeworks. The homeworks will depend on materials from the readings, so you should do the readings before starting the homeworks. With the reading done, each homework should take you 15-20 minutes (longer if you decide to pursue the issues in greater depth, perhaps as a lead-in to a project).
Our goals for the homeworks: (i) to raise important questions, (ii) to foster common ground for the in-class discussions, and (iii) to help you master central NLU concepts.
The final project is the main assignment of the second half of the course. Final projects can be done in groups of 1-3 people. They are required to be related in a substantive way to at least one of the central topics of the course. The main components are as follows:
Your grade is determined based on:
Each student will have a total of 4 free late (calendar) days applicable to any assignment (including the lit review and project milestone) except the final project paper. These can be used at any time, no questions asked. Each 24 hours or part thereof that a homework is late uses up one full late day. Once these late days are exhausted, any homework turned in late will be penalized 20% per late day. Late days are not applicable to final projects. If a group's assignment is late n days, then each group member is charged n late days.
On the one hand, we want to encourage you to pursue unified interdisciplinary projects that weave together themes from multiple classes. On the other hand, we need to ensure that final projects for this course are original and involve a substantial new effort.
To try to meet both these demands, we are adopting the following policy on joint submission: if your final project for this course is related to your final project for another course, you are required to submit both projects to us by our final project due date. If we decide that the projects are too similar, your project will receive a failing grade. To avoid this extreme outcome, we strongly encourage you to stay in close communication with us if your project is related to another you are submitting for credit, so that there are no unhappy surprises at the end of the term. Since there is no single objective standard for what counts as "different enough", it is better to play it safe by talking with us.
Fundamentally, we are saying that combining projects is not a shortcut. In a sense, we are in the same position as professional conferences and journals, which also need to watch out for multiple submissions. You might have a look at the current ACL/NAACL policy, which strives to ensure that any two papers submitted to those conferences are make substantially different contributions — our goal here as well.
Please familiarize yourself with Stanford's honor code
We will adhere to it and follow through on its penalty guidelines.
Students who may need an academic accommodation based on the impact of a disability must initiate the request with the Student Disability Resource Center (SDRC) located within the Office of Accessible Education (OAE). SDRC staff will evaluate the request with required documentation, recommend reasonable accommodations, and prepare an Accommodation Letter for faculty dated in the current quarter in which the request is being made. Students should contact the SDRC as soon as possible since timely notice is needed to coordinate accommodations. The OAE is located at 563 Salvatierra Walk (phone: 723-1066).
|Week||Date||HW due||Who||Topic and Readings|
|1||Jan 8||Chris & Bill||
|PART I: Lexical semantics|
|1||Jan 10||HW 1 due||Bill||
|2||Jan 15||HW 2 due||Bill||
|2||Jan 17||HW 3 due||Chris||
|3||Jan 22||HW 4 due||Richard Socher||
|3||Jan 24||HW 5 due||Natalia||
|4||Jan 29||HW 6 due||Bill||
Relation extraction I
|4||Jan 31||HW 7 due||Bill||
Relation extraction II
|5||Feb 5||HW 8 due||Chris & Bill||
|PART II: Semantic composition|
|5||Feb 7||HW 9 due||Bill|
|6||Feb 12||HW 10 due||Percy Liang||
|6||Feb 14||Lit review due||Bill||
Natural logic and textual inference
|7||Feb 19||HW 11 due||Jakob Uszkoreit||
Interpreting queries with structure at Google
|7||Feb 21||HW 12 due||Bill & Chris||
Workshop 2: Evaluating your model
|PART III: Discourse and context|
|8||Feb 26||HW 13 due||Chris||
slides (same as Feb 26)
|9||Mar 5||Project milestone due||Adam Vogel||
Workshop 3: Writing up and presenting your work
|PART IV: Project presentations|
|March 20, 3:15 pm||Final project due||