START Conference Manager    

TextGraphs-6: Graph-based Methods for Natural Language Processing

Textgraphs 2011

Submission Page

To revise a previous submission, please type in its passcode below, and press the ENTER button.

   

If you lost the passcode for your submission, please click HERE.

To make a new submission, please fill in the form below, and then press the submit button at the bottom.

Important: Textgraphs 2011 is running a double-blind review process. In preparing your manuscript, do not include any information which could reveal your identity, or that of your co-authors. The title section of your manuscript should not contain any author names, email addresses, or affiliation status. If you do include any author names on the title page, your submission will be automatically rejected. In the body of your submission, you should eliminate all direct references to your own previous work. That is, avoid phrases such as "this contribution generalizes our results for XYZ". Also, please do not disproportionately cite your own previous work. In other words, make your submission as anonymous as possible. We need your cooperation in our effort to maintain a fair, double-blind reviewing process - and to consider all submissions equally.

Title of Submission:  

List of Authors:

Please enter the complete list of authors for your submission, in the order in which they will appear on the abstract. You can add as many author slots as you want, to accommodate the total number of authors for your submission.

First name(s) Last name Email Affiliation
#1
#2
#3
#4
#5
#6
#7
#8
#9
#10
#11
#12
#13
#14
#15
#16
#17
#18
#19
#20

More authors      Fewer authors

Contact Information:

Title 
First name*
Last name*
  Affiliation/organization*
       Affiliation Dept/Lab 
Phone*
Fax 
Email*
Country*
Address 
Address 
Address 
City/Town*
Zip/Postal Code*

Conflicts of Interest:

Please identify all potential committee members and reviewers who should not review this submission, due to having a conflict of interest with you or any of your co-authors. It is crucial that you fill in this section as carefully as possible, and that you do so in consultation with all of your co-authors. For more information on how to determine your conflicts of interest, please see the author guidelines posted at the website for Textgraphs.

Reviewer checklist: Please carefully examine the list of names below, and check-off any of the people who should not review this submission, due to a conflict of interest with one of the authors. (This also includes the names of any co-authors, if they appear below.)

 Eneko Agirre     Roberto Basili     Ulf Brefeld     Razvan Bunescu   
 Nicola Cancedda     Giuseppe Carenini     Yejin Choi     William Cohen   
 Andras Csomai     Mona Diab     Gaël Dias     Thomas Gaertner   
 Michael Gamon     Andrew Goldberg     Zhou GuoDong     Richard Johansson   
 Lillian Lee     Dekang Lin     Chris Manning     Irina Matveeva   
 Ryan McDonald     Rada Mihalcea     Alessandro Moschitti     Animesh Mukherjee   
 Lluís Màrquez     Bo Pang     Patrick Pantel     Daniele Pighin   
 Uwe Quasthoff     Dragomir Radev     Brian Roark     Dan Roth   
 Swapna Somasundaran     Aitor Soroa     Veselin Stoyanov     Theresa Wilson   
 Fabio Zanzotto     Min Zhang   

Additional conflicts: The committee may call on external reviewers to help evaluate your submission. These reviewer names may not appear in the list above. Therefore, we also request that you identify any other conflicts of interest you can think of. Specifically, you should list anybody you know of who works in an area related to Textgraphs, and who has a conflict of interest with either you or one of your co-authors. (You do not need to include your own author names in this list.)

First name Last name Email Affiliation
#1
#2
#3
#4
#5
#6
#7
#8
#9
#10
#11
#12
#13
#14
#15
#16
#17
#18
#19
#20
#21
#22
#23
#24
#25
#26
#27
#28
#29
#30

More Conflicts      Fewer Conflicts

Summary:

Type (or cut-and-paste) a short summary for your submission. You must enter plain text only.

 

Submit Paper:

Your submission must be in one of the following document formats:

  • Adobe PDF (pdf)
  • Postscript (ps)
  • Microsoft Word (doc)
  • Rich Text (rtf)

The file's name should have the proper MIME extent associated with its document type. For example, a pdf file could have a name such as "mypaper.pdf".

Find the file containing your submission: 

