Datasets:
GEM
/

Languages:
Finnish
Multilinguality:
unknown
Size Categories:
unknown
Language Creators:
unknown
Annotations Creators:
expert-created
Source Datasets:
original
Tags:
data-to-text
License:
Sebastian Gehrmann commited on
Commit
30c9202
1 Parent(s): 03bea7a
Files changed (1) hide show
  1. turku_hockey_data2text.json +9 -6
turku_hockey_data2text.json CHANGED
@@ -4,10 +4,10 @@
4
  "has-leaderboard": "no",
5
  "leaderboard-url": "N/A",
6
  "leaderboard-description": "N/A",
7
- "website": "https://turkunlp.org/hockey_data2text.html",
8
- "data-url": "https://github.com/TurkuNLP/Turku-hockey-data2text",
9
- "paper-url": "https://aclanthology.org/W19-6125/",
10
- "paper-bibtext": "@inproceedings{kanerva2019newsgen,\n Title = {Template-free Data-to-Text Generation of Finnish Sports News},\n Author = {Jenna Kanerva and Samuel R{\\\"o}nnqvist and Riina Kekki and Tapio Salakoski and Filip Ginter},\n booktitle = {Proceedings of the 22nd Nordic Conference on Computational Linguistics (NoDaLiDa\u201919)},\n year={2019}\n }",
11
  "contact-name": "Jenna Kanerva, Filip Ginter",
12
  "contact-email": "jmnybl@utu.fi, figint@utu.fi"
13
  },
@@ -36,9 +36,12 @@
36
  },
