metadata

annotations_creators:
  - no-annotation
language_creators:
  - found
languages:
  - en
license:
  - apache-2.0
multilinguality:
  - monolingual
pretty_name: AdapTable-cluster11
size_categories:
  - 100K<n<1M
source_datasets: []
task_categories:
  - multiple-choice
  - question-answering
  - zero-shot-classification
  - text2text-generation
  - table-question-answering
  - text-generation
  - text-classification
  - tabular-classification
task_ids:
  - multiple-choice-qa
  - extractive-qa
  - open-domain-qa
  - closed-domain-qa
  - closed-book-qa
  - open-book-qa
  - language-modeling
  - multi-class-classification
  - natural-language-inference
  - topic-classification
  - multi-label-classification
  - tabular-multi-class-classification
  - tabular-multi-label-classification

Dataset Card for "AdapTable-cluster11" - Dataset of Few-shot Tasks from Tables

Dataset Description
Dataset Structure
Dataset Creation
Considerations for Using the Data
Additional Information

Dataset Description

Homepage: [Needs More Information]
Repository: https://github.com/JunShern/few-shot-pretraining
Paper: Exploring Few-Shot Adaptation of Language Models with Tables
Leaderboard: [Needs More Information]
Point of Contact: junshern@nyu.edu, perez@nyu.edu

Dataset Summary

The AdapTable dataset consists of tables that naturally occur on the web and that are formatted as few-shot tasks for fine-tuning language models to improve their few-shot performance.

There are several dataset versions available:

AdapTable-full: Starting from the initial WTC corpus of 50M tables, we apply our tables-to-tasks procedure to produce our resulting dataset, AdapTable-full, which comprises 413,350 tasks from 23,744 unique websites.
AdapTable-unique: This is the same as AdapTable-full but filtered to have a maximum of one task per website. AdapTable-unique contains exactly 23,744 tasks from 23,744 websites.
AdapTable-5k: This dataset uses 5k random tables from the full dataset.
AdapTable data subsets based on a manual human quality rating:
AdapTable data subsets based on the website of origin:
AdapTable data subsets based on clustering (for the clustering details please see our publication):

Supported Tasks and Leaderboards

Since the tables come from the web, the distribution of tasks and topics is very broad. The shape of our dataset is very wide, i.e., we have 1000's of tasks, while each task has only a few examples, compared to most current NLP datasets which are very deep, i.e., 10s of tasks with many examples. This implies that our dataset covers a broad range of potential tasks, e.g., multiple-choice, question-answering, table-question-answering, text-classification, etc.

The intended use of this dataset is to improve few-shot performance by fine-tuning/pre-training on our dataset.

Languages

English

Dataset Structure

Data Instances

Each table, i.e., task is represented as a json-lines file and consists of several few-shot examples. Each example is a dictionary containing a field 'task', which identifies the task, followed by an 'input', 'options', and 'output' field. The 'input' field contains several column elements of the same row in the table, while the 'output' field is a target which represents an individual column of the same row. Each task contains several such examples which can be concatenated as a few-shot task. In the case of multiple choice classification, the 'options' field contains the possible classes that a model needs to choose from.

There are also additional meta-data fields such as 'pageTitle', 'title', 'outputColName', 'url', 'wdcFile'.

Data Fields

'task': task identifier

'input': column elements of a specific row in the table.

'options': for multiple choice classification, it provides the options to choose from.

'output': target column element of the same row as input.

'pageTitle': the title of the page containing the table.

'outputColName': output column name

'url': url to the website containing the table

'wdcFile': WDC Web Table Corpus file

Data Splits

The AdapTable datasets do not come with additional data splits.

Dataset Creation

Curation Rationale

How do we convert tables to few-shot tasks? Unlike unstructured text, structured data in the form of tables lends itself easily to the few-shot task format. Given a table where each row is an instance of a similar class and the columns describe the attributes of each instance, we can turn each row into a task example to predict one attribute given the others. When the table has more than one row, we instantly have multiple examples of this task by using each row as a single example, and thus each table becomes a few-shot dataset for a particular task.

The few-shot setting in this setup is significant: Tables often do not come with clear instructions for each field, so tasks may be underspecified if prompted in a zero-shot manner, but the intended task becomes clearer when examples are provided. This makes a good two-way match: The few-shot format is a perfect setup for table learning, and tables provide a natural dataset for few-shot training.

Source Data

Initial Data Collection and Normalization

The data processing pipeline is explained in detail in our publication.

Who are the source language producers?

The dataset is extracted from WDC Web Table Corpora.

Annotations

Annotation process

No manual annotation process used. Only for the AdapTable-rated-low, AdapTable-rated-medium, and AdapTable-rated-high manual annotations were carried out.

Who are the annotators?

People involved in the publication.

Personal and Sensitive Information

The data was extracted from WDC Web Table Corpora, which in turn extracted tables from the Common Crawl. We did not filter the data in any way. Thus any user identities or otherwise sensitive information (e.g., data that reveals racial or ethnic origins, sexual orientations, religious beliefs, political opinions or union memberships, or locations; financial or health data; biometric or genetic data; forms of government identification, such as social security numbers; criminal history, etc.) might be contained in our dataset.

Considerations for Using the Data

Social Impact of Dataset

The purpose of this dataset is to help develop models that are better at few-shot learning and have higher few-shot performance by fine-tuning few-shot tasks extracted from tables.

While tables have a similar structure to few-shot tasks and we do see an improved performance on few-shot tasks in our paper, we want to make clear that fine-tuning on tables also has its risks. First of all, since the tables are extracted from the web, they may contain user identities or otherwise sensitive information which a model might reveal at inference, or which could influence the learning process of a model in a negative way. Second, since tables are very diverse in nature, the model also trains on low-quality data or data with an unusual structure. While it is interesting that training on such data improves few-shot performance on downstream tasks, this could also imply that the model learns concepts that are very dissimilar to human concepts that would be useful for a certain downstream task. In other words, it is possible that the model learns weird things that are helpful on the evaluated downstream tasks, but might lead to bad out-of-distribution behavior.

Discussion of Biases

Since our dataset contains tables that are scraped from the web, it will also contain many toxic, racist, sexist, and otherwise harmful biases and texts. We have not run any analysis on the biases prevalent in our datasets. Neither have we explicitly filtered the content. This implies that a model trained on our dataset will potentially reinforce harmful biases and toxic text that exist in our dataset.

Other Known Limitations

No additional known limitations.

Additional Information

Dataset Curators

Jun Shern Chan, Michael Pieler, Jonathan Jao, Jérémy Scheurer, Ethan Perez

Licensing Information

Apache 2.0

Citation Information

[Needs More Information]

Datasets:

MicPie
/

unpredictable_cluster11