Sebastian Gehrmann commited on
Commit
3e2ed53
1 Parent(s): cfedfc8

data card.

Browse files
Files changed (1) hide show
  1. README.md +409 -161
README.md CHANGED
@@ -1,21 +1,85 @@
1
- ## Dataset Overview
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
2
 
3
- ### Where to find the data and its documentation
4
 
5
- #### What is the webpage for the dataset (if it exists)?
6
 
7
- https://github.com/nlgcat/sport_sett_basketball
 
 
8
 
9
- #### What is the link to where the original dataset is hosted?
10
 
11
- https://github.com/nlgcat/sport_sett_basketball
 
 
12
 
13
- #### What is the link to the paper describing the dataset (open access preferred)?
14
 
15
- https://aclanthology.org/2020.intellang-1.4/
 
 
16
 
17
- #### Provide the BibTex-formatted reference for the dataset. Please use the correct published version (ACL anthology, etc.) instead of google scholar created Bibtex.
18
 
 
 
19
  ```
20
  @inproceedings{thomson-etal-2020-sportsett,
21
  title = "{S}port{S}ett:Basketball - A robust and maintainable data-set for Natural Language Generation",
@@ -30,83 +94,153 @@ https://aclanthology.org/2020.intellang-1.4/
30
  url = "https://aclanthology.org/2020.intellang-1.4",
31
  pages = "32--40",
32
  }
33
- ```
 
 
34
 
35
- #### If known, provide the name of at least one person the reader can contact for questions about the dataset.
 
 
 
36
 
37
- Craig Thomson
38
 
39
- #### If known, provide the email of at least one person the reader can contact for questions about the dataset.
 
 
40
 
41
42
 
43
- #### Does the dataset have an active leaderboard?
 
 
44
 
45
- no
46
 
47
- ### Languages and Intended Use
48
 
49
- #### Is the dataset multilingual?
50
 
51
- no
 
 
 
52
 
53
- #### What dialects are covered? Are there multiple dialects per language?
54
 
 
 
55
  American English
56
 
57
- One dialect, one language.
 
 
 
 
 
 
 
 
 
 
 
 
 
58
 
59
- #### What languages/dialects are covered in the dataset?
60
 
61
- English
 
 
 
62
 
63
- #### Whose language is in the dataset?
64
 
65
- American sports writers
 
 
66
 
67
- #### What is the license of the dataset?
68
 
69
- mit: MIT License
 
 
70
 
71
- #### What is the intended use of the dataset?
72
 
73
- Maintain a robust and scalable Data-to-Text generation resource with structured data and textual summaries
 
 
 
74
 
75
- #### What primary task does the dataset support?
76
 
77
- Data-to-Text
78
 
79
- #### Provide a short description of the communicative goal of a model trained for this task on this dataset.
80
 
81
- A model trained on this dataset should summarise the statistical and other information from a basketball game. This will be focused on a single game, although facts from prior games, or aggregate statistics over many games can and should be used for comparison where appropriate. There no single common narrative, although summaries usually start with who player, when, where, and the score. They then provide high level commentary on what the difference in the game was (why the winner won). breakdowns of statistics for prominent players follow, winning team first. Finally, the upcoming schedule for both teams is usually included. There are, however, other types of fact that can be included, and other narrative structures.
 
 
82
 
83
- ### Credit
84
 
85
- #### In what kind of organization did the dataset curation happen?
 
 
86
 
87
- academic
88
 
89
- #### Name the organization(s).
 
 
90
 
91
- University of Aberdeen, Robert Gordon University
92
 
93
- #### Who created the original dataset? List the people involved in collecting the dataset and their affiliation(s).
 
 
94
 
95
- Craig Thomson, Ashish Upadhyay
96
 
97
- #### Who funded the data creation?
 
 
98
 
99
- EPSRC
100
 
101
- #### Who contributed to the data card and adding the dataset to GEM? List the people+affiliations involved in creating this data card and who helped integrate this dataset into GEM.
102
 
103
- Craig Thomson, Ashish Upadhyay
104
 
105
- ### Structure
 
 
106
 
107
- #### Provide a JSON formatted example of a typical instance in the dataset.
108
 
109
- ```json
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
110
  {
111
  "sportsett_id": "1",
112
  "gem_id": "GEM-sportsett_basketball-train-0",
@@ -1180,48 +1314,68 @@ Craig Thomson, Ashish Upadhyay
1180
  "The Miami Heat ( 20 ) defeated the Philadelphia 76ers ( 0 - 3 ) 114 - 96 on Saturday . Chris Bosh scored a game - high 30 points to go with eight rebounds in 33 minutes . Josh McRoberts made his Heat debut after missing the entire preseason recovering from toe surgery . McRoberts came off the bench and played 11 minutes . Shawne Williams was once again the starter at power forward in McRoberts ' stead . Williams finished with 15 points and three three - pointers in 29 minutes . Mario Chalmers scored 18 points in 25 minutes off the bench . Luc Richard Mbah a Moute replaced Chris Johnson in the starting lineup for the Sixers on Saturday . Hollis Thompson shifted down to the starting shooting guard job to make room for Mbah a Moute . Mbah a Moute finished with nine points and seven rebounds in 19 minutes . K.J . McDaniels , who suffered a minor hip flexor injury in Friday 's game , was available and played 21 minutes off the bench , finishing with eight points and three blocks . Michael Carter-Williams is expected to be out until Nov. 13 , but Tony Wroten continues to put up impressive numbers in Carter-Williams ' absence . Wroten finished with a double - double of 21 points and 10 assists in 33 minutes . The Heat will complete a back - to - back set at home Sunday against the Tornoto Raptors . The Sixers ' next game is at home Monday against the Houston Rockets ."
1181
  ]
1182
  }
1183
- ```
1184
 
1185
- #### Describe and name the splits in the dataset if there are more than one.
1186
 
