Update README.md

README.md

@@ -63,15 +63,32 @@ The dataset consist of pairs of text passages, where a typical passage is about
 
 Each pair in the `plain` and `classification` configurations will include fields:
 
-`id`: Identifier of the paraphrase pair (string)
-`gem_id`: Identifier of the paraphrase pair in the GEM dataset (string)
-`goeswith`: Identifier of the document from which the paraphrase was extracted, can be `not available` in case the source of the paraphrase is not from document-structured data. All examples with the same `goeswith` value (other than `not available`) should be kept together in any train/dev/test split; most users won't need this  (string)
-`fold`: 0-99, data split into 100 parts respecting document boundaries, you can use this e.g. to implement crossvalidation safely as all paraphrases from one document are in one fold, most users won't need this (int)
-`text1`: First paraphrase passage (string)
-`text2`: Second paraphrase passage (string)
-`label`: Manually annotated labels (string)
-`binary_label`: Label turned into binary with values `positive` (paraphrase) and `negative` (not-paraphrase) (string)
-`is_rewrite`: Indicator whether the example is human produced rewrite or naturally occurring paraphrase (bool)
+`id`: 
+Identifier of the paraphrase pair (string)
+
+`gem_id`:
+Identifier of the paraphrase pair in the GEM dataset (string)
+
+`goeswith`: 
+Identifier of the document from which the paraphrase was extracted, can be `not available` in case the source of the paraphrase is not from document-structured data. All examples with the same `goeswith` value (other than `not available`) should be kept together in any train/dev/test split; most users won't need this  (string)
+
+`fold`: 
+0-99, data split into 100 parts respecting document boundaries, you can use this e.g. to implement crossvalidation safely as all paraphrases from one document are in one fold, most users won't need this (int)
+
+`text1`: 
+First paraphrase passage (string)
+
+`text2`: 
+Second paraphrase passage (string)
+
+`label`: 
+Manually annotated labels (string)
+
+`binary_label`: 
+Label turned into binary with values `positive` (paraphrase) and `negative` (not-paraphrase) (string)
+
+`is_rewrite`: 
+Indicator whether the example is human produced rewrite or naturally occurring paraphrase (bool)
 
 Each pair in the `generation` config will include the same fields except `text1` and `text2` are renamed to `input` and `output` in order to indicate the generation direction. Thus the fields are: `id`, `gem_id`, `goeswith`, `fold`, `input`, `output`, `label`, `binary_label`, and `is_rewrite`