Resource Map In collaboration with LREC, the purpose of this section is to monitor the use and creation of language resources (datasets, tools, etc.). We are therefore collecting information on both existing resources that you used for your research, and on resources that you have newly created. To make this process as easy as possible for you, we have intentionally oversimplified the resource entry form, and have constrained the choices of possible values to select.

For each existing resource that you used, please just briefly fill in the name, url, and resource type. For each new resource that you are creating, please include all the other information on size, license type, and so on.

For more details, please read the Help Page on the LREC 2010 web site. If you do not have any resources to describe (e.g. if your submission is on general issues), please check the following box and complete your submission.

No resources to report with this submission.

If you have more than one resource, please fill in as many forms as the resources you must describe.

#1
Resource Type:
Resource Name:
Size: Enter package size - a number and a relevant unit of measurement, e.g., 48Mbyte, 5500 lexemes, 2.1Gbyte.
Resource Production Status:
Language(s):
Modality:
Use of the Resource:
Resource Availability:
License: Licence type, e.g., ELRA, LDC, Gnu, CreativeCommons, OpenSource, etc.
Resource URL (if available):
Documentation: Is there documentation? In which language? Is the documentation publicly available?
Resource Description:
#2
Resource Type:
Resource Name:
Size: Enter package size - a number and a relevant unit of measurement, e.g., 48Mbyte, 5500 lexemes, 2.1Gbyte.
Resource Production Status:
Language(s):
Modality:
Use of the Resource:
Resource Availability:
License: Licence type, e.g., ELRA, LDC, Gnu, CreativeCommons, OpenSource, etc.
Resource URL (if available):
Documentation: Is there documentation? In which language? Is the documentation publicly available?
Resource Description:
#3
Resource Type:
Resource Name:
Size: Enter package size - a number and a relevant unit of measurement, e.g., 48Mbyte, 5500 lexemes, 2.1Gbyte.
Resource Production Status:
Language(s):
Modality:
Use of the Resource:
Resource Availability:
License: Licence type, e.g., ELRA, LDC, Gnu, CreativeCommons, OpenSource, etc.
Resource URL (if available):
Documentation: Is there documentation? In which language? Is the documentation publicly available?
Resource Description:
#4
Resource Type:
Resource Name:
Size: Enter package size - a number and a relevant unit of measurement, e.g., 48Mbyte, 5500 lexemes, 2.1Gbyte.
Resource Production Status:
Language(s):
Modality:
Use of the Resource:
Resource Availability:
License: Licence type, e.g., ELRA, LDC, Gnu, CreativeCommons, OpenSource, etc.
Resource URL (if available):
Documentation: Is there documentation? In which language? Is the documentation publicly available?
Resource Description:
#5
Resource Type:
Resource Name:
Size: Enter package size - a number and a relevant unit of measurement, e.g., 48Mbyte, 5500 lexemes, 2.1Gbyte.
Resource Production Status:
Language(s):
Modality:
Use of the Resource:
Resource Availability:
License: Licence type, e.g., ELRA, LDC, Gnu, CreativeCommons, OpenSource, etc.
Resource URL (if available):
Documentation: Is there documentation? In which language? Is the documentation publicly available?
Resource Description:
#6
Resource Type:
Resource Name:
Size: Enter package size - a number and a relevant unit of measurement, e.g., 48Mbyte, 5500 lexemes, 2.1Gbyte.
Resource Production Status:
Language(s):
Modality:
Use of the Resource:
Resource Availability:
License: Licence type, e.g., ELRA, LDC, Gnu, CreativeCommons, OpenSource, etc.
Resource URL (if available):
Documentation: Is there documentation? In which language? Is the documentation publicly available?
Resource Description:
#7
Resource Type:
Resource Name:
Size: Enter package size - a number and a relevant unit of measurement, e.g., 48Mbyte, 5500 lexemes, 2.1Gbyte.
Resource Production Status:
Language(s):
Modality:
Use of the Resource:
Resource Availability:
License: Licence type, e.g., ELRA, LDC, Gnu, CreativeCommons, OpenSource, etc.
Resource URL (if available):
Documentation: Is there documentation? In which language? Is the documentation publicly available?
Resource Description:
#8
Resource Type:
Resource Name:
Size: Enter package size - a number and a relevant unit of measurement, e.g., 48Mbyte, 5500 lexemes, 2.1Gbyte.
Resource Production Status:
Language(s):
Modality:
Use of the Resource:
Resource Availability:
License: Licence type, e.g., ELRA, LDC, Gnu, CreativeCommons, OpenSource, etc.
Resource URL (if available):
Documentation: Is there documentation? In which language? Is the documentation publicly available?
Resource Description:
#9
Resource Type:
Resource Name:
Size: Enter package size - a number and a relevant unit of measurement, e.g., 48Mbyte, 5500 lexemes, 2.1Gbyte.
Resource Production Status:
Language(s):
Modality:
Use of the Resource:
Resource Availability:
License: Licence type, e.g., ELRA, LDC, Gnu, CreativeCommons, OpenSource, etc.
Resource URL (if available):
Documentation: Is there documentation? In which language? Is the documentation publicly available?
Resource Description:
#10
Resource Type:
Resource Name:
Size: Enter package size - a number and a relevant unit of measurement, e.g., 48Mbyte, 5500 lexemes, 2.1Gbyte.
Resource Production Status:
Language(s):
Modality:
Use of the Resource:
Resource Availability:
License: Licence type, e.g., ELRA, LDC, Gnu, CreativeCommons, OpenSource, etc.
Resource URL (if available):
Documentation: Is there documentation? In which language? Is the documentation publicly available?
Resource Description:
#11
Resource Type:
Resource Name:
Size: Enter package size - a number and a relevant unit of measurement, e.g., 48Mbyte, 5500 lexemes, 2.1Gbyte.
Resource Production Status:
Language(s):
Modality:
Use of the Resource:
Resource Availability:
License: Licence type, e.g., ELRA, LDC, Gnu, CreativeCommons, OpenSource, etc.
Resource URL (if available):
Documentation: Is there documentation? In which language? Is the documentation publicly available?
Resource Description:
#12
Resource Type:
Resource Name:
Size: Enter package size - a number and a relevant unit of measurement, e.g., 48Mbyte, 5500 lexemes, 2.1Gbyte.
Resource Production Status:
Language(s):
Modality:
Use of the Resource:
Resource Availability:
License: Licence type, e.g., ELRA, LDC, Gnu, CreativeCommons, OpenSource, etc.
Resource URL (if available):
Documentation: Is there documentation? In which language? Is the documentation publicly available?
Resource Description:
#13
Resource Type:
Resource Name:
Size: Enter package size - a number and a relevant unit of measurement, e.g., 48Mbyte, 5500 lexemes, 2.1Gbyte.
Resource Production Status:
Language(s):
Modality:
Use of the Resource:
Resource Availability:
License: Licence type, e.g., ELRA, LDC, Gnu, CreativeCommons, OpenSource, etc.
Resource URL (if available):
Documentation: Is there documentation? In which language? Is the documentation publicly available?
Resource Description:
#14
Resource Type:
Resource Name:
Size: Enter package size - a number and a relevant unit of measurement, e.g., 48Mbyte, 5500 lexemes, 2.1Gbyte.
Resource Production Status:
Language(s):
Modality:
Use of the Resource:
Resource Availability:
License: Licence type, e.g., ELRA, LDC, Gnu, CreativeCommons, OpenSource, etc.
Resource URL (if available):
Documentation: Is there documentation? In which language? Is the documentation publicly available?
Resource Description:
#15
Resource Type:
Resource Name:
Size: Enter package size - a number and a relevant unit of measurement, e.g., 48Mbyte, 5500 lexemes, 2.1Gbyte.
Resource Production Status:
Language(s):
Modality:
Use of the Resource:
Resource Availability:
License: Licence type, e.g., ELRA, LDC, Gnu, CreativeCommons, OpenSource, etc.
Resource URL (if available):
Documentation: Is there documentation? In which language? Is the documentation publicly available?
Resource Description:

More resources      Fewer resources

START Conference Manager (V2.61.0 - Rev. 6236M)