Round 7 Train DatasetThis is the training data used to construct and evaluate trojan detection software solutions. This data, generated at NIST, consists of natural language processing (NLP) AIs trained to perform named entity recognition (NER) on English text. A known percentage of these trained AI models have been poisoned with a known trigger which induces incorrect behavior. This data will be used to develop software solutions for detecting which trained AI models have been poisoned via embedded triggers.

Round 7 Test DatasetThis is the test data used to construct and evaluate trojan detection software solutions. This data, generated at NIST, consists of natural language processing (NLP) AIs trained to perform named entity recognition (NER) on English text. A known percentage of these trained AI models have been poisoned with a known trigger which induces incorrect behavior. This data will be used to develop software solutions for detecting which trained AI models have been poisoned via embedded triggers.

Round 7 Holdout DatasetThis is the holdout data used to construct and evaluate trojan detection software solutions. This data, generated at NIST, consists of natural language processing (NLP) AIs trained to perform named entity recognition (NER) on English text. A known percentage of these trained AI models have been poisoned with a known trigger which induces incorrect behavior. This data will be used to develop software solutions for detecting which trained AI models have been poisoned via embedded triggers.

Round 8 Train DatasetThis is the training data used to construct and evaluate trojan detection software solutions. This data, generated at NIST, consists of natural language processing (NLP) AIs trained to perform extractive question answering (QA on English text. A known percentage of these trained AI models have been poisoned with a known trigger which induces incorrect behavior. This data will be used to develop software solutions for detecting which trained AI models have been poisoned via embedded triggers.

Contains detailed information derived from the Office actions issued by patent examiners to applicants during the patent examination process. The Office Action is a written notification to the applicant of the examiners decision on patentability. It generally discloses the reasons for any rejections, objections, or requirements and includes relevant information or references that the applicant may find useful for responding to the examiner and deciding whether to continue prosecuting the application.

Contains detailed information derived from the Office actions issued by patent examiners to applicants during the patent examination process. The Office Action is a written notification to the applicant of the examiners decision on patentability. It generally discloses the reasons for any rejections, objections, or requirements and includes relevant information or references that the applicant may find useful for responding to the examiner and deciding whether to continue prosecuting the application.

The Office Action Retrieval API provides access to the full-text information of Office Actions (bundled as a JSON file in downloadable weekly zip files) issued by patent examiners to applicants during the patent examination process. The Office Action is a written notification to the applicant of the examiners decision on patentability. It generally discloses the reasons for any rejections, objections, or requirements and includes relevant information or references that the applicant may find useful for responding to the examiner and deciding whether to continue prosecuting the application.

Use this API to retrieve patent assignment information from the USPTO assignment search database and generate XML files with the search results. An XML file with search results contains a list of found documents and their categorization. For API, please use Chrome or Safari browser.

Patent Examination Data System lets customers retrieve and download multiple records of USPTO patent application or patent filing status at no cost. PEDS contains the bibliographic, published document and patent term extension data tabs in Public PAIR from 1981 to present. There is also some data dating back to 1935. Customers can download the entire dataset containing the data for all indexed documents. There are over 13 million records in PEDS. The data can be accessed by anyone using the web interface or the provided Application Programming Interface (API).

Use this API to search the Office of the Chief Economist (OCE) Patent Examination Event Codes Dataset 2015. The Event Codes dataset includes short descriptions of the event codes used in the transactions dataset. The descriptions can be linked to transactions using the event_code variable. There are 1,873 unique event codes represented in this data file.