37
  "structure": {
38
  "data-fields": "The dataset is constructed of games, where each game is a list of events. If the event was annotated (corresponding sentence was found from the news article), it includes `text` field with value other than empty string (\"\").\n\nFor each game (dict), there are keys `gem_id` (string), `id` (string), `news_article` (string), and `events` (list).\n\nFor each event (dict), there are different, relevant keys available with non empty values depending on the event type (e.g. goal or penalty). The mandatory keys for each event are `event_id` (string), `event_type` (string), `text` (string, empty string if not annotated), and `multi_reference` (bool). The keys not relevant for the specific event type are left empty.\n\nThe relevant keys in the event dictionary are:\n\nFor each event type, the following keys are relevant:\n `event_id`: Identifier of the event, unique to the game but not globally, in chronological order (string)\n `event_type`: Type of the event, possible values are `game result`, `goal`, `penalty`, or `saves` (string)\n `text`: Natural language description of the event, or empty string if not available (string)\n `multi_reference`: Does this event refer to a text passage describing multiple events? (bool)\n\n\nThe rest of the fields are specific to the event type. The relevant fields for each event type are:\n\ngame result:\n `event_id`: Identifier of the event, unique to the game but not globally, in chronological order (string)\n `event_type`: Type of the event (string)\n `home_team`: Name of the home team (string)\n `guest_team`: Name of the guest team (string)\n `score`: Final score of the game, in the form of home\u2013guest (string)\n `periods`: Scores for individual periods, each in the form of home\u2013guest score in that period (list of strings)\n `features`: Additional features, such as overtime win or shoot out (list of strings)\n `text`: Natural language description of the event, or empty string if not available (string)\n `multi_reference`: Does this event refer to a text passage describing multiple events? (bool)\n\ngoal:\n `event_id`: Identifier of the event, unique to the game but not globally, in chronological order (string)\n `event_type`: Type of the event (string)\n `player`: Name of the player scoring (string)\n `assist`: Names of the players assisting, at most two players (list of strings)\n `team`: Team scoring with possible values of `home` or `guest` (string)\n `team_name`: Name of the team scoring (string)\n `score`: Score after the goal, in the form of home\u2013guest (string)\n `time`: Time of the goal, minutes and seconds from the beginning (string)\n `features`: Additional features, such as power play or short-handed goal (list of strings)\n `text`: Natural language description of the event, or empty string if not available (string)\n `multi_reference`: Does this event refer to a text passage describing multiple events? (bool)\n\npenalty:\n `event_id`: Identifier of the event, unique to the game but not globally, in chronological order (string)\n `event_type`: Type of the event (string)\n `player`: Name of the player getting the penalty (string)\n `team`: Team getting the penalty with possible values of `home` or `guest` (string)\n `team_name`: Name of the team getting the penalty (string)\n `penalty_minutes`: Penalty minutes (string)\n `time`: Time of the penalty, minutes and seconds from the beginning (string)\n `text`: Natural language description of the event, or empty string if not available (string)\n `multi_reference`: Does this event refer to a text passage describing multiple events? (bool)\n\nsaves:\n `event_id`: Identifier of the event, unique to the game but not globally, in chronological order (string)\n `event_type`: Type of the event (string)\n `player`: Name of the goalkeeper (string)\n `team`: Team of the goalkeeper with possible values of `home` or `guest` (string)\n `team_name`: Name of the team (string)\n `saves`: Number of saves in the game (string)\n `text`: Natural language description of the event, or empty string if not available (string)\n `multi_reference`: Does this event refer to a text passage describing multiple events? (bool)\n\n\nText passages describing multiple events (multi_reference):\n\nSome text passages refer to multiple events in such way that separating them to individual statements is not adequate (e.g. \"The home team received two penalties towards the end of the first period.\"). In these cases, multiple events are aligned to the same text passage so that the first event (in chronological order) include the annotated text passage, while the rest of the events referring to the same text passage include the identifier of the first event in the annotated text field (e.g. `text`: \"E4\").",
39
- "structure-example": "{\n 'gem_id': 'gem-turku_hockey_data2text-train-0',\n 'id': '20061031-TPS-HPK',\n 'news_article': 'HPK:n hyv\u00e4 syysvire jatkuu j\u00e4\u00e4kiekon SM-liigassa. Tiistaina HPK kukisti mainiolla liikkeell\u00e4 ja tehokkaalla ylivoimapelill\u00e4 TPS:n vieraissa 1\u20130 (1\u20130, 0\u20130, 0\u20130).\\nHPK hy\u00f6dynsi ylivoimaa mennen jo ensimm\u00e4isess\u00e4 er\u00e4ss\u00e4 Mikko M\u00e4enp\u00e4\u00e4n maalilla 1\u20130 -johtoon.\\nToisessa ja kolmannessa er\u00e4ss\u00e4 HPK tarjosi edelleen TPS:lle runsaasti tilanteita, mutta maalia eiv\u00e4t turkulaiset mill\u00e4\u00e4n ilveell\u00e4 saaneet. Pahin este oli loistavan pelin H\u00e4meenlinnan maalilla pelannut Mika Oksa.\\nTPS:n maalissa Jani Hurme ei osumille mit\u00e4\u00e4n mahtanut. Joukkueen suuri yksin\u00e4inen kentt\u00e4pelaaja oli Kai Nurminen, mutta h\u00e4nell\u00e4k\u00e4\u00e4n ei ollut onnea maalitilanteissa.',\n 'events':\n {\n 'event_id': ['E1', 'E2', 'E3'],\n 'event_type': ['game result', 'penalty', 'goal'],\n 'text': ['HPK kukisti TPS:n vieraissa 1\u20130 (1\u20130, 0\u20130, 0\u20130).', '', 'HPK hy\u00f6dynsi ylivoimaa mennen jo ensimm\u00e4isess\u00e4 er\u00e4ss\u00e4 Mikko M\u00e4enp\u00e4\u00e4n maalilla 1\u20130 -johtoon.'],\n 'home_team': ['TPS', '', ''],\n 'guest_team': ['HPK', '', ''],\n 'score': ['0\u20131', '', '0\u20131'],\n 'periods': [['0\u20131', '0\u20130', '0\u20130'], [], []],\n 'features': [[], [], ['power play']],\n 'player': ['', 'Fredrik Svensson', 'Mikko M\u00e4enp\u00e4\u00e4'],\n 'assist': [[], [], ['Jani Kein\u00e4nen', 'Toni M\u00e4kiaho']],\n 'team': ['', 'guest', 'guest'],\n 'team_name': ['', 'HPK', 'HPK'],\n 'time': ['', '9.28', '14.57'],\n 'penalty_minutes': ['', '2', ''],\n 'saves': ['', '', ''],\n 'multi_reference': [false, false, false]\n }\n}",
40
  "structure-splits": "The corpus include 3 splits: train, validation, and test.",
41
  "structure-description": ""
 
 
 
42
  }
43
  },
