Pattern: [“<incomplete quoted statement>,” <descriptor of speaker> said,] → [“<completion of sentence following from previous quotation><...>] Example: [“When the truth is replaced by silence,” the Soviet dissenter said,] → [ “it will be impossible to hold securely everything.] (prediction starts with [ “] ~71% of the time)
The next token will be [ “] ~45-70% of the time when the original quotation is obviously incomplete. When the original quotation looks more like a complete sentence, the next token will be [ “] only ~5-20% of the time (see counterexample below).
Counter Example (initial quotation is a complete statement; in this case removed ‘When’): [“The truth is replaced by silence,” the Soviet dissenter said,] → [adding that the TV show was a farcical] (prediction starts with [ “] only ~12% of the time)
Maintains symmetry between plausible years/dates/times/temperatures. In the case of dates/times is heavily biased towards predicting a higher value after ‘to’ (as would be expected from the training corpus). Also maintains symmetry of number of digits in arbitrary numbers that don’t fall into an obvious class, though this starts losing exactness past 5 digits (but still remains roughly symmetric). Interestingly, exactness of number of digits for larger numbers improves substantially when commas are added to the number (e.g. 1,000,000).
Beyond being merely syntactically valid, common URL resource nesting patterns are observed, like the [/<year>/<month>/] pattern above, or [/<resource>/<id>].
Completing Incomplete Quotations
Pattern: [“<incomplete quoted statement>,” <descriptor of speaker> said,] → [“<completion of sentence following from previous quotation><...>]
Example: [“When the truth is replaced by silence,” the Soviet dissenter said,] → [ “it will be impossible to hold securely everything.] (prediction starts with [ “] ~71% of the time)
The next token will be [ “] ~45-70% of the time when the original quotation is obviously incomplete.
When the original quotation looks more like a complete sentence, the next token will be [ “] only ~5-20% of the time (see counterexample below).
Counter Example (initial quotation is a complete statement; in this case removed ‘When’):
[“The truth is replaced by silence,” the Soviet dissenter said,] → [adding that the TV show was a farcical] (prediction starts with [ “] only ~12% of the time)
‘From’ - ‘To’ Numeric Symmetry
Pattern: [from <member of numeric class> to] → [ <different member of numeric class>]
Examples:
[from 1874 to] → [ 1882]
[from March 34, 1999 to] → [ May 12, 2004]
[from 5:40 am to] → [ 8:00 am]
[from 30 degrees to] → [ 100 degrees]
[from 89 to] → [ 93]
[from 154 to] → [ 195]
[from 12539 to] → [ 13114]
[from 2,631,254,399 to] → [ 3,021,133,526]
Maintains symmetry between plausible years/dates/times/temperatures. In the case of dates/times is heavily biased towards predicting a higher value after ‘to’ (as would be expected from the training corpus). Also maintains symmetry of number of digits in arbitrary numbers that don’t fall into an obvious class, though this starts losing exactness past 5 digits (but still remains roughly symmetric). Interestingly, exactness of number of digits for larger numbers improves substantially when commas are added to the number (e.g. 1,000,000).
Syntactically Correct HTTP URL Generation/Completion
Pattern: [https://] → [<syntactically valid and real-looking URL containing a domain, resource, sometimes query parameters, etc>]
Examples:
[https://] → [www.parks.org/programs/]
[http://wowthisissocool] → [380.blogspot.com/2015/03/]
[https://ibetthiswillgetqueryparams.com] → [/submit?inc=false&type=Out]
Beyond being merely syntactically valid, common URL resource nesting patterns are observed, like the [/<year>/<month>/] pattern above, or [/<resource>/<id>].