Create README.md
Browse filesfirst version of README
README.md
ADDED
@@ -0,0 +1,79 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
---
|
2 |
+
languages:
|
3 |
+
- en
|
4 |
+
licenses:
|
5 |
+
- unknown
|
6 |
+
multilinguality:
|
7 |
+
- monolingual
|
8 |
+
size_categories:
|
9 |
+
- 10K<n<100K
|
10 |
+
---
|
11 |
+
|
12 |
+
# Dataset Card for CLUTRR
|
13 |
+
|
14 |
+
## Table of Contents
|
15 |
+
|
16 |
+
## Dataset Description
|
17 |
+
### Dataset Summary
|
18 |
+
**CLUTRR** (**C**ompositional **L**anguage **U**nderstanding and **T**ext-based **R**elational **R**easoning), a diagnostic benchmark suite, is first introduced in (https://arxiv.org/abs/1908.06177) to test the systematic generalization and inductive reasoning capabilities of NLU systems.
|
19 |
+
|
20 |
+
The CLUTRR benchmark allows us to test a model’s ability for **systematic generalization** by testing on stories that contain unseen combinations of logical rules, and test for the various forms of **model robustness** by adding different kinds of superfluous noise facts to the stories.
|
21 |
+
|
22 |
+
### Dataset Task
|
23 |
+
CLUTRR contains a large set of semi-synthetic stories involving hypothetical families. The task is to infer the relationship between two family members, whose relationship is not explicitly mentioned in the given story.
|
24 |
+
|
25 |
+
## Dataset Structure
|
26 |
+
We show detailed information for all 17 configurations of the dataset.
|
27 |
+
|
28 |
+
### configurations:
|
29 |
+
**id**: a unique series of characters and numbers that identify each instance <br>
|
30 |
+
**story**: one semi-synthetic story involving hypothetical families<br>
|
31 |
+
**query**: the target query/relation which contains two names, where the goal is to classify the relation that holds between these two entities<br>
|
32 |
+
**text\_query**: <br>
|
33 |
+
**target**: correct relation for the query <br>
|
34 |
+
(the following kin-ship relations are used: son, father, husband, brother, grandson, grandfather, son-in-law, father-in-law, brother-in-law, uncle, nephew, daughter, mother, wife, sister, granddaughter, grandmother, daughter-in-law, mother-in-law, sister-in-law, aunt, niece.)<br>
|
35 |
+
**text\_target**: <br>
|
36 |
+
**clean\_story**: <br>
|
37 |
+
**proof\_state**: the logical rule of the kinship generation <br>
|
38 |
+
**f\_comb**: the kinships of the query followed by the logical rule<br>
|
39 |
+
**task\_name**: the task of the sub-dataset in a form of "task_[num1].[num2]"<br>
|
40 |
+
The first number [num1] indicates the status of noise facts added in the story: 1- no noise facts; 2- Irrelevant facts*; 3- Supporting facts*; 4- Disconnected facts*.<br>
|
41 |
+
The second number [num2] directly indicates the length of clauses for the task target.<br>
|
42 |
+
*for example:*<br>
|
43 |
+
*task_1.2 -- task requiring clauses of length 2 without adding noise facts*<br>
|
44 |
+
*task_2.3 -- task requiring clauses of length 3 with Irrelevant noise facts added in the story*<br>
|
45 |
+
**story\_edges**: all the edges in the kinship graph<br>
|
46 |
+
**edge\_types**: similar to the f\_comb, another form of the query's kinships followed by the logical rule <br>
|
47 |
+
**query\_edge**: the corresponding edge of the target query in the kinship graph<br>
|
48 |
+
**genders**: genders of names appeared in the story<br>
|
49 |
+
**syn\_story**: <br>
|
50 |
+
**node\_mapping**: <br>
|
51 |
+
**task\_split**: train,test <br>
|
52 |
+
|
53 |
+
*Further explanation of Irrelevant facts, Supporting facts and Disconnected facts can be found in the 3.5 Robust Reasoning section in https://arxiv.org/abs/1908.06177
|
54 |
+
|
55 |
+
### Data Instances
|
56 |
+
|
57 |
+
An example of 'train'in Task 1.2 looks as follows.
|
58 |
+
```
|
59 |
+
{
|
60 |
+
"id": b2b9752f-d7fa-46a9-83ae-d474184c35b6,
|
61 |
+
"story": "[Lillian] and her daughter [April] went to visit [Lillian]'s mother [Ashley] last Sunday.",
|
62 |
+
"query": ('April', 'Ashley'),
|
63 |
+
"text_query": ,
|
64 |
+
"target": "grandmother",
|
65 |
+
"text_target": ['[Ashley] has a granddaughter called [April] who is her favourite.'],
|
66 |
+
"clean_story": [Lillian] and her daughter [April] went to visit [Lillian]'s mother [Ashley] last Sunday.,
|
67 |
+
"proof_state": [{('April', 'grandmother', 'Ashley'): [('April', 'mother', 'Lillian'), ('Lillian', 'mother', 'Ashley')]}],
|
68 |
+
"f_comb": "mother-mother",
|
69 |
+
"task_name": "task_1.2",
|
70 |
+
"story_edges": [(0, 1), (1, 2)],
|
71 |
+
"edge_types": ['mother', 'mother'],
|
72 |
+
"query_edge": (0, 2),
|
73 |
+
"genders": "April:female,Lillian:female,Ashley:female";
|
74 |
+
"syn_story": ,
|
75 |
+
"node_mapping": {7: 0, 2: 1, 1: 2},
|
76 |
+
"task_split": trian
|
77 |
+
}
|
78 |
+
```
|
79 |
+
|