44
  "curation": {
@@ -168,4 +171,4 @@
168
  "speaker-distibution": "The dataset represents only written standard language. "
169
  }
170
  }
171
- }
 
4
  "has-leaderboard": "no",
5
  "leaderboard-url": "N/A",
6
  "leaderboard-description": "N/A",
7
+ "website": "[Website](https://turkunlp.org/hockey_data2text.html)",
8
+ "data-url": "[Github](https://github.com/TurkuNLP/Turku-hockey-data2text)",
9
+ "paper-url": "[ACL anthology](https://aclanthology.org/W19-6125/)",
10
+ "paper-bibtext": "```\n@inproceedings{kanerva2019newsgen,\n Title = {Template-free Data-to-Text Generation of Finnish Sports News},\n Author = {Jenna Kanerva and Samuel R{\\\"o}nnqvist and Riina Kekki and Tapio Salakoski and Filip Ginter},\n booktitle = {Proceedings of the 22nd Nordic Conference on Computational Linguistics (NoDaLiDa\u201919)},\n year={2019}\n }\n```",
11
  "contact-name": "Jenna Kanerva, Filip Ginter",
12
  "contact-email": "jmnybl@utu.fi, figint@utu.fi"
13
  },
 
36
  },
37
  "structure": {
38
  "data-fields": "The dataset is constructed of games, where each game is a list of events. If the event was annotated (corresponding sentence was found from the news article), it includes `text` field with value other than empty string (\"\").\n\nFor each game (dict), there are keys `gem_id` (string), `id` (string), `news_article` (string), and `events` (list).\n\nFor each event (dict), there are different, relevant keys available with non empty values depending on the event type (e.g. goal or penalty). The mandatory keys for each event are `event_id` (string), `event_type` (string), `text` (string, empty string if not annotated), and `multi_reference` (bool). The keys not relevant for the specific event type are left empty.\n\nThe relevant keys in the event dictionary are:\n\nFor each event type, the following keys are relevant:\n `event_id`: Identifier of the event, unique to the game but not globally, in chronological order (string)\n `event_type`: Type of the event, possible values are `game result`, `goal`, `penalty`, or `saves` (string)\n `text`: Natural language description of the event, or empty string if not available (string)\n `multi_reference`: Does this event refer to a text passage describing multiple events? (bool)\n\n\nThe rest of the fields are specific to the event type. The relevant fields for each event type are:\n\ngame result:\n `event_id`: Identifier of the event, unique to the game but not globally, in chronological order (string)\n `event_type`: Type of the event (string)\n `home_team`: Name of the home team (string)\n `guest_team`: Name of the guest team (string)\n `score`: Final score of the game, in the form of home\u2013guest (string)\n `periods`: Scores for individual periods, each in the form of home\u2013guest score in that period (list of strings)\n `features`: Additional features, such as overtime win or shoot out (list of strings)\n `text`: Natural language description of the event, or empty string if not available (string)\n `multi_reference`: Does this event refer to a text passage describing multiple events? (bool)\n\ngoal:\n `event_id`: Identifier of the event, unique to the game but not globally, in chronological order (string)\n `event_type`: Type of the event (string)\n `player`: Name of the player scoring (string)\n `assist`: Names of the players assisting, at most two players (list of strings)\n `team`: Team scoring with possible values of `home` or `guest` (string)\n `team_name`: Name of the team scoring (string)\n `score`: Score after the goal, in the form of home\u2013guest (string)\n `time`: Time of the goal, minutes and seconds from the beginning (string)\n `features`: Additional features, such as power play or short-handed goal (list of strings)\n `text`: Natural language description of the event, or empty string if not available (string)\n `multi_reference`: Does this event refer to a text passage describing multiple events? (bool)\n\npenalty:\n `event_id`: Identifier of the event, unique to the game but not globally, in chronological order (string)\n `event_type`: Type of the event (string)\n `player`: Name of the player getting the penalty (string)\n `team`: Team getting the penalty with possible values of `home` or `guest` (string)\n `team_name`: Name of the team getting the penalty (string)\n `penalty_minutes`: Penalty minutes (string)\n `time`: Time of the penalty, minutes and seconds from the beginning (string)\n `text`: Natural language description of the event, or empty string if not available (string)\n `multi_reference`: Does this event refer to a text passage describing multiple events? (bool)\n\nsaves:\n `event_id`: Identifier of the event, unique to the game but not globally, in chronological order (string)\n `event_type`: Type of the event (string)\n `player`: Name of the goalkeeper (string)\n `team`: Team of the goalkeeper with possible values of `home` or `guest` (string)\n `team_name`: Name of the team (string)\n `saves`: Number of saves in the game (string)\n `text`: Natural language description of the event, or empty string if not available (string)\n `multi_reference`: Does this event refer to a text passage describing multiple events? (bool)\n\n\nText passages describing multiple events (multi_reference):\n\nSome text passages refer to multiple events in such way that separating them to individual statements is not adequate (e.g. \"The home team received two penalties towards the end of the first period.\"). In these cases, multiple events are aligned to the same text passage so that the first event (in chronological order) include the annotated text passage, while the rest of the events referring to the same text passage include the identifier of the first event in the annotated text field (e.g. `text`: \"E4\").",
39
+ "structure-example": "```\n{\n 'gem_id': 'gem-turku_hockey_data2text-train-0',\n 'id': '20061031-TPS-HPK',\n 'news_article': 'HPK:n hyv\u00e4 syysvire jatkuu j\u00e4\u00e4kiekon SM-liigassa. Tiistaina HPK kukisti mainiolla liikkeell\u00e4 ja tehokkaalla ylivoimapelill\u00e4 TPS:n vieraissa 1\u20130 (1\u20130, 0\u20130, 0\u20130).\\nHPK hy\u00f6dynsi ylivoimaa mennen jo ensimm\u00e4isess\u00e4 er\u00e4ss\u00e4 Mikko M\u00e4enp\u00e4\u00e4n maalilla 1\u20130 -johtoon.\\nToisessa ja kolmannessa er\u00e4ss\u00e4 HPK tarjosi edelleen TPS:lle runsaasti tilanteita, mutta maalia eiv\u00e4t turkulaiset mill\u00e4\u00e4n ilveell\u00e4 saaneet. Pahin este oli loistavan pelin H\u00e4meenlinnan maalilla pelannut Mika Oksa.\\nTPS:n maalissa Jani Hurme ei osumille mit\u00e4\u00e4n mahtanut. Joukkueen suuri yksin\u00e4inen kentt\u00e4pelaaja oli Kai Nurminen, mutta h\u00e4nell\u00e4k\u00e4\u00e4n ei ollut onnea maalitilanteissa.',\n 'events':\n {\n 'event_id': ['E1', 'E2', 'E3'],\n 'event_type': ['game result', 'penalty', 'goal'],\n 'text': ['HPK kukisti TPS:n vieraissa 1\u20130 (1\u20130, 0\u20130, 0\u20130).', '', 'HPK hy\u00f6dynsi ylivoimaa mennen jo ensimm\u00e4isess\u00e4 er\u00e4ss\u00e4 Mikko M\u00e4enp\u00e4\u00e4n maalilla 1\u20130 -johtoon.'],\n 'home_team': ['TPS', '', ''],\n 'guest_team': ['HPK', '', ''],\n 'score': ['0\u20131', '', '0\u20131'],\n 'periods': [['0\u20131', '0\u20130', '0\u20130'], [], []],\n 'features': [[], [], ['power play']],\n 'player': ['', 'Fredrik Svensson', 'Mikko M\u00e4enp\u00e4\u00e4'],\n 'assist': [[], [], ['Jani Kein\u00e4nen', 'Toni M\u00e4kiaho']],\n 'team': ['', 'guest', 'guest'],\n 'team_name': ['', 'HPK', 'HPK'],\n 'time': ['', '9.28', '14.57'],\n 'penalty_minutes': ['', '2', ''],\n 'saves': ['', '', ''],\n 'multi_reference': [false, false, false]\n }\n}\n```",
40
  "structure-splits": "The corpus include 3 splits: train, validation, and test.",
41
  "structure-description": ""
42
+ },
43
+ "what": {
44
+ "dataset": "This is a Finnish data-to-text dataset in which the input is structured information about a hockey game and the output a description of the game."
45
  }
46
  },
47
  "curation": {
 
171
  "speaker-distibution": "The dataset represents only written standard language. "
172
  }
173
  }
174
+ }