1187
- Train: NBA seasons - 2014, 2015, & 2016; total instances - 3690
1188
- Validation: NBA seasons - 2017; total instances - 1230
1189
- Test: NBA seasons - 2018; total instances - 1230
 
 
1190
 
1191
- #### Describe any criteria for splitting the data, if used. If there are differences between the splits (e.g., if the training annotations are machine-generated and the dev and test ones are created by humans, or if different numbers of annotators contributed to each example), describe them here.
1192
 
1193
- The splits were created as per different NBA seasons. All the games in regular season (no play-offs) are added in the dataset
 
 
1194
 
1195
- ## Dataset in GEM
1196
 
1197
- ### Rationale
1198
 
1199
- #### What does this dataset contribute toward better generation evaluation and why is it part of GEM?
1200
 
1201
- This dataset contains a data analytics problem in the classic sense (Reiter, 2007, https://aclanthology.org/W07-2315). That is, there is a large amount of data from which insights need to be selected. Further, the insights should be both from simple shallow queries (such as dirext transcriptions of the properties of a subject, i.e., a player and their statistics), as well as aggregated (how a player has done over time). There is far more on the data side than is required to be realised, and indeed, could be practically realised. This depth of data analytics problem does not exist in other datasets.
1202
 
1203
- #### Do other datasets for the high level task exist?
1204
 
1205
- no
 
 
1206
 
1207
- #### What aspect of model ability can be measured with this dataset?
1208
 
1209
- Many, if not all aspects of data-to-text systems can be measured with this dataset. It has complex data analytics, meaninful document planning (10-15 sentence documents with a narrative structure), as well as microplanning and realisation requirements. Finding models to handle this volume of data, as well as methods for meaninfully evaluate generations is a very open question.
 
 
1210
 
1211
- ### GEM Additional Curation
1212
 
1213
- #### Has the GEM version of the dataset been modified in any way (data, processing, splits) from the original curated data?
 
 
1214
 
1215
- no
1216
 
1217
- #### Does GEM provide additional splits to the dataset?
1218
 
1219
- no
1220
 
1221
- ### Getting Started
 
 
1222
 
1223
- #### Getting started with in-depth research on the task. Add relevant pointers to resources that researchers can consult when they want to get started digging deeper into the task.
1224
 
 
 
 
 
 
 
 
 
 
 
 
1225
  For dataset discussion see:
1226
  Thomson et al, 2020 https://aclanthology.org/2020.intellang-1.4/
1227
 
@@ -1235,191 +1389,285 @@ Thomson et al (2020): https://aclanthology.org/2020.inlg-1.6/
1235
 
1236
  For recent systems using the Rotowire dataset, see:
1237
  Puduppully & Lapata (2021): https://github.com/ratishsp/data2text-macro-plan-py
1238
- Rebuffel et all (2020): https://github.com/KaijuML/data-to-text-hierarchical
 
 
1239
 
1240
- ## Previous Results
1241
 
1242
- ### Previous Results
1243
 
1244
- #### What aspect of model ability can be measured with this dataset?
1245
 
1246
- Many, if not all aspects of data-to-text systems can be measured with this dataset. It has complex data analytics, meaninful document planning (10-15 sentence documents with a narrative structure), as well as microplanning and realisation requirements. Finding models to handle this volume of data, as well as methods for meaninfully evaluate generations is a very open question.
 
 
1247
 
1248
- #### What metrics are typically used for this task?
1249
 
1250
- BLEU
 
 
1251
 
1252
- #### List and describe the purpose of the metrics and evaluation methodology (including human evaluation) that the dataset creators used when introducing this task.
1253
 
1254
- BLEU is the only off-the-shelf metric commonly used. Works have also used custom metrics like RG (Wiseman et al, 2017: https://aclanthology.org/D17-1239), and a recent shared task explored other metrics and their corrolation with human evaluation (Thomson & Reiter, 2021: https://aclanthology.org/2021.inlg-1.23).
 
 
1255
 
1256
- #### Are previous results available?
1257
 
1258
- yes
 
 
1259
 
1260
- #### What evaluation approaches have others used?
1261
 
 
 
1262
  Most results from prior works use the original Rotowire dataset, which has train/validation/test contamination. For results of BLEU and RG on the relational database format of SportSett, as a guide, see Thomson et al, 2020:
1263
- https://aclanthology.org/2020.inlg-1.6.
1264
 
1265
- #### What are the most relevant previous results for this task/dataset?
1266
 
1267
- The results on this dataset are largely unexplored, as is the selection of suitable metrics that correlate with human judgment. See Thomson et al, 2021 (https://aclanthology.org/2021.inlg-1.23) for an overview, and Kasner et al (2021) for the best performing metric at the time of writing (https://aclanthology.org/2021.inlg-1.25).
 
 
1268
 
1269
- ## Dataset Curation
1270
 
1271
- ### Original Curation
1272
 
1273
- #### Original curation rationale
1274
 
1275
- The references texts were taken from the existing dataset RotoWire-FG (Wang, 2019: https://www.aclweb.org/anthology/W19-8639), which is in turn based on Rotowire (Wiseman et al, 2017: https://aclanthology.org/D17-1239). The rationale behind this dataset was to re-structure the data such that aggregate statistics over multiple games, as well as upcoming game schedules could be included, moving the dataset from snapshots of single games, to a format where almost everything that could be present in the reference texts could be found in the data.
1276
 
1277
- #### What was the communicative goal?
1278
 
1279
- Create a summary of a basketball, with insightful facts about the game, teams, and players, both within the game, withing periods during the game, and over the course of seasons/careers where appropriate. This is a data-to-text problem in the classic sense (Reiter, 2007: https://aclanthology.org/W07-2315) in that it has a difficult data analystics state, in addition to ordering and transcription of selected facts.
 
 
1280
 
1281
- #### Is the dataset aggregated from different data sources?
1282
 
1283
- yes
 
 
1284
 
1285
- #### List the sources (one per line)
1286
 
 
 
 
 
 
 
 
 
1287
  RotoWire-FG (https://www.rotowire.com).
1288
  Wikipedia (https://en.wikipedia.org/wiki/Main_Page)
1289
  Basketball Reference (https://www.basketball-reference.com)
1290
-
1291
 
1292
- ### Language Data
1293
 
1294
- #### How was the language data obtained?
1295
 
1296
- Found
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1297
 
1298
- #### If found, where from?
 
 
1299
 
1300
- Multiple websites
1301
 
1302
- #### What further information do we have on the language producers?
1303
 
1304
- None
1305
 
1306
- #### Does the language in the dataset focus on specific topics? How would you describe them?
 
 
 
1307
 
1308
- Summaries of basketball games (in the NBA).
1309
 
1310
- #### Was the text validated by a different worker or a data curator?
 
 
1311
 
1312
- not validated
1313
 
1314
- #### How was the text data pre-processed? (Enter N/A if the text was not pre-processed)
1315
 
1316
- It retains the original tokenization scheme employed by Wang 2019
1317
 
1318
- #### Were text instances selected or filtered?
 
 
1319
 
1320
- manually
1321
 
1322
- #### What were the selection criteria?
 
 
1323
 
1324
- Games from the 2014 through 2018 seasons were selected. Within these seasons games are not filtered, all are present, but this was an arbitrary solution from the original RotoWirte-FG dataset.
1325
 
1326
- ### Structured Annotations
1327
 
1328
- #### Does the dataset have additional annotations for each instance?
1329
 
1330
- none
 
 
 
1331
 
1332
- #### Was an annotation service used?
1333
 
1334
- no
 
 
1335
 
1336
- ### Consent
1337
 
1338
- #### Was there a consent policy involved when gathering the data?
 
 
1339
 
1340
- no
1341
 
1342
- #### If not, what is the justification for reusing the data?
1343
 
1344
- The dataset consits of a pre-existing dataset, as well as publically available facts.
1345
 
1346
- ### Private Identifying Information (PII)
 
 
1347
 
1348
- #### Does the source language data likely contain Personal Identifying Information about the data creators or subjects?
1349
 
1350
- unlikely
1351
 
1352
- #### What categories of PII are present or suspected in the data?
1353
 
1354
- generic PII
1355
 
1356
- #### Did the curators use any automatic/manual method to identify PII in the dataset?
1357
 
1358
- no identification
 
 
1359
 
1360
- ### Maintenance
1361
 
1362
- #### Does the original dataset have a maintenance plan?
1363
 
1364
- no
1365
 
1366
- ## Broader Social Context
 
 
1367
 
1368
- ### Previous Work on the Social Impact of the Dataset
1369
 
1370
- #### Are you aware of cases where models trained on the task featured in this dataset ore related tasks have been used in automated systems?
1371
 
1372
- no
1373
 
1374
- ### Impact on Under-Served Communities
 
 
1375
 
1376
- #### Does this dataset address the needs of communities that are traditionally underserved in language technology, and particularly language generation technology? Communities may be underserved for exemple because their language, language variety, or social or geographical context is underepresented in NLP and NLG resources (datasets and models).
1377
 
1378
- no
 
 
1379
 
1380
- ### Discussion of Biases
1381
 
1382
- #### Are there documented social biases in the dataset? Biases in this context are variations in the ways members of different social categories are represented that can have harmful downstream consequences for members of the more disadvantaged group.
 
 
1383
 
1384
- yes
1385
 
1386
- #### Provide links to and summaries of works analyzing these biases.
1387
 
1388
- Unaware of any work, but, this is a dataset considting solely of summaries of mens professional basketball games. It does not cover different levels of the sport, or different genders, and all pronouns are likely to be male unless a specific player is referred to by other pronouns in the training text. This makes it difficult to train systems where gender can be specified as an attribute, although it is an interesting, open problem that could be investigated using the dataset.
1389
 
1390
- #### Does the distribution of language producers in the dataset accurately represent the full distribution of speakers of the language world-wide? If not, how does it differ?
1391
 
1392
- No, it is very specifically American English from the sports journalism domain.
1393
 
1394
- ## Considerations for Using the Data
 
 
1395
 
1396
- ### PII Risks and Liability
1397
 
1398
- #### Considering your answers to the PII part of the Data Curation Section, describe any potential privacy to the data subjects and creators risks when using the dataset.
1399
 
1400
- All information relating to persons is of public record.
1401
 
1402
- ### Licenses
 
 
1403
 
1404
- #### Based on your answers in the Intended Use part of the Data Overview Section, which of the following best describe the copyright and licensing status of the dataset?
1405
 
1406
- public domain
 
 
1407
 
1408
- #### Based on your answers in the Language part of the Data Curation Section, which of the following best describe the copyright and licensing status of the underlying language data?
1409
 
1410
- public domain
1411
 
1412
- ### Known Technical Limitations
1413
 
1414
- #### Describe any known technical limitations, such as spurrious correlations, train/test overlap, annotation biases, or mis-annotations, and cite the works that first identified these limitations when possible.
 
 
1415
 
1416
- SportSett resolved the major overlap problems of RotoWire, although some overlap is unavoidable. For example, whilst it is not possible to find career totals and other historic information for all players (the data only goes back to 2014), it is possible to do so for some players. It is unavoidable that some data which is aggregated, exists in its base form in previous partitions. The season-based partition scheme heavily constrains this however.
1417
 
1418
- #### When using a model trained on this dataset in a setting where users or the public may interact with its predictions, what are some pitfalls to look out for? In particular, describe some applications of the general task featured in this dataset that its curation or properties make it less suitable for.
 
 
1419
 
1420
- Factual accuray continues to be a problem, systems may incorrectly represent the facts of the game.
1421
 
1422
- #### What are some discouraged use cases of a model trained to maximize the proposed metrics on this dataset? In particular, think about settings where decisions made by a model that performs reasonably well on the metric my still have strong negative consequences for user or members of the public.
 
 
1423
 
1424
- Using the RG metric to maximise the number of true facts in a generate summary is not nececeraly
1425
 
 
1
+ ---
2
+ annotations_creators:
3
+ - none
4
+ language_creators:
5
+ - unknown
6
+ languages:
7
+ - unknown
8
+ licenses:
9
+ - mit
10
+ multilinguality:
11
+ - unknown
12
+ pretty_name: sportsett_basketball
13
+ size_categories:
14
+ - unknown
15
+ source_datasets:
16
+ - original
17
+ task_categories:
18
+ - data-to-text
19
+ task_ids:
20
+ - unknown
21
+ ---
22
+
23
+ # Dataset Card for GEM/sportsett_basketball
24
+
25
+ ## Dataset Description
26
+
27
+ - **Homepage:** https://github.com/nlgcat/sport_sett_basketball
28
+ - **Repository:** https://github.com/nlgcat/sport_sett_basketball
29
+ - **Paper:** https://aclanthology.org/2020.intellang-1.4/
30
+ - **Leaderboard:** N/A
31
+ - **Point of Contact:** Craig Thomson
32
+
33
+ ### Link to Main Data Card
34
+
35
+ You can find the main data card on the [GEM Website](https://gem-benchmark.com/data_cards/sportsett_basketball).
36
+
37
+ ### Dataset Summary
38
+
39
+ The sportsett dataset is an English data-to-text dataset in the basketball domain. The inputs are statistics summarizing an NBA game and the outputs are high-quality descriptions of the game in natural language.
40
+
41
+ You can load the dataset via:
42
+ ```
43
+ import datasets
44
+ data = datasets.load_dataset('GEM/sportsett_basketball')
45
+ ```
46
+ The data loader can be found [here](https://huggingface.co/datasets/GEM/sportsett_basketball).
47
+
48
+ #### website
49
+ [Github](https://github.com/nlgcat/sport_sett_basketball)
50
+
51
+ #### paper
52
+ [ACL Anthology](https://aclanthology.org/2020.intellang-1.4/)
53
+
54
+ #### authors
55
+ Craig Thomson, Ashish Upadhyay
56
+
57
+ ## Dataset Overview
58
 
59
+ ### Where to find the Data and its Documentation
60
 
61
+ #### Webpage
62
 
63
+ <!-- info: What is the webpage for the dataset (if it exists)? -->
64
+ <!-- scope: telescope -->
65
+ [Github](https://github.com/nlgcat/sport_sett_basketball)
66
 
67
+ #### Download
68
 
69
+ <!-- info: What is the link to where the original dataset is hosted? -->
70
+ <!-- scope: telescope -->
71
+ [Github](https://github.com/nlgcat/sport_sett_basketball)
72
 
73
+ #### Paper
74
 
75
+ <!-- info: What is the link to the paper describing the dataset (open access preferred)? -->
76
+ <!-- scope: telescope -->
77
+ [ACL Anthology](https://aclanthology.org/2020.intellang-1.4/)
78
 
79
+ #### BibTex
80
 
81
+ <!-- info: Provide the BibTex-formatted reference for the dataset. Please use the correct published version (ACL anthology, etc.) instead of google scholar created Bibtex. -->
82
+ <!-- scope: microscope -->
83
  ```
84
  @inproceedings{thomson-etal-2020-sportsett,
85
  title = "{S}port{S}ett:Basketball - A robust and maintainable data-set for Natural Language Generation",
 
94
  url = "https://aclanthology.org/2020.intellang-1.4",
95
  pages = "32--40",
96
  }
97
+ ```
98
+
99
+ #### Contact Name
100
 
101
+ <!-- quick -->
102
+ <!-- info: If known, provide the name of at least one person the reader can contact for questions about the dataset. -->
103
+ <!-- scope: periscope -->
104
+ Craig Thomson
105
 
106
+ #### Contact Email
107
 
108
+ <!-- info: If known, provide the email of at least one person the reader can contact for questions about the dataset. -->
109
+ <!-- scope: periscope -->
110
111
 
112
+ #### Has a Leaderboard?
113
 
114
+ <!-- info: Does the dataset have an active leaderboard? -->
115
+ <!-- scope: telescope -->
116
+ no
117
 
 
118
 
119
+ ### Languages and Intended Use
120
 
121
+ #### Multilingual?
122
 
123
+ <!-- quick -->
124
+ <!-- info: Is the dataset multilingual? -->
125
+ <!-- scope: telescope -->
126
+ no
127
 
128
+ #### Covered Dialects
129
 
130
+ <!-- info: What dialects are covered? Are there multiple dialects per language? -->
131
+ <!-- scope: periscope -->
132
  American English
133
 
134
+ One dialect, one language.
135
+
136
+ #### Covered Languages
137
+
138
+ <!-- quick -->
139
+ <!-- info: What languages/dialects are covered in the dataset? -->
140
+ <!-- scope: telescope -->
141
+ `English`
142
+
143
+ #### Whose Language?
144
+
145
+ <!-- info: Whose language is in the dataset? -->
146
+ <!-- scope: periscope -->
147
+ American sports writers
148
 
149
+ #### License
150
 
151
+ <!-- quick -->
152
+ <!-- info: What is the license of the dataset? -->
153
+ <!-- scope: telescope -->
154
+ mit: MIT License
155
 
156
+ #### Intended Use
157
 
158
+ <!-- info: What is the intended use of the dataset? -->
159
+ <!-- scope: microscope -->
160
+ Maintain a robust and scalable Data-to-Text generation resource with structured data and textual summaries
161
 
162
+ #### Primary Task
163
 
164
+ <!-- info: What primary task does the dataset support? -->
165
+ <!-- scope: telescope -->
166
+ Data-to-Text
167
 
168
+ #### Communicative Goal
169
 
170
+ <!-- quick -->
171
+ <!-- info: Provide a short description of the communicative goal of a model trained for this task on this dataset. -->
172
+ <!-- scope: periscope -->
173
+ A model trained on this dataset should summarise the statistical and other information from a basketball game. This will be focused on a single game, although facts from prior games, or aggregate statistics over many games can and should be used for comparison where appropriate. There no single common narrative, although summaries usually start with who player, when, where, and the score. They then provide high level commentary on what the difference in the game was (why the winner won). breakdowns of statistics for prominent players follow, winning team first. Finally, the upcoming schedule for both teams is usually included. There are, however, other types of fact that can be included, and other narrative structures.
174
 
 
175
 
176
+ ### Credit
177
 
178
+ #### Curation Organization Type(s)
179
 
180
+ <!-- info: In what kind of organization did the dataset curation happen? -->
181
+ <!-- scope: telescope -->
182
+ `academic`
183
 
184
+ #### Curation Organization(s)
185
 
186
+ <!-- info: Name the organization(s). -->
187
+ <!-- scope: periscope -->
188
+ University of Aberdeen, Robert Gordon University
189
 
190
+ #### Dataset Creators
191
 
192
+ <!-- info: Who created the original dataset? List the people involved in collecting the dataset and their affiliation(s). -->
193
+ <!-- scope: microscope -->
194
+ Craig Thomson, Ashish Upadhyay
195
 
196
+ #### Funding
197
 
198
+ <!-- info: Who funded the data creation? -->
199
+ <!-- scope: microscope -->
200
+ EPSRC
201
 
202
+ #### Who added the Dataset to GEM?
203
 
204
+ <!-- info: Who contributed to the data card and adding the dataset to GEM? List the people+affiliations involved in creating this data card and who helped integrate this dataset into GEM. -->
205
+ <!-- scope: microscope -->
206
+ Craig Thomson, Ashish Upadhyay
207
 
 
208
 
209
+ ### Dataset Structure
210
 
211
+ #### Data Fields
212
 
213
+ <!-- info: List and describe the fields present in the dataset. -->
214
+ <!-- scope: telescope -->
215
+ Each instance in the dataset has five fields.
216
 
217
+ 1. "sportsett_id": This is a unique id as used in the original SportSett database. It starts with '1' with the first instance in the train-set and ends with '6150' with the last instance in test-set.
218
 
219
+ 2. "gem_id": This is a unique id created as per GEM's requirement which follows the `GEM-${DATASET_NAME}-${SPLIT-NAME}-${id}` pattern.
220
+
221
+ 3. "game": This field contains a dictionary with information about current game. It has information such as date on which the game was played alongwith the stadium, city, state where it was played.
222
+
223
+ 4. "teams": This filed is a dictionary of multiple nested dictionaries. On the highest level, it has two keys: 'home' and 'vis', which provide the stats for home team and visiting team of the game. Both are dictionaries with same structure. Each dictionary will contain team's information such as name of the team, their total wins/losses in current season, their conference standing, the SportSett ids for their current and previous games. Apart from these general information, they also have the box- and line- scores for the team in the game. Box score is the stats of players from the team at the end of the game, while line score along with the whole game stats is divided into quarters and halves as well as the extra-time (if happened in the game). After these scores, there is another field of next-game, which gives general information about team's next game such as the place and opponent's name of the next game.
224
+
225
+ 5. "summaries": This is a list of summaries for each game. Some games will have more than one summary, in that case, the list will have more than one entries. Each summary in the list is a string which can be tokenised by a space, following the practices in RotoWire-FG dataset ((Wang, 2019)[https://www.aclweb.org/anthology/W19-8639]).
226
+
227
+ #### Reason for Structure
228
+
229
+ <!-- info: How was the dataset structure determined? -->
230
+ <!-- scope: microscope -->
231
+ The structure mostly follows the original structure defined in RotoWire dataset ((Wiseman et. al. 2017)[https://aclanthology.org/D17-1239/]) with some modifications (such as game and next-game keys) address the problem of information gap between input and output data ((Thomson et. al. 2020)[https://aclanthology.org/2020.inlg-1.6/]).
232
+
233
+ #### How were labels chosen?
234
+
235
+ <!-- info: How were the labels chosen? -->
236
+ <!-- scope: microscope -->
237
+ Similar to RotoWire dataset ((Wiseman et. al. 2017)[https://aclanthology.org/D17-1239/])
238
+
239
+ #### Example Instance
240
+
241
+ <!-- info: Provide a JSON formatted example of a typical instance in the dataset. -->
242
+ <!-- scope: periscope -->
243
+ ```
244
  {
245
  "sportsett_id": "1",
246
  "gem_id": "GEM-sportsett_basketball-train-0",
 
1314
  "The Miami Heat ( 20 ) defeated the Philadelphia 76ers ( 0 - 3 ) 114 - 96 on Saturday . Chris Bosh scored a game - high 30 points to go with eight rebounds in 33 minutes . Josh McRoberts made his Heat debut after missing the entire preseason recovering from toe surgery . McRoberts came off the bench and played 11 minutes . Shawne Williams was once again the starter at power forward in McRoberts ' stead . Williams finished with 15 points and three three - pointers in 29 minutes . Mario Chalmers scored 18 points in 25 minutes off the bench . Luc Richard Mbah a Moute replaced Chris Johnson in the starting lineup for the Sixers on Saturday . Hollis Thompson shifted down to the starting shooting guard job to make room for Mbah a Moute . Mbah a Moute finished with nine points and seven rebounds in 19 minutes . K.J . McDaniels , who suffered a minor hip flexor injury in Friday 's game , was available and played 21 minutes off the bench , finishing with eight points and three blocks . Michael Carter-Williams is expected to be out until Nov. 13 , but Tony Wroten continues to put up impressive numbers in Carter-Williams ' absence . Wroten finished with a double - double of 21 points and 10 assists in 33 minutes . The Heat will complete a back - to - back set at home Sunday against the Tornoto Raptors . The Sixers ' next game is at home Monday against the Houston Rockets ."
1315
  ]
1316
  }
1317
+ ```
1318
 
1319
+ #### Data Splits
1320
 
1321
+ <!-- info: Describe and name the splits in the dataset if there are more than one. -->
1322
+ <!-- scope: periscope -->
1323
+ - Train: NBA seasons - 2014, 2015, & 2016; total instances - 3690
1324
+ - Validation: NBA seasons - 2017; total instances - 1230
1325
+ - Test: NBA seasons - 2018; total instances - 1230
1326
 
1327
+ #### Splitting Criteria
1328
 
1329
+ <!-- info: Describe any criteria for splitting the data, if used. If there are differences between the splits (e.g., if the training annotations are machine-generated and the dev and test ones are created by humans, or if different numbers of annotators contributed to each example), describe them here. -->
1330
+ <!-- scope: microscope -->
1331
+ The splits were created as per different NBA seasons. All the games in regular season (no play-offs) are added in the dataset
1332
 
 
1333
 
 
1334
 
1335
+ ## Dataset in GEM
1336
 
1337
+ ### Rationale for Inclusion in GEM
1338
 
1339
+ #### Why is the Dataset in GEM?
1340
 
1341
+ <!-- info: What does this dataset contribute toward better generation evaluation and why is it part of GEM? -->
1342
+ <!-- scope: microscope -->
1343
+ This dataset contains a data analytics problem in the classic sense ((Reiter, 2007)[https://aclanthology.org/W07-2315]). That is, there is a large amount of data from which insights need to be selected. Further, the insights should be both from simple shallow queries (such as dirext transcriptions of the properties of a subject, i.e., a player and their statistics), as well as aggregated (how a player has done over time). There is far more on the data side than is required to be realised, and indeed, could be practically realised. This depth of data analytics problem does not exist in other datasets.
1344
 
1345
+ #### Similar Datasets
1346
 
1347
+ <!-- info: Do other datasets for the high level task exist? -->
1348
+ <!-- scope: telescope -->
1349
+ no
1350
 
1351
+ #### Ability that the Dataset measures
1352
 
1353
+ <!-- info: What aspect of model ability can be measured with this dataset? -->
1354
+ <!-- scope: periscope -->
1355
+ Many, if not all aspects of data-to-text systems can be measured with this dataset. It has complex data analytics, meaninful document planning (10-15 sentence documents with a narrative structure), as well as microplanning and realisation requirements. Finding models to handle this volume of data, as well as methods for meaninfully evaluate generations is a very open question.
1356
 
 
1357
 
1358
+ ### GEM-Specific Curation
1359
 
1360
+ #### Modificatied for GEM?
1361
 
1362
+ <!-- info: Has the GEM version of the dataset been modified in any way (data, processing, splits) from the original curated data? -->
1363
+ <!-- scope: telescope -->
1364
+ no
1365
 
1366
+ #### Additional Splits?
1367
 
1368
+ <!-- info: Does GEM provide additional splits to the dataset? -->
1369
+ <!-- scope: telescope -->
1370
+ no
1371
+
1372
+
1373
+ ### Getting Started with the Task
1374
+
1375
+ #### Pointers to Resources
1376
+
1377
+ <!-- info: Getting started with in-depth research on the task. Add relevant pointers to resources that researchers can consult when they want to get started digging deeper into the task. -->
1378
+ <!-- scope: microscope -->
1379
  For dataset discussion see:
1380
  Thomson et al, 2020 https://aclanthology.org/2020.intellang-1.4/
1381
 
 
1389
 
1390
  For recent systems using the Rotowire dataset, see:
1391
  Puduppully & Lapata (2021): https://github.com/ratishsp/data2text-macro-plan-py
1392
+ Rebuffel et all (2020): https://github.com/KaijuML/data-to-text-hierarchical
1393
+
1394
+
1395
 
1396
+ ## Previous Results
1397
 
1398
+ ### Previous Results
1399
 
1400
+ #### Measured Model Abilities
1401
 
1402
+ <!-- info: What aspect of model ability can be measured with this dataset? -->
1403
+ <!-- scope: telescope -->
1404
+ Many, if not all aspects of data-to-text systems can be measured with this dataset. It has complex data analytics, meaninful document planning (10-15 sentence documents with a narrative structure), as well as microplanning and realisation requirements. Finding models to handle this volume of data, as well as methods for meaninfully evaluate generations is a very open question.
1405
 
1406
+ #### Metrics
1407
 
1408
+ <!-- info: What metrics are typically used for this task? -->
1409
+ <!-- scope: periscope -->
1410
+ `BLEU`
1411
 
1412
+ #### Proposed Evaluation
1413
 
1414
+ <!-- info: List and describe the purpose of the metrics and evaluation methodology (including human evaluation) that the dataset creators used when introducing this task. -->
1415
+ <!-- scope: microscope -->
1416
+ BLEU is the only off-the-shelf metric commonly used. Works have also used custom metrics like RG (Wiseman et al, 2017: https://aclanthology.org/D17-1239), and a recent shared task explored other metrics and their corrolation with human evaluation ((Thomson & Reiter, 2021)[https://aclanthology.org/2021.inlg-1.23]).
1417
 
1418
+ #### Previous results available?
1419
 
1420
+ <!-- info: Are previous results available? -->
1421
+ <!-- scope: telescope -->
1422
+ yes
1423
 
1424
+ #### Other Evaluation Approaches
1425
 
1426
+ <!-- info: What evaluation approaches have others used? -->
1427
+ <!-- scope: periscope -->
1428
  Most results from prior works use the original Rotowire dataset, which has train/validation/test contamination. For results of BLEU and RG on the relational database format of SportSett, as a guide, see Thomson et al, 2020:
1429
+ https://aclanthology.org/2020.inlg-1.6.
1430
 
1431
+ #### Relevant Previous Results
1432
 
1433
+ <!-- info: What are the most relevant previous results for this task/dataset? -->
1434
+ <!-- scope: microscope -->
1435
+ The results on this dataset are largely unexplored, as is the selection of suitable metrics that correlate with human judgment. See Thomson et al, 2021 (https://aclanthology.org/2021.inlg-1.23) for an overview, and Kasner et al (2021) for the best performing metric at the time of writing (https://aclanthology.org/2021.inlg-1.25).
1436
 
 
1437
 
 
1438
 
1439
+ ## Dataset Curation
1440
 
1441
+ ### Original Curation
1442
 
1443
+ #### Original Curation Rationale
1444
 
1445
+ <!-- info: Original curation rationale -->
1446
+ <!-- scope: telescope -->
1447
+ The references texts were taken from the existing dataset RotoWire-FG (Wang, 2019: https://www.aclweb.org/anthology/W19-8639), which is in turn based on Rotowire (Wiseman et al, 2017: https://aclanthology.org/D17-1239). The rationale behind this dataset was to re-structure the data such that aggregate statistics over multiple games, as well as upcoming game schedules could be included, moving the dataset from snapshots of single games, to a format where almost everything that could be present in the reference texts could be found in the data.
1448
 
1449
+ #### Communicative Goal
1450
 
1451
+ <!-- info: What was the communicative goal? -->
1452
+ <!-- scope: periscope -->
1453
+ Create a summary of a basketball, with insightful facts about the game, teams, and players, both within the game, withing periods during the game, and over the course of seasons/careers where appropriate. This is a data-to-text problem in the classic sense (Reiter, 2007: https://aclanthology.org/W07-2315) in that it has a difficult data analystics state, in addition to ordering and transcription of selected facts.
1454
 
1455
+ #### Sourced from Different Sources
1456
 
1457
+ <!-- info: Is the dataset aggregated from different data sources? -->
1458
+ <!-- scope: telescope -->
1459
+ yes
1460
+
1461
+ #### Source Details
1462
+
1463
+ <!-- info: List the sources (one per line) -->
1464
+ <!-- scope: periscope -->
1465
  RotoWire-FG (https://www.rotowire.com).
1466
  Wikipedia (https://en.wikipedia.org/wiki/Main_Page)
1467
  Basketball Reference (https://www.basketball-reference.com)
 
1468
 
 
1469
 
 
1470
 
1471
+ ### Language Data
1472
+
1473
+ #### How was Language Data Obtained?
1474
+
1475
+ <!-- info: How was the language data obtained? -->
1476
+ <!-- scope: telescope -->
1477
+ `Found`
1478
+
1479
+ #### Where was it found?
1480
+
1481
+ <!-- info: If found, where from? -->
1482
+ <!-- scope: telescope -->
1483
+ `Multiple websites`
1484
+
1485
+ #### Language Producers
1486
+
1487
+ <!-- info: What further information do we have on the language producers? -->
1488
+ <!-- scope: microscope -->
1489
+ None
1490
+
1491
+ #### Topics Covered
1492
+
1493
+ <!-- info: Does the language in the dataset focus on specific topics? How would you describe them? -->
1494
+ <!-- scope: periscope -->
1495
+ Summaries of basketball games (in the NBA).
1496
+
1497
+ #### Data Validation
1498
+
1499
+ <!-- info: Was the text validated by a different worker or a data curator? -->
1500
+ <!-- scope: telescope -->
1501
+ not validated
1502
+
1503
+ #### Data Preprocessing
1504
+
1505
+ <!-- info: How was the text data pre-processed? (Enter N/A if the text was not pre-processed) -->
1506
+ <!-- scope: microscope -->
1507
+ It retains the original tokenization scheme employed by Wang 2019
1508
+
1509
+ #### Was Data Filtered?
1510
+
1511
+ <!-- info: Were text instances selected or filtered? -->
1512
+ <!-- scope: telescope -->
1513
+ manually
1514
+
1515
+ #### Filter Criteria
1516
 
1517
+ <!-- info: What were the selection criteria? -->
1518
+ <!-- scope: microscope -->
1519
+ Games from the 2014 through 2018 seasons were selected. Within these seasons games are not filtered, all are present, but this was an arbitrary solution from the original RotoWirte-FG dataset.
1520
 
 
1521
 
1522
+ ### Structured Annotations
1523
 
1524
+ #### Additional Annotations?
1525
 
1526
+ <!-- quick -->
1527
+ <!-- info: Does the dataset have additional annotations for each instance? -->
1528
+ <!-- scope: telescope -->
1529
+ none
1530
 
1531
+ #### Annotation Service?
1532
 
1533
+ <!-- info: Was an annotation service used? -->
1534
+ <!-- scope: telescope -->
1535
+ no
1536
 
 
1537
 
1538
+ ### Consent
1539
 
1540
+ #### Any Consent Policy?
1541
 
1542
+ <!-- info: Was there a consent policy involved when gathering the data? -->
1543
+ <!-- scope: telescope -->
1544
+ no
1545
 
1546
+ #### Justification for Using the Data
1547
 
1548
+ <!-- info: If not, what is the justification for reusing the data? -->
1549
+ <!-- scope: microscope -->
1550
+ The dataset consits of a pre-existing dataset, as well as publically available facts.
1551
 
 
1552
 
1553
+ ### Private Identifying Information (PII)
1554
 
1555
+ #### Contains PII?
1556
 
1557
+ <!-- quick -->
1558
+ <!-- info: Does the source language data likely contain Personal Identifying Information about the data creators or subjects? -->
1559
+ <!-- scope: telescope -->
1560
+ unlikely
1561
 
1562
+ #### Categories of PII
1563
 
1564
+ <!-- info: What categories of PII are present or suspected in the data? -->
1565
+ <!-- scope: periscope -->
1566
+ `generic PII`
1567
 
1568
+ #### Any PII Identification?
1569
 
1570
+ <!-- info: Did the curators use any automatic/manual method to identify PII in the dataset? -->
1571
+ <!-- scope: periscope -->
1572
+ no identification
1573
 
 
1574
 
1575
+ ### Maintenance
1576
 
1577
+ #### Any Maintenance Plan?
1578
 
1579
+ <!-- info: Does the original dataset have a maintenance plan? -->
1580
+ <!-- scope: telescope -->
1581
+ no
1582
 
 
1583
 
 
1584
 
1585
+ ## Broader Social Context
1586
 
1587
+ ### Previous Work on the Social Impact of the Dataset
1588
 
1589
+ #### Usage of Models based on the Data
1590
 
1591
+ <!-- info: Are you aware of cases where models trained on the task featured in this dataset ore related tasks have been used in automated systems? -->
1592
+ <!-- scope: telescope -->
1593
+ no
1594
 
 
1595
 
1596
+ ### Impact on Under-Served Communities
1597
 
1598
+ #### Addresses needs of underserved Communities?
1599
 
1600
+ <!-- info: Does this dataset address the needs of communities that are traditionally underserved in language technology, and particularly language generation technology? Communities may be underserved for exemple because their language, language variety, or social or geographical context is underepresented in NLP and NLG resources (datasets and models). -->
1601
+ <!-- scope: telescope -->
1602
+ no
1603
 
 
1604
 
1605
+ ### Discussion of Biases
1606
 
1607
+ #### Any Documented Social Biases?
1608
 
1609
+ <!-- info: Are there documented social biases in the dataset? Biases in this context are variations in the ways members of different social categories are represented that can have harmful downstream consequences for members of the more disadvantaged group. -->
1610
+ <!-- scope: telescope -->
1611
+ yes
1612
 
1613
+ #### Links and Summaries of Analysis Work
1614
 
1615
+ <!-- info: Provide links to and summaries of works analyzing these biases. -->
1616
+ <!-- scope: microscope -->
1617
+ Unaware of any work, but, this is a dataset considting solely of summaries of mens professional basketball games. It does not cover different levels of the sport, or different genders, and all pronouns are likely to be male unless a specific player is referred to by other pronouns in the training text. This makes it difficult to train systems where gender can be specified as an attribute, although it is an interesting, open problem that could be investigated using the dataset.
1618
 
1619
+ #### Are the Language Producers Representative of the Language?
1620
 
1621
+ <!-- info: Does the distribution of language producers in the dataset accurately represent the full distribution of speakers of the language world-wide? If not, how does it differ? -->
1622
+ <!-- scope: periscope -->
1623
+ No, it is very specifically American English from the sports journalism domain.
1624
 
 
1625
 
 
1626
 
1627
+ ## Considerations for Using the Data
1628
 
1629
+ ### PII Risks and Liability
1630
 
1631
+ #### Potential PII Risk
1632
 
1633
+ <!-- info: Considering your answers to the PII part of the Data Curation Section, describe any potential privacy to the data subjects and creators risks when using the dataset. -->
1634
+ <!-- scope: microscope -->
1635
+ All information relating to persons is of public record.
1636
 
 
1637
 
1638
+ ### Licenses
1639
 
1640
+ #### Copyright Restrictions on the Dataset
1641
 
1642
+ <!-- info: Based on your answers in the Intended Use part of the Data Overview Section, which of the following best describe the copyright and licensing status of the dataset? -->
1643
+ <!-- scope: periscope -->
1644
+ `public domain`
1645
 
1646
+ #### Copyright Restrictions on the Language Data
1647
 
1648
+ <!-- info: Based on your answers in the Language part of the Data Curation Section, which of the following best describe the copyright and licensing status of the underlying language data? -->
1649
+ <!-- scope: periscope -->
1650
+ `public domain`
1651
 
 
1652
 
1653
+ ### Known Technical Limitations
1654
 
1655
+ #### Technical Limitations
1656
 
1657
+ <!-- info: Describe any known technical limitations, such as spurrious correlations, train/test overlap, annotation biases, or mis-annotations, and cite the works that first identified these limitations when possible. -->
1658
+ <!-- scope: microscope -->
1659
+ SportSett resolved the major overlap problems of RotoWire, although some overlap is unavoidable. For example, whilst it is not possible to find career totals and other historic information for all players (the data only goes back to 2014), it is possible to do so for some players. It is unavoidable that some data which is aggregated, exists in its base form in previous partitions. The season-based partition scheme heavily constrains this however.
1660
 
1661
+ #### Unsuited Applications
1662
 
1663
+ <!-- info: When using a model trained on this dataset in a setting where users or the public may interact with its predictions, what are some pitfalls to look out for? In particular, describe some applications of the general task featured in this dataset that its curation or properties make it less suitable for. -->
1664
+ <!-- scope: microscope -->
1665
+ Factual accuray continues to be a problem, systems may incorrectly represent the facts of the game.
1666
 
1667
+ #### Discouraged Use Cases
1668
 
1669
+ <!-- info: What are some discouraged use cases of a model trained to maximize the proposed metrics on this dataset? In particular, think about settings where decisions made by a model that performs reasonably well on the metric my still have strong negative consequences for user or members of the public. -->
1670
+ <!-- scope: microscope -->
1671
+ Using the RG metric to maximise the number of true facts in a generate summary is not nececeraly
1672
 
 
1673