Curriculum Project for Information Extraction. Task definitions Task 1: Entity detection and recognition Task 2: Relation detection and recognition Both.

Slides:



Advertisements
Similar presentations
Teaming Up. Teams A group of people working together to accomplish a task.
Advertisements

May 2, May 2, 2015May 2, 2015May 2, 2015 Azusa, CA Sheldon X. Liang Ph. D. Software Engineering in CS at APU Azusa Pacific University, Azusa, CA.
Evaluation Team Chair Training Presented By Dr. Tim Eaton TRACS Regional Representative.
Software Testing and Quality Assurance
CSE 784 Software Studio Phil Pratt-Szeliga Fall 2010 Slides Derived From: Dr. Fawcett.
CSE 111: Object Oriented Design. Design “To program is human but to design is divine” (WEH)
CSc 160 Overview of Fundamentals of Computer Programming II Spring (SO1) 2004.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
Mobile Application for SAT Preparation Preliminary Project Plan By Project Team: Hi5 Anant Kambli Amit Shukla Ajaykumar Aswathappa Prabin Gautam Rama K.
Introduction to Information System Development.
CryptKeeper Project Plan 1 CryptKeeper Project Plan.
PROJECT PLANNING. PLANNING Planning is essential and software development is no exception. Achieving success in software development requires planning.
Web Trnsport – Beta Testing and Implementation TUG Roundtable Discussion Elizabeth Rodgers Info Tech, Inc. October 9, 2007.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Software Process Models.
1 Chapter 5 Software Engineering Practice. 2 What is “Practice”? Practice is a broad array of concepts, principles, methods, and tools that you must consider.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Coming up: Software Engineering: A Practitioner’s Approach, 6/e Chapter 5 Practice: A Generic View copyright © 1996, 2001, 2005 R.S. Pressman & Associates,
MAE126B Report Writing Lecture Refer also to MAE126A Report Writing Lecture.
Exploring an Open Source Automation Framework Implementation.
The TERN Task EVALITA 2007 Valentina Bartalesi Lenzi & Rachele Sprugnoli
Ahmad Al-Ghoul. Learning Objectives Explain what a project is,, list various attributes of projects. Describe project management, discuss Who uses Project.
April 1, 2007 Global Design Effort 1 Materials for S4 meeting Discussion of risks in BDS WP April 1, 2007.
Test vs. inspection Part 2 Tor Stålhane. Testing and inspection A short data analysis.
Intro: FIT1001 Computer Systems S Important Notice for Lecturers This file is in skeleton form only Lecturers are expected to modify / enhance.
11/12/2009 Beta Prototype. 11/12/2009 TOPICS FOR TODAY Project Schedule o Milestones (Past and Future) o Work hours Beta Design and Architecture o Overview.
Object Oriented Programming (OOP) Design Lecture 1 : Course Overview Bong-Soo Sohn Associate Professor School of Computer Science and Engineering Chung-Ang.
Physics Project Management Chin-Sung Lin Eleanor Roosevelt High School.
Ensures project work is divided evenly and everyone has the necessary resources to keep the project on track as well as making sure all members contribute.
ACE Automatic Content Extraction A program to develop technology to extract and characterize meaning from human language.
CSE Senior Design II Day 1: Getting Organized Spring 2015 Instructor: Manfred Huber.
1 Pre-Exam Lecture 4 Final Examination is scheduled on Monday December 18th at 1:30PM in class 4 There are 8 questions with or without sub- parts and.
Team Manager’s Meeting June 6, Team Managers Duties Our practice is to try and delegate responsibility of portions of the website to the individual.
Lab Results Interface Validation Suite WG July 28, 2011.
EM Report1 Report from Engineering Management Group to GDE EC 2007/12/12 Report by N.Toge.
ITCS 6265 Details on Project & Paper Presentation.
Lecture 13.  Failure mode: when team understands requirements but is unable to meet them.  To ensure that you are building the right system Continually.
Functions Part I (Syntax). What is a function? A function is a set of statements which is split off into a separate entity that can be used like a “new.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
The Level-2 Projects for Course Clusters Haojun Sun College of Engineering Shantou University.
Computer Networks CNT5106C
10/23/2009 Alpha Prototype. 10/23/2009 TOPICS FOR TODAY Project Schedule o Achievements o The last few weeks... System Design and Architecture (new) Prototype.
Software Process Models.
CSE Senior Design II Day 1: Getting Organized Spring 2012 Instructor: Mike O’Dell.
CSE Senior Design II Day 1: Getting Organized Spring 2016 Instructor: Mike O’Dell.
1 Sean Aluoto Anthony Keeley Eric Werner. 2 Project Plan Overview Project Lifecycle model Time line Deliverables Organization plan Risk management Design.
The following training presentation is for all 1Prospect employees and is taken upon joining the company team. Quality Management System (QMS) Training.
T Iteration Demo LicenseChecker I2 Iteration
L5 Computing Team Project Final Presentation Guidelines.
CSE784 – Software Studio Jim Fawcett Fall 2002.
Day 1: Getting Organized Spring 2014
CS616 Software Engineering I BoNY
Proposal for Term Project
IEEE Std 1074: Standard for Software Lifecycle
CSE784 – Software Studio Jim Fawcett Fall 2006.
Roles and Responsibilities (1/3)
Step 1 : Submit Project Information
Day 1: Getting Organized Fall 2012
Day 1: Getting Organized Summer 2012
homework assignment due Feb 23
Final Project Description
Day 1: Getting Organized Fall 2013
Day 1: Getting Organized Spring 2013
Project Name Group Members.
Project Name Group Members.
Guidelines Please do not add more slides than required by this template Presentation time 5min Rehearse!
Day 1: Getting Organized Spring 2011
Project Name Group Members.
<Your Team # > Your Team Name Here
Your Project Title (It is YOUR project, not the team's project, not CAM2) Your Name Date.
Presentation transcript:

Curriculum Project for Information Extraction

Task definitions Task 1: Entity detection and recognition Task 2: Relation detection and recognition Both of the tasks are based on ACE projects.

Task definitions (EDR) Task 1: Entity detection and recognition The Entity Detection and Recognition task (EDR) requires that certain specified types of entities that are mentioned in the source language data be detected and that selected information about these entities be recognized and merged into a unified representation for each detected entity.

Task definitions (EDR) Subtypes in the table are for reference only

Task definitions (RDR) Task 2: Relation detection and recognition The Relation Detection and Recognition task (RDR) requires that certain specified types of relations that are mentioned in the source language data be detected and that selected information about these relations be recognized and merged into a unified representation for each detected relation.

Task definitions (RDR) A relation is a relation between two entities, which are called the relation arguments. Some relations are symmetric, meaning that the ordering of the two entities does not matter (e.g., “partner”). But for asymmetric relations the order does matter (e.g., “subsidiary”) and for these relations the entity arguments must be assigned the correct argument role.

Task definitions (RDR) (Subtypes in the table are for reference only)

Task definitions ACE website: For more details: Curriculum Project for Information Extraction.doc

Team organization A student can accomplish the task alone. But we encourage students to organize their teams towards a common goal.

Team organization A team has its name and leader. The team can be formed with 2-4 members. Since task 2 is based on task1, teams working on task 2 will get a higher score and must be composed of at least 3 members. The leader must be responsible for the work arrangement and project quality.

Team organization The member selection should meet the combination validity (that is, the remainders of their student numbers' last two digits divided by the number of members of the team must be different). Each member should focus on different tasks and study the corresponding topics intensively.

Document Registration Form 1)Team name: 2)Team members: Leader: Student No. Member1: Student No. Member2: Student No. Member3: Student No. 3)Tasks: (EDR/RDR) 4)Language: (Chinese/English) 5)Implementation Schedule:

Document Mid-term Research Report 1) Preliminary research 2) Preliminary system architecture 3) Preliminary system implementation method 4) Conclusion & references Project Report 1) System architecture 2) System implementation method 3) Contributions 4) Conclusion & references 5) Everything else worth mentioning

Document DocumentDeadline Registration formSep.19 Mid-term research reportOct.18 Project report, presentation, and source code16 th week

Demo Workshop The workshop will be held in the 17 th week. You will be required to make a presentation to show us what you have done and we will evaluate your project.

Evaluation Total (70%)  Presentation (9%)  Implementation (40%) Performance(22%) Algorithm (11%) Interface (4%) Stability(3%)  Source Code (7%)  Document (14%)

Assignments Deliver assignments to: Files should be named as: student number+name+(X).pdf X is the serial number of the assignment.

An Example Final project report by team1 last year

Thank you!