File size: 94,073 Bytes
6fa4bc9 |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959 960 961 962 963 964 965 966 967 968 969 970 971 972 973 974 975 976 977 978 979 980 981 982 983 984 985 986 987 988 989 990 991 992 993 994 995 996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 1134 1135 1136 1137 1138 1139 1140 1141 1142 1143 1144 1145 1146 1147 1148 1149 1150 1151 1152 1153 1154 1155 1156 1157 1158 1159 1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194 1195 1196 1197 1198 1199 1200 1201 1202 1203 1204 1205 1206 1207 1208 1209 1210 1211 1212 1213 1214 1215 1216 1217 1218 1219 1220 1221 1222 1223 1224 1225 1226 1227 1228 1229 1230 1231 1232 1233 1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252 1253 1254 1255 1256 1257 1258 1259 1260 1261 1262 1263 1264 1265 1266 1267 1268 1269 1270 1271 1272 1273 1274 1275 1276 1277 1278 1279 1280 1281 1282 1283 1284 1285 1286 1287 1288 1289 1290 1291 1292 1293 1294 1295 1296 1297 1298 1299 1300 1301 1302 1303 1304 1305 1306 1307 1308 1309 1310 1311 1312 1313 1314 1315 1316 1317 1318 1319 1320 1321 1322 1323 1324 1325 1326 1327 1328 1329 1330 1331 1332 1333 1334 1335 1336 1337 1338 1339 1340 1341 1342 1343 1344 1345 1346 1347 1348 1349 1350 1351 1352 1353 1354 1355 1356 1357 1358 1359 1360 1361 1362 1363 1364 1365 1366 1367 1368 1369 1370 1371 1372 1373 1374 1375 1376 1377 1378 1379 1380 1381 1382 1383 1384 1385 1386 1387 1388 1389 1390 1391 1392 1393 1394 1395 1396 1397 1398 1399 1400 1401 1402 1403 1404 1405 1406 1407 1408 1409 1410 1411 1412 1413 1414 1415 1416 1417 1418 1419 1420 1421 1422 1423 1424 1425 1426 1427 1428 1429 1430 1431 1432 1433 1434 1435 1436 1437 1438 1439 1440 1441 1442 1443 1444 1445 1446 1447 1448 1449 1450 1451 1452 1453 1454 1455 1456 1457 1458 1459 1460 1461 1462 1463 1464 1465 1466 1467 1468 1469 1470 1471 1472 1473 1474 1475 1476 1477 1478 1479 1480 1481 1482 1483 1484 1485 1486 1487 1488 1489 1490 1491 1492 1493 1494 1495 1496 1497 1498 1499 1500 1501 1502 1503 1504 1505 1506 1507 1508 1509 1510 1511 1512 1513 1514 1515 1516 1517 1518 1519 1520 1521 1522 1523 1524 1525 1526 1527 1528 1529 1530 1531 1532 1533 1534 1535 1536 1537 1538 1539 1540 1541 1542 1543 1544 1545 1546 1547 1548 1549 1550 1551 1552 1553 1554 1555 1556 1557 1558 1559 1560 1561 1562 1563 1564 1565 1566 1567 1568 1569 1570 1571 1572 1573 1574 1575 1576 1577 1578 1579 1580 1581 1582 1583 1584 1585 1586 1587 1588 1589 1590 1591 1592 1593 1594 1595 1596 1597 1598 1599 1600 1601 1602 1603 1604 1605 1606 1607 1608 1609 1610 1611 1612 1613 1614 1615 1616 1617 1618 1619 1620 1621 1622 1623 1624 1625 1626 1627 1628 1629 1630 1631 1632 1633 1634 1635 1636 1637 1638 1639 1640 1641 1642 1643 1644 1645 1646 1647 1648 1649 1650 1651 1652 1653 1654 1655 1656 1657 1658 1659 1660 1661 1662 1663 1664 1665 1666 1667 1668 1669 1670 1671 1672 1673 1674 1675 1676 1677 1678 1679 1680 1681 1682 1683 1684 1685 1686 1687 1688 1689 1690 1691 1692 1693 1694 1695 1696 1697 1698 1699 1700 1701 1702 1703 1704 1705 1706 1707 1708 1709 1710 1711 1712 1713 1714 1715 1716 1717 1718 1719 1720 1721 1722 1723 1724 1725 1726 1727 1728 1729 1730 1731 1732 1733 1734 1735 1736 1737 1738 1739 1740 1741 1742 1743 1744 1745 1746 1747 1748 1749 1750 1751 1752 1753 1754 1755 1756 1757 1758 1759 1760 1761 1762 1763 1764 1765 1766 1767 1768 1769 1770 1771 1772 |
{
"paper_id": "N15-1045",
"header": {
"generated_with": "S2ORC 1.0.0",
"date_generated": "2023-01-19T14:35:29.721871Z"
},
"title": "An In-depth Analysis of the Effect of Text Normalization in Social Media",
"authors": [
{
"first": "Tyler",
"middle": [],
"last": "Baldwin",
"suffix": "",
"affiliation": {
"laboratory": "",
"institution": "IBM Research -Almaden",
"location": {
"addrLine": "650 Harry Road San Jose",
"postCode": "95120",
"region": "CA",
"country": "USA"
}
},
"email": "baldwin.tyler.s@gmail.com"
},
{
"first": "Yunyao",
"middle": [],
"last": "Li",
"suffix": "",
"affiliation": {
"laboratory": "",
"institution": "IBM Research -Almaden",
"location": {
"addrLine": "650 Harry Road San Jose",
"postCode": "95120",
"region": "CA",
"country": "USA"
}
},
"email": "yunyaoli@us.ibm.com"
}
],
"year": "",
"venue": null,
"identifiers": {},
"abstract": "Recent years have seen increased interest in text normalization in social media, as the informal writing styles found in Twitter and other social media data often cause problems for NLP applications. Unfortunately, most current approaches narrowly regard the normalization task as a \"one size fits all\" task of replacing non-standard words with their standard counterparts. In this work we build a taxonomy of normalization edits and present a study of normalization to examine its effect on three different downstream applications (dependency parsing, named entity recognition, and text-to-speech synthesis). The results suggest that how the normalization task should be viewed is highly dependent on the targeted application. The results also show that normalization must be thought of as more than word replacement in order to produce results comparable to those seen on clean text.",
"pdf_parse": {
"paper_id": "N15-1045",
"_pdf_hash": "",
"abstract": [
{
"text": "Recent years have seen increased interest in text normalization in social media, as the informal writing styles found in Twitter and other social media data often cause problems for NLP applications. Unfortunately, most current approaches narrowly regard the normalization task as a \"one size fits all\" task of replacing non-standard words with their standard counterparts. In this work we build a taxonomy of normalization edits and present a study of normalization to examine its effect on three different downstream applications (dependency parsing, named entity recognition, and text-to-speech synthesis). The results suggest that how the normalization task should be viewed is highly dependent on the targeted application. The results also show that normalization must be thought of as more than word replacement in order to produce results comparable to those seen on clean text.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Abstract",
"sec_num": null
}
],
"body_text": [
{
"text": "The informal writing style employed by authors of social media data is problematic for many natural language processing (NLP) tools, which are generally trained on clean, formal text such as newswire data. One possible solution to this problem is normalization, in which the informal text is converted into a more standard formal form. Because of this, the rise of social media data has coincided with a rise in interest in the normalization problem.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Introduction",
"sec_num": "1"
},
{
"text": "Unfortunately, while many approaches to the problem exist, there are notable limitations to the * Work was done while at IBM Research -Almaden.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Introduction",
"sec_num": "1"
},
{
"text": "way in which normalization is examined. First, although social media normalization is universally motivated by pointing to its role in helping downstream applications, most normalization work gives little to no insight into the effect of the normalization process on the downstream application of interest. Further, the normalization process is generally seen to be agnostic of the downstream application, adopting a \"one size fits all\" view of how normalization should be performed. This view seems intuitively problematic, as different information is likely to be of importance for different tasks. For instance, while capitalization is important for resolving named entities, it is less important for other tasks, such as dependency parsing.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Introduction",
"sec_num": "1"
},
{
"text": "Some recent work has given credence to the idea that application-targeted normalization is appropriate (Wang and Ng, 2013; Zhang et al., 2013) . However, how certain normalization actions influence the overall performance of these applications is not well understood. To address this, we design a taxonomy of possible normalization edits based on inspiration from previous work and an examination of annotated data. We then use this taxonomy to examine the importance of individual normalization actions on three different downstream applications: dependency parsing, named entity recognition, and textto-speech synthesis. The results suggest that the importance of a given normalization edit is highly dependent on the task, making the \"one size fits all\" approach inappropriate. The results also show that a narrow view of normalization as word replacement is insufficient, as many often-ignored normalization actions prove to be important for certain tasks.",
"cite_spans": [
{
"start": 103,
"end": 122,
"text": "(Wang and Ng, 2013;",
"ref_id": "BIBREF22"
},
{
"start": 123,
"end": 142,
"text": "Zhang et al., 2013)",
"ref_id": "BIBREF24"
}
],
"ref_spans": [],
"eq_spans": [],
"section": "Introduction",
"sec_num": "1"
},
{
"text": "In the next section, we give an overview of previous work on the normalization problem. We then introduce our taxonomy of normalization edits in Section 3. In Section 4, we present our evaluation methodology and present results over the three applications, using Twitter data as a representative domain. Finally, we discuss our results in Section 5 and conclude in Section 6.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Introduction",
"sec_num": "1"
},
{
"text": "Twitter and other social media data is littered with non-standard word forms and other informal usage patterns, making it difficult for many NLP tools to produce results comparable to what is seen on formal datasets. There are two approaches proposed in the literature to handle this problem (Eisenstein, 2013) . One approach is to tailor a specific NLP tool towards the data, by using training data from the domain to help the tool learn its specific idiosyncrasies. This approach has been applied with reasonable success on named entity recognition (Liu et al., 2011b; Ritter et al., 2011) as well as on parsing and part-ofspeech tagging (Foster et al., 2011) .",
"cite_spans": [
{
"start": 292,
"end": 310,
"text": "(Eisenstein, 2013)",
"ref_id": "BIBREF6"
},
{
"start": 551,
"end": 570,
"text": "(Liu et al., 2011b;",
"ref_id": "BIBREF14"
},
{
"start": 571,
"end": 591,
"text": "Ritter et al., 2011)",
"ref_id": "BIBREF19"
},
{
"start": 640,
"end": 661,
"text": "(Foster et al., 2011)",
"ref_id": "BIBREF8"
}
],
"ref_spans": [],
"eq_spans": [],
"section": "Related Work",
"sec_num": "2"
},
{
"text": "The other approach is normalization. Rather than tailoring a NLP tool towards the data, normalization seeks to tailor the data towards the tool. This is accomplished by transforming the data into a form more akin to the formal text that NLP tools are generally trained on. While normalization is often more straightforward and more easily applied in instances in which retraining is difficult or impractical, it has potential disadvantages as well, such as the potential loss of pragmatic nuance (Baldwin and Chai, 2011) .",
"cite_spans": [
{
"start": 496,
"end": 520,
"text": "(Baldwin and Chai, 2011)",
"ref_id": "BIBREF1"
}
],
"ref_spans": [],
"eq_spans": [],
"section": "Related Work",
"sec_num": "2"
},
{
"text": "Prior to the rise of social media, the normalization process was primarily seen as one of standardizing non-standard tokens found in otherwise clean text, such as numbers, dates, and acronyms (Sproat et al., 2001) . However, the current popularity of Twitter and other informal texts has caused the normalization task to take on a broader meaning in these contexts, where the goal is to convert informal text into formal text that downstream applications expect.",
"cite_spans": [
{
"start": 192,
"end": 213,
"text": "(Sproat et al., 2001)",
"ref_id": "BIBREF21"
}
],
"ref_spans": [],
"eq_spans": [],
"section": "Related Work",
"sec_num": "2"
},
{
"text": "Many different approaches to social media normalization have been undertaken. These approaches often draw inspiration from other tasks such as machine translation (Pennell and Liu, 2011; Aw et al., 2006) , spell checking (Choudhury et al., 2007) or speech recognition (Kobus et al., 2008) . Other approaches include creating automatic abbreviations via a maximum entropy classifier (Pennell and Liu, 2010) , creating word association graphs (Sonmez and Ozgur, 2014) , and incorporating both rules and statistical models (Beaufort et al., 2010) . While most initial approaches used supervised methods, unsupervised methods have recently become popular (Cook and Stevenson, 2009; Liu et al., 2011a; Yang and Eisenstein, 2013; Li and Liu, 2014) . Some work has chosen to focus on specific aspects of the normalization process, such as providing good coverage (Liu et al., 2012) or building normalization dictionaries (Han et al., 2012) .",
"cite_spans": [
{
"start": 163,
"end": 186,
"text": "(Pennell and Liu, 2011;",
"ref_id": "BIBREF18"
},
{
"start": 187,
"end": 203,
"text": "Aw et al., 2006)",
"ref_id": "BIBREF0"
},
{
"start": 221,
"end": 245,
"text": "(Choudhury et al., 2007)",
"ref_id": "BIBREF4"
},
{
"start": 268,
"end": 288,
"text": "(Kobus et al., 2008)",
"ref_id": "BIBREF11"
},
{
"start": 382,
"end": 405,
"text": "(Pennell and Liu, 2010)",
"ref_id": "BIBREF17"
},
{
"start": 441,
"end": 465,
"text": "(Sonmez and Ozgur, 2014)",
"ref_id": "BIBREF20"
},
{
"start": 520,
"end": 543,
"text": "(Beaufort et al., 2010)",
"ref_id": "BIBREF2"
},
{
"start": 651,
"end": 677,
"text": "(Cook and Stevenson, 2009;",
"ref_id": "BIBREF5"
},
{
"start": 678,
"end": 696,
"text": "Liu et al., 2011a;",
"ref_id": "BIBREF13"
},
{
"start": 697,
"end": 723,
"text": "Yang and Eisenstein, 2013;",
"ref_id": "BIBREF23"
},
{
"start": 724,
"end": 741,
"text": "Li and Liu, 2014)",
"ref_id": "BIBREF12"
},
{
"start": 856,
"end": 874,
"text": "(Liu et al., 2012)",
"ref_id": "BIBREF15"
},
{
"start": 914,
"end": 932,
"text": "(Han et al., 2012)",
"ref_id": "BIBREF9"
}
],
"ref_spans": [],
"eq_spans": [],
"section": "Related Work",
"sec_num": "2"
},
{
"text": "In all of the work mentioned above, the normalization task was seen primarily as one of converting non-standard tokens into an equivalent standard form. Similarly, many of these works defined the problem even more narrowly such that punctuation, capitalization, and multi-word replacements were ignored. However, two pieces of recent work have suggested that this understanding of the normalization task is too narrow, as it ignores many other hallmarks of informal writing that are prevalent in social media data. Wang and Ng (2013) present a beam search based approach designed to handle machine translation which incorporates attempts to correct mistaken punctuation and add missing words, such as forms of the verb to be. Similarly, Zhang et al. (2013) attempt to perform all actions necessary to create a formal text. In both instances the work was motivated by, and evaluated with respect to, a specific downstream application (machine translation and dependency parsing, respectively). However, not every study that tied the output to an application chose a broad interpretation of the normalization problem (Beaufort et al., 2010; Kaji and Kitsuregawa, 2014) .",
"cite_spans": [
{
"start": 515,
"end": 533,
"text": "Wang and Ng (2013)",
"ref_id": "BIBREF22"
},
{
"start": 737,
"end": 756,
"text": "Zhang et al. (2013)",
"ref_id": "BIBREF24"
},
{
"start": 1115,
"end": 1138,
"text": "(Beaufort et al., 2010;",
"ref_id": "BIBREF2"
},
{
"start": 1139,
"end": 1166,
"text": "Kaji and Kitsuregawa, 2014)",
"ref_id": "BIBREF10"
}
],
"ref_spans": [],
"eq_spans": [],
"section": "Related Work",
"sec_num": "2"
},
{
"text": "In order to understand the impact of individual normalization edits on downstream applications, we first need to define the space of possible normalization edits. While it is not uncommon for normalization work to present some analysis of the data, these analyses are often quite specific to the domain and datasets of interest. Because there is no agreed upon Figure 1 : Taxonomy of normalization edits taxonomy of normalization token or edit types, different analyses often look at different edit types and at different levels of granularity. In an attempt to help future work converge on a common understanding of normalization edits, in this section we present our taxonomy of normalization edits at several different levels of granularity. While it would be difficult for a taxonomy of normalization edits to be universal enough to be appropriate over all datasets and domains, we attempt to provide a taxonomy general enough to give future work a meaningful initial point of reference.",
"cite_spans": [],
"ref_spans": [
{
"start": 361,
"end": 369,
"text": "Figure 1",
"ref_id": null
}
],
"eq_spans": [],
"section": "Taxonomy of Normalization Edits",
"sec_num": "3"
},
{
"text": "Our taxonomy draws inspiration from both previous work and an examination of our own dataset (Section 3.3). In doing so, it attempts to cover normalization edits broadly, including cases that are universally understood to be important, such as slang replacement, as well as cases that are frequently ignored, such as capitalization correction. One of the guiding principles in the design of our taxonomy was that categories should not be divided so narrowly such that the phenomenon they capture appeared very infrequently in the data. One example of this is our decision not to divide punctuation edits at the lowest level of granularity. While certain clear categories exist (e.g., emoticons), these cases appeared in a small enough percentage of tokens that they would be difficult to examine and likely have a negligible effect on overall performance.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Methodology",
"sec_num": "3.1"
},
{
"text": "Our taxonomy of normalization edits is shown in Figure 1 . As can be seen, we categorize edits at three levels of granularity. Level One. The primary goal of the level one segmentation is to separate token replacements which are most centrally thought of as part of the normalization task from other instances that may require additional pragmatic inference. Specifically, we separate edits coarsely into three categories:",
"cite_spans": [],
"ref_spans": [
{
"start": 48,
"end": 56,
"text": "Figure 1",
"ref_id": null
}
],
"eq_spans": [],
"section": "Taxonomy",
"sec_num": "3.2"
},
{
"text": "\u2022 Token Replacements. Replacing one or more existing tokens with one or more new tokens (e.g., replacing wanna with want to).",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Taxonomy",
"sec_num": "3.2"
},
{
"text": "\u2022 Token Additions. Adding a token that does not replace an existing token (e.g., adding in missing subjects).",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Taxonomy",
"sec_num": "3.2"
},
{
"text": "\u2022 Token Removals. Removing a token without replacing it with an equivalent (e.g., removing laughter words such as lol and hahaha).",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Taxonomy",
"sec_num": "3.2"
},
{
"text": "Level Two. The next level of granularity separates normalization edits over word tokens from those over punctuation:",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Taxonomy",
"sec_num": "3.2"
},
{
"text": "\u2022 Word. Replacing, adding, or removing word tokens (depending on parent).",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Taxonomy",
"sec_num": "3.2"
},
{
"text": "\u2022 Punctuation. Replacing, adding, or removing punctuation tokens (depending on parent).",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Taxonomy",
"sec_num": "3.2"
},
{
"text": "Level Three. At the final level, we subdivide word edits into groups as appropriate for the edit type.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Taxonomy",
"sec_num": "3.2"
},
{
"text": "Rather than attempting to keep consistent groups across all leaf nodes, we selected the grouping based on the data distribution. For instance, Twitterspecific tokens (e.g., retweets) are often removed during normalization, so examining the removal of these words as a group is warranted. In contrast, these tokens are never added, so different segmentation is appropriate when examining word addition. At the lowest level of the taxonomy, word replacements were subdivided as follows:",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Taxonomy",
"sec_num": "3.2"
},
{
"text": "\u2022 Contraction Replacements. Unrolling standard contractions (don't), common informal cases (wanna), and non-standard variations produced via apostrophe omission (dont).",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Taxonomy",
"sec_num": "3.2"
},
{
"text": "\u2022 Slang Replacements. Replacing slang terms, such as slang shortenings and word elongation.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Taxonomy",
"sec_num": "3.2"
},
{
"text": "\u2022 Capitalization Replacements. Correcting the capitalization of words. The replaced word differs from its replacement by only capitalization.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Taxonomy",
"sec_num": "3.2"
},
{
"text": "\u2022 Other Replacements. Correcting unintentional typographic mistakes, such as misspelling and word concatenation.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Taxonomy",
"sec_num": "3.2"
},
{
"text": "When segmenting word additions, we note that words that need to be added in a normalization edit were often consciously dropped by the user in the original text. Our categorization reflects this by examining syntactic categories that are often dropped in informal writing:",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Taxonomy",
"sec_num": "3.2"
},
{
"text": "\u2022 Subject Addition. Adding in omitted subjects.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Taxonomy",
"sec_num": "3.2"
},
{
"text": "\u2022 Determiner Addition. Adding in omitted determiners (e.g., \"[The] front row is so close\").",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Taxonomy",
"sec_num": "3.2"
},
{
"text": "\u2022 Be-verb Addition. Adding in omitted forms of the verb to be.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Taxonomy",
"sec_num": "3.2"
},
{
"text": "\u2022 Other Addition. All word additions not covered by the other categories.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Taxonomy",
"sec_num": "3.2"
},
{
"text": "Finally, word removals are subdivided into just two categories:",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Taxonomy",
"sec_num": "3.2"
},
{
"text": "\u2022 Dataset-specific Removals. Removing tokens that do not appear outside of the dataset in question (e.g., for Twitter: hashtags, @replies, and retweets).",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Taxonomy",
"sec_num": "3.2"
},
{
"text": "\u2022 Other Removals. Removing interjections, laughter words, and other expression of emotion (e.g., ugh).",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Taxonomy",
"sec_num": "3.2"
},
{
"text": "Note that we are not suggesting here that datasetspecific words should be removed in all cases. While in many cases they may be removed if they do not have a formal equivalent, they may also be replaced or retained as is, depending on the context.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Taxonomy",
"sec_num": "3.2"
},
{
"text": "To facilitate our experiments, we collected and annotated a dataset of Twitter posts (tweets) from the TREC Twitter Corpus 1 . The TREC Twitter corpus is a collection of 16 million tweets posted in January and February of 2011. The corpus is designed to be a representative sample of Twitter usage, and as such includes both regular and spam tweets. To build our dataset, we sampled 600 posts at random from the corpus. The tweets were then manually filtered such that tweets that were not in English were replaced with those in English.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Dataset",
"sec_num": "3.3"
},
{
"text": "To produce our gold standard, two oDesk 2 contractors were asked to manually normalize each tweet in the dataset to its fully grammatical form, as would be found in formal text. Annotation guidelines stipulated that twitter-specific tokens should be retained if important to understanding the sentence, but modified or removed otherwise. As noted, most previous work often stopped short of requiring full grammaticality. However, Zhang et al. (2013) argued that grammaticality should be the ideal end goal of normalization since the models used in downstream applications are typically trained on well-formed sentences. We adopt this methodology here both because we agree with this assertion and because a fully grammatical form is appropriate for all of the downstream applications of interest, allowing for a single unified gold standard that can aid comparison across applications.",
"cite_spans": [
{
"start": 430,
"end": 449,
"text": "Zhang et al. (2013)",
"ref_id": "BIBREF24"
}
],
"ref_spans": [],
"eq_spans": [],
"section": "Dataset",
"sec_num": "3.3"
},
{
"text": "During gold standard creation, each normalization edit was labeled with its type, according to the above taxonomy. The distribution of normalization edits in the dataset is given in Table 1 . As shown, normalization edits accounted for about 29% of all tokens. Token replacements accounted for just over half of all edits (53%), while token addition (29%) was more common than token removal (18%). One interesting observation is non-capitalization word replacement accounted for only 25% of all normalization edits, intuitively indicating potential drawbacks for the common definition of normalization as one of simple word replacement which ignores capitalization and punctuation. ",
"cite_spans": [],
"ref_spans": [
{
"start": 182,
"end": 189,
"text": "Table 1",
"ref_id": "TABREF2"
}
],
"eq_spans": [],
"section": "Dataset",
"sec_num": "3.3"
},
{
"text": "In this section, we present our examination of the effect of normalization edits on downstream NLP applications. To get a broad understanding of these effects, we examine three very different cases: dependency parsing, named entity recognition (NER), and text-to-speech (TTS) synthesis. We chose these tasks because they each require the extraction of different information from the text. For instance, named entity recognition requires only a shallow syntactic analysis, in contrast to the deeper understanding required for dependency parsing. Similarly, only speech synthesis requires phoneme production, while the other tasks do not. Despite their differences, each of these tasks is relevant to larger applications that would benefit from improved performance on Twitter data, and each has garnered attention in the normalization and Twitter-adaptation literature (Beaufort et al., 2010; Liu et al., 2011b; Zhang et al., 2013) . Although the differences in these tasks also dictates that they be evaluated somewhat differently, we examine them within a common evaluation structure. In all cases, to examine the effects of each nor-malization edit we model our analyses as ablation studies. That is, for every category in the taxonomy, we examine the effect of performing all normalization edits except the relevant case. This allows us to measure the drop in performance solely attributable to each category; the greater the performance drop observed when a given normalization edit is not performed, the greater the importance of performing that edit.",
"cite_spans": [
{
"start": 868,
"end": 891,
"text": "(Beaufort et al., 2010;",
"ref_id": "BIBREF2"
},
{
"start": 892,
"end": 910,
"text": "Liu et al., 2011b;",
"ref_id": "BIBREF14"
},
{
"start": 911,
"end": 930,
"text": "Zhang et al., 2013)",
"ref_id": "BIBREF24"
}
],
"ref_spans": [],
"eq_spans": [],
"section": "Evaluation",
"sec_num": "4"
},
{
"text": "To aid analysis, results are presented in two ways: 1) as raw performance numbers, and 2) as an error rate per-token. These metrics give two different views of the relevance of each edit type. The raw numbers give a sense of the overall impact of a given category, and as such may be impacted by the size of the category, with common edits becoming more important simply by virtue of their frequency. In contrast, the per-token error rate highlights the cost of failing to perform a single instance of a given normalization edit, independent of the frequency of the edit. Both of these measures are likely to be relevant when attempting to improve the performance of a normalization system. Note that since the first measure is one of overall performance, smaller numbers reflect larger performance drops when removing a given type of edit, so that the smaller the number the more critical the need to perform the given type of normalization. In contrast, the latter judgment is one of error rate, and thus interpretation is reversed; the larger the error rate when it is removed, the more critical the normalization edit.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Evaluation",
"sec_num": "4"
},
{
"text": "Another commonality among the analyses is that performance is measured relative to the top performance of the tool, not the task. That is, following Zhang et al. (2013), we consider the output produced by the tool (e.g., the dependency parser) on the grammatically correct data to be gold standard performance. This means that some output based on our gold standard may in fact be incorrect relative to human judgment, simply because the tool used does not have perfect performance even if the text if fully grammatical. Since the goal is to understand how normalization edits impact the performance, this style of evaluation is appropriate; it considers mistakes attributable to normalization edits as erroneous, but ignores those mistakes attributable to the limitations of the tool.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Evaluation",
"sec_num": "4"
},
{
"text": "Finally, to maximize the relevance of the analyses given here, in each case we employ publicly available and widely used tools.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Evaluation",
"sec_num": "4"
},
{
"text": "To examine the effect of normalization on dependency parsing, we employ the Stanford dependency parser 3 (Marneffe et al., 2006) . To produce the gold standard dependencies for comparison, the manually grammaticalized tweets (Section 3.3) were run through the parser. To compare the ablation results to the gold standard parses, we adopt a variation of the evaluation method used by Zhang et al. (2013) . Given dependency parses from the gold standard and a candidate normalization, we define precision and recall as follows:",
"cite_spans": [
{
"start": 105,
"end": 128,
"text": "(Marneffe et al., 2006)",
"ref_id": "BIBREF16"
},
{
"start": 383,
"end": 402,
"text": "Zhang et al. (2013)",
"ref_id": "BIBREF24"
}
],
"ref_spans": [],
"eq_spans": [],
"section": "Parser Evaluation",
"sec_num": "4.1"
},
{
"text": "EQUATION",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [
{
"start": 0,
"end": 8,
"text": "EQUATION",
"ref_id": "EQREF",
"raw_str": "precision sov = |SOV \u2229 SOV gold | |SOV | (1) recall sov = |SOV \u2229 SOV gold | |SOV gold |",
"eq_num": "(2)"
}
],
"section": "Parser Evaluation",
"sec_num": "4.1"
},
{
"text": "Where SOV and SOV gold are the sets of subject, object, and verb dependencies in the candidate normalization and gold standard, respectively. While Zhang et al. chose to examine subjects and objects separately from verbs, we employ a unified metric to simplify interpretation.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Parser Evaluation",
"sec_num": "4.1"
},
{
"text": "Results of the ablation study are summarized in Table 2 . As shown, the performance of a complex task such as dependency parsing is broadly impacted by a variety of normalization edits. Based on the raw F-measure, the more common word replacements proved to be the most critical, although failing to handle token addition and removal edits also resulted in substantial drops in performance. At the lowest level in the taxonomy, slang replacements and subject addition were the most critical edits.",
"cite_spans": [],
"ref_spans": [
{
"start": 48,
"end": 55,
"text": "Table 2",
"ref_id": "TABREF4"
}
],
"eq_spans": [],
"section": "Results",
"sec_num": "4.1.1"
},
{
"text": "Although many replacement tasks were important in aggregate, on a per-token basis the most important edits were those that required token removal and addition. Perhaps unsurprisingly, failing to add subjects and verbs resulted in the largest issues, as the parser has little chance of identifying these dependencies if the terms simply do not appear in the sentence. However, not all word additions proved crit- ical, as failing to add in a missing determiner generally had little impact on the overall performance. Similarly, failing to correct capitalization did not cause substantial problems for the parser. Some word replacements did prove to be important, with slang and other word replacements showing some of the largest per-token error rates. Removing misleading punctuation or changing non-standard punctuation both proved important, but the per-token effect of punctuation addition was modest. In general, the results suggest that a complex task such as dependency parsing suffers substantially when the input data differs from formal text in any number of ways. With the exception of capitalization correction, performing almost every normalization edit is necessary to achieve results commensurate with those seen on formal text.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Results",
"sec_num": "4.1.1"
},
{
"text": "In this section, we examine the effect of each normalization edit on a somewhat more shallow interpretation task, named entity recognition. Unlike dependency parsing which requires an understanding of every token in the text, NER must only determine whether a given token is a named entity, and if so, discover its associated entity type.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "NER Evaluation",
"sec_num": "4.2"
},
{
"text": "The setup for evaluation of normalization edits on named entity recognition closely follows that of dependency parsing. We once again employ a tool from the suite of Stanford NLP tools, the Stanford named entity recognizer 4 (Finkel et al., 2005) . We also define precision and recall in a similar manner:",
"cite_spans": [
{
"start": 225,
"end": 246,
"text": "(Finkel et al., 2005)",
"ref_id": "BIBREF7"
}
],
"ref_spans": [],
"eq_spans": [],
"section": "NER Evaluation",
"sec_num": "4.2"
},
{
"text": "EQUATION",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [
{
"start": 0,
"end": 8,
"text": "EQUATION",
"ref_id": "EQREF",
"raw_str": "precision ner = |EN T \u2229 EN T gold | |EN T | (3) recall ner = |EN T \u2229 EN T gold | |EN T gold |",
"eq_num": "(4)"
}
],
"section": "NER Evaluation",
"sec_num": "4.2"
},
{
"text": "Where EN T and EN T gold are the sets of entities identified over the candidate normalization and gold standard sentences, respectively. Entities were labeled as one of three classes (person, location, or organization), and two entities were only considered a match if they both selected the same entity and the same entity class. Table 3 shows the results of the NER ablation study. Unlike dependency parsing, only word replacement edits proved to be critically important for NER tasks, as adding and subtracting words had little impact on the overall performance. Capitalization, which is generally an important feature for the identification of named entities, was unsurprisingly important. Similarly, the replacement of word types other than slang and contraction was important, because many of these instances may come from misspelled named entities. Slang and contractions were less important, as they were generally not used to reference named entities. As the words dropped by Twitter users tend to be function words that are not critical to understanding the sentence they are rarely named entities and have only a small effect on named entity recognition. Similarly, terms that are removed during normalization also tend to not be named entities, and thus has minor overall impact.",
"cite_spans": [],
"ref_spans": [
{
"start": 331,
"end": 338,
"text": "Table 3",
"ref_id": "TABREF6"
}
],
"eq_spans": [],
"section": "NER Evaluation",
"sec_num": "4.2"
},
{
"text": "A similar phenomenon is observed in the pertoken evaluation, where unintentionally produced, non-slang, non-contraction word replacement was seen to be of paramount importance. Punctuation removal was also important on a per-token basis, despite having little impact in aggregate.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Results",
"sec_num": "4.2.1"
},
{
"text": "Overall, the results given in Table 3 indicate that a focused approach to normalization for named entity recognition is warranted. Unlike dependency parsing that required a broad approach involving token addition and removal, the replacement-centric normalization approach typically employed by previous work is likely to be sufficient when the goal is to improve entity recognition.",
"cite_spans": [],
"ref_spans": [
{
"start": 30,
"end": 37,
"text": "Table 3",
"ref_id": "TABREF6"
}
],
"eq_spans": [],
"section": "Results",
"sec_num": "4.2.1"
},
{
"text": "Unlike the previous two tasks, the TTS problem is complicated by its need for speech production. Similarly, evaluation of speech synthesis is more difficult, as it requires human judgment about the overall quality of the output (Black and Tokuda, 2005) . While speech synthesis evaluations often rate performance on a 5 point scale, we adopt a more restricted method, based on the comparison to gold standard methodology used in the previous evaluations. For each tweet and each round of ablation, a synthesized audio file was produced from both the gold standard and ablated version of the tweet. These audio snippets were randomized and presented to human judges who were asked to make a binary judgment as to whether the meaning and understandability of the ablated case was comparable to the gold standard. The accuracy of a given round of ablation is then calculated to be the percentage of tweets judged to be similar to the gold standard. The eSpeak speech synthesizer 5 was used to produce audio files for all tweet variations in the ablation study. As is common for speech synthesizers, eSpeak does perform some amount of TTS-specific normalization natively. While this does influence the normalizations produced, the comparison to gold standard methodology employed in this study helps us to focus on differences that are primarily attributable to the normalization edits we wish to examine, not those produced natively. To obtain the gold standard, two native-English speaking judges were recruited via oDesk. Inter-annotator agreement was moderate, \u03ba = 0.48. Table 4 shows the results of the speech synthesis study. As shown, the removal of non-standard or out of place tokens was most critical to the production of a normalization that is clearly understandable to human listeners. The aggregate results for token removals were comparable to or better than those of replacements at all levels of the taxonomy, in contrast to the results from the other two tasks, where the larger number of replacements led to the largest performance hits. Meanwhile, word addition proved to be less essential overall.",
"cite_spans": [
{
"start": 228,
"end": 252,
"text": "(Black and Tokuda, 2005)",
"ref_id": "BIBREF3"
}
],
"ref_spans": [
{
"start": 1571,
"end": 1578,
"text": "Table 4",
"ref_id": "TABREF8"
}
],
"eq_spans": [],
"section": "TTS Evaluation",
"sec_num": "4.3"
},
{
"text": "At the token level, the importance of token removal is even more stark; the per-token error rate of every category of removal is greater than that of all other categories at the same taxonomy level. Although most word additions had a comparatively small effect on performance overall, they were important on a per-token basis. Most notably, subject adding had high per-token importance. In contrast, failing to add missing punctuation was not often marked as erroneous by human judges, nor was failing to normalize capitalization or contractions.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Results",
"sec_num": "4.3.1"
},
{
"text": "Similar to those on dependency parsing, the results on speech synthesis suggest that a broad approach that considers several different types of normalization edit is necessary to produce results comparable to those seen on clean text. However, at a high level there is a clear divide in importance between normalization types, where the greatest performance gains can be obtained by focusing on the comparatively small number of token removals.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Results",
"sec_num": "4.3.1"
},
{
"text": "The results presented in Section 4 are consistent with the hypothesis that a \"one size fits all\" approach to Twitter normalization is problematic, as the importance of a given normalization edit was highly dependent on the intended downstream task. Differences in which edits had the most substantial effect were present at all levels of scrutiny. Adding subjects and other words that a Twitter author dropped can be vitally important if the goal is to improve parsing performance, but can mostly be ignored if the goal is NER. Removing twitter-specific or otherwise non-standard words showed a gradation of importance over the three tasks, with little importance for NER, moderate importance for parsing, and critical importance for speech synthesis. Capitalization correction had negligible impact on the parser or synthesizer, but was helpful for NER.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Discussion",
"sec_num": "5"
},
{
"text": "The importance of different edit types can be seen even at the most coarse level of examination. While normalization for speech synthesis is primarily dependent on removing unknown tokens, normalization that targets name entity recognition would be better served focusing on replacing non-standard to-kens with their standard forms. In contrast, parsertargeted normalization must attend to both of the tasks, as well as the task of restoring dropped tokens.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Discussion",
"sec_num": "5"
},
{
"text": "Despite the differences, there are a few common threads that appear in each evaluation. Most notably, the results suggest that the decision of most recent Twitter normalization work to focus on word replacement was not entirely without merit, as the high frequency of token replacements translated into high overall importance for all tasks. Similarly, the focus on slang was also somewhat reasonable, as failing to handle slang terms had a significant impact on parsing and speech synthesis, though it had little impact on entity recognition. Nonetheless, the results in Section 4 clearly suggest that handling these cases represent only a small fraction of the actions necessary to produce performance comparable to what would be seen on formal text.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Discussion",
"sec_num": "5"
},
{
"text": "Another similarity among all instances was the lack of importance of certain categories. For instance, punctuation addition was not important for any of the three tasks. While Zhang et al. had hypothesized that punctuation addition would be important for dependency parsing, the results given here suggest that the overall impact is minor. Similarly, contraction standardization was not shown to be important in any of the evaluations. Contraction normalization is more representative of how the normalization task was seen prior to the rise of social media normalization, as it represents a fairly minor normalizing action that might still be performed on formal text. Since contractions likely appear in a variety of forms in the data used to train NLP tools, it is unsurprising that these tools are comparatively robust to contraction differences than to cases that are less typically encountered.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Discussion",
"sec_num": "5"
},
{
"text": "In this work, we presented an in-depth look at the effects of the normalization of Twitter data. To do so, we introduced a taxonomy of normalization edits based on an examination of our Twitter dataset and inspiration from previous work. The taxonomy allowed for normalization edits to be examined systematically at different levels of granularity, and enabled an examination of the effects of not only token replacements, but the token additions and removals that recent work has suggested may have been unjustly ignored.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Conclusion",
"sec_num": "6"
},
{
"text": "To understand the effects of each edit, we conducted ablation studies that examined results on three different downstream tasks: dependency parsing, named entity recognition, and text-to-speech synthesis. We found that while some normalization edits were universally important (or unimportant) for the production of accurate results, many differences persist. These results suggest that, for best results, how the normalization task is performed should not be agnostic of the downstream application. Further, our results support the suggestion that in order for downstream applications to produce accurate results, in most cases it is necessary to take a broad view of the normalization task the looks beyond simple word replacements.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Conclusion",
"sec_num": "6"
},
{
"text": "http://trec.nist.gov/data/tweets/ 2 https://www.odesk.com/",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "",
"sec_num": null
},
{
"text": "Version 1.47.11, http://espeak.sourceforge.net/",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "",
"sec_num": null
}
],
"back_matter": [
{
"text": "The authors would like to thank Benny Kimelfeld for his comments on an early draft of this work. We also thank our anonymous reviewers for their constructive comments and feedback, and Stephanie Mcneish, Lacy Corlis, and Kaila Milos C. Factolerin for their assistance with annotation and evaluation.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Acknowledgments",
"sec_num": null
}
],
"bib_entries": {
"BIBREF0": {
"ref_id": "b0",
"title": "A phrase-based statistical model for sms text normalization",
"authors": [
{
"first": "Aiti",
"middle": [],
"last": "Aw",
"suffix": ""
},
{
"first": "Min",
"middle": [],
"last": "Zhang",
"suffix": ""
},
{
"first": "Juan",
"middle": [],
"last": "Xiao",
"suffix": ""
},
{
"first": "Jian",
"middle": [],
"last": "Su",
"suffix": ""
}
],
"year": 2006,
"venue": "ACL",
"volume": "",
"issue": "",
"pages": "33--40",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "AiTi Aw, Min Zhang, Juan Xiao, and Jian Su. 2006. A phrase-based statistical model for sms text normaliza- tion. In ACL, pages 33-40.",
"links": null
},
"BIBREF1": {
"ref_id": "b1",
"title": "Beyond normalization: Pragmatics of word form in text messages",
"authors": [
{
"first": "Tyler",
"middle": [],
"last": "Baldwin",
"suffix": ""
},
{
"first": "Joyce",
"middle": [],
"last": "Chai",
"suffix": ""
}
],
"year": 2011,
"venue": "IJCNLP",
"volume": "",
"issue": "",
"pages": "1437--1441",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Tyler Baldwin and Joyce Chai. 2011. Beyond normal- ization: Pragmatics of word form in text messages. In IJCNLP, pages 1437-1441, Chiang Mai, Thailand, November. Asian Federation of Natural Language Pro- cessing.",
"links": null
},
"BIBREF2": {
"ref_id": "b2",
"title": "A hybrid rule/model-based finite-state framework for normalizing sms messages",
"authors": [
{
"first": "Richard",
"middle": [],
"last": "Beaufort",
"suffix": ""
},
{
"first": "Sophie",
"middle": [],
"last": "Roekhaut",
"suffix": ""
}
],
"year": 2010,
"venue": "ACL",
"volume": "",
"issue": "",
"pages": "770--779",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Richard Beaufort, Sophie Roekhaut, Louise-Am\u00e9lie Cougnon, and C\u00e9drick Fairon. 2010. A hybrid rule/model-based finite-state framework for normaliz- ing sms messages. In ACL, pages 770-779.",
"links": null
},
"BIBREF3": {
"ref_id": "b3",
"title": "The blizzard challenge -2005: evaluating corpus-based speech synthesis on common datasets",
"authors": [
{
"first": "Alan",
"middle": [
"W"
],
"last": "Black",
"suffix": ""
},
{
"first": "Keiichi",
"middle": [],
"last": "Tokuda",
"suffix": ""
}
],
"year": 2005,
"venue": "INTERSPEECH",
"volume": "",
"issue": "",
"pages": "77--80",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Alan W. Black and Keiichi Tokuda. 2005. The blizzard challenge -2005: evaluating corpus-based speech syn- thesis on common datasets. In INTERSPEECH, pages 77-80.",
"links": null
},
"BIBREF4": {
"ref_id": "b4",
"title": "Investigation and modeling of the structure of texting language",
"authors": [
{
"first": "Monojit",
"middle": [],
"last": "Choudhury",
"suffix": ""
},
{
"first": "Rahul",
"middle": [],
"last": "Saraf",
"suffix": ""
},
{
"first": "Vijit",
"middle": [],
"last": "Jain",
"suffix": ""
},
{
"first": "Animesh",
"middle": [],
"last": "Mukherjee",
"suffix": ""
},
{
"first": "Sudeshna",
"middle": [],
"last": "Sarkar",
"suffix": ""
},
{
"first": "Anupam",
"middle": [],
"last": "Basu",
"suffix": ""
}
],
"year": 2007,
"venue": "IJDAR",
"volume": "10",
"issue": "3-4",
"pages": "157--174",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Monojit Choudhury, Rahul Saraf, Vijit Jain, Animesh Mukherjee, Sudeshna Sarkar, and Anupam Basu. 2007. Investigation and modeling of the structure of texting language. IJDAR, 10(3-4):157-174.",
"links": null
},
"BIBREF5": {
"ref_id": "b5",
"title": "An unsupervised model for text message normalization",
"authors": [
{
"first": "Paul",
"middle": [],
"last": "Cook",
"suffix": ""
},
{
"first": "Suzanne",
"middle": [],
"last": "Stevenson",
"suffix": ""
}
],
"year": 2009,
"venue": "CALC",
"volume": "",
"issue": "",
"pages": "71--78",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Paul Cook and Suzanne Stevenson. 2009. An unsuper- vised model for text message normalization. In CALC, pages 71-78.",
"links": null
},
"BIBREF6": {
"ref_id": "b6",
"title": "What to do about bad language on the internet",
"authors": [
{
"first": "Jacob",
"middle": [],
"last": "Eisenstein",
"suffix": ""
}
],
"year": 2013,
"venue": "NAACL-HLT",
"volume": "",
"issue": "",
"pages": "359--369",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Jacob Eisenstein. 2013. What to do about bad language on the internet. In NAACL-HLT, pages 359-369, At- lanta, Georgia, June. Association for Computational Linguistics.",
"links": null
},
"BIBREF7": {
"ref_id": "b7",
"title": "Incorporating non-local information into information extraction systems by gibbs sampling",
"authors": [
{
"first": "Jenny",
"middle": [
"Rose"
],
"last": "Finkel",
"suffix": ""
},
{
"first": "Trond",
"middle": [],
"last": "Grenager",
"suffix": ""
},
{
"first": "Christopher",
"middle": [],
"last": "Manning",
"suffix": ""
}
],
"year": 2005,
"venue": "ACL",
"volume": "",
"issue": "",
"pages": "363--370",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Jenny Rose Finkel, Trond Grenager, and Christopher Manning. 2005. Incorporating non-local information into information extraction systems by gibbs sampling. In ACL, pages 363-370, Ann Arbor, Michigan, June. Association for Computational Linguistics.",
"links": null
},
"BIBREF8": {
"ref_id": "b8",
"title": "hardtoparse: Pos tagging and parsing the twitterverse. volume WS-11-05 of AAAI Workshops",
"authors": [
{
"first": "Jennifer",
"middle": [],
"last": "Foster",
"suffix": ""
},
{
"first": "Joachim",
"middle": [],
"last": "\u00d6zlem \u00c7 Etinoglu",
"suffix": ""
},
{
"first": "Joseph",
"middle": [
"Le"
],
"last": "Wagner",
"suffix": ""
},
{
"first": "Stephen",
"middle": [],
"last": "Roux",
"suffix": ""
},
{
"first": "Joakim",
"middle": [],
"last": "Hogan",
"suffix": ""
},
{
"first": "Deirdre",
"middle": [],
"last": "Nivre",
"suffix": ""
},
{
"first": "Josef",
"middle": [],
"last": "Hogan",
"suffix": ""
},
{
"first": "",
"middle": [],
"last": "Van Genabith",
"suffix": ""
}
],
"year": 2011,
"venue": "",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Jennifer Foster,\u00d6zlem \u00c7 etinoglu, Joachim Wagner, Joseph Le Roux, Stephen Hogan, Joakim Nivre, Deirdre Hogan, and Josef van Genabith. 2011. hard- toparse: Pos tagging and parsing the twitterverse. vol- ume WS-11-05 of AAAI Workshops. AAAI.",
"links": null
},
"BIBREF9": {
"ref_id": "b9",
"title": "Automatically constructing a normalisation dictionary for microblogs",
"authors": [
{
"first": "Bo",
"middle": [],
"last": "Han",
"suffix": ""
},
{
"first": "Paul",
"middle": [],
"last": "Cook",
"suffix": ""
},
{
"first": "Timothy",
"middle": [],
"last": "Baldwin",
"suffix": ""
}
],
"year": 2012,
"venue": "EMNLP-CoNLL",
"volume": "",
"issue": "",
"pages": "421--432",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Bo Han, Paul Cook, and Timothy Baldwin. 2012. Auto- matically constructing a normalisation dictionary for microblogs. In EMNLP-CoNLL, pages 421-432.",
"links": null
},
"BIBREF10": {
"ref_id": "b10",
"title": "Accurate word segmentation and pos tagging for japanese microblogs: Corpus annotation and joint modeling with lexical normalization",
"authors": [
{
"first": "Nobuhiro",
"middle": [],
"last": "Kaji",
"suffix": ""
},
{
"first": "Masaru",
"middle": [],
"last": "Kitsuregawa",
"suffix": ""
}
],
"year": 2014,
"venue": "Proceedings of the 2014 Conference on Empirical Methods in Natural Language Processing (EMNLP)",
"volume": "",
"issue": "",
"pages": "99--109",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Nobuhiro Kaji and Masaru Kitsuregawa. 2014. Accu- rate word segmentation and pos tagging for japanese microblogs: Corpus annotation and joint modeling with lexical normalization. In Proceedings of the 2014 Conference on Empirical Methods in Natural Language Processing (EMNLP), pages 99-109, Doha, Qatar, October. Association for Computational Lin- guistics.",
"links": null
},
"BIBREF11": {
"ref_id": "b11",
"title": "Normalizing SMS: are two metaphors better than one",
"authors": [
{
"first": "Catherine",
"middle": [],
"last": "Kobus",
"suffix": ""
},
{
"first": "Fran\u00e7ois",
"middle": [],
"last": "Yvon",
"suffix": ""
},
{
"first": "G\u00e9raldine",
"middle": [],
"last": "Damnati",
"suffix": ""
}
],
"year": 2008,
"venue": "COLING",
"volume": "",
"issue": "",
"pages": "441--448",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Catherine Kobus, Fran\u00e7ois Yvon, and G\u00e9raldine Damnati. 2008. Normalizing SMS: are two metaphors better than one? In COLING, pages 441-448.",
"links": null
},
"BIBREF12": {
"ref_id": "b12",
"title": "Improving text normalization via unsupervised model and discriminative reranking",
"authors": [
{
"first": "Chen",
"middle": [],
"last": "Li",
"suffix": ""
},
{
"first": "Yang",
"middle": [],
"last": "Liu",
"suffix": ""
}
],
"year": 2014,
"venue": "Proceedings of the ACL 2014 Student Research Workshop",
"volume": "",
"issue": "",
"pages": "86--93",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Chen Li and Yang Liu. 2014. Improving text nor- malization via unsupervised model and discriminative reranking. In Proceedings of the ACL 2014 Student Research Workshop, pages 86-93, Baltimore, Mary- land, USA, June. Association for Computational Lin- guistics.",
"links": null
},
"BIBREF13": {
"ref_id": "b13",
"title": "Insertion, deletion, or substitution? normalizing text messages without pre-categorization nor supervision",
"authors": [
{
"first": "Fei",
"middle": [],
"last": "Liu",
"suffix": ""
},
{
"first": "Fuliang",
"middle": [],
"last": "Weng",
"suffix": ""
},
{
"first": "Bingqing",
"middle": [],
"last": "Wang",
"suffix": ""
},
{
"first": "Yang",
"middle": [],
"last": "Liu",
"suffix": ""
}
],
"year": 2011,
"venue": "ACL",
"volume": "",
"issue": "",
"pages": "71--76",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Fei Liu, Fuliang Weng, Bingqing Wang, and Yang Liu. 2011a. Insertion, deletion, or substitution? normal- izing text messages without pre-categorization nor su- pervision. In ACL, pages 71-76.",
"links": null
},
"BIBREF14": {
"ref_id": "b14",
"title": "Recognizing named entities in tweets",
"authors": [
{
"first": "Xiaohua",
"middle": [],
"last": "Liu",
"suffix": ""
},
{
"first": "Shaodian",
"middle": [],
"last": "Zhang",
"suffix": ""
},
{
"first": "Furu",
"middle": [],
"last": "Wei",
"suffix": ""
},
{
"first": "Ming",
"middle": [],
"last": "Zhou",
"suffix": ""
}
],
"year": 2011,
"venue": "NAACL-HLT",
"volume": "",
"issue": "",
"pages": "359--367",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Xiaohua Liu, Shaodian Zhang, Furu Wei, and Ming Zhou. 2011b. Recognizing named entities in tweets. In NAACL-HLT, pages 359-367, Portland, Oregon, USA, June. Association for Computational Linguis- tics.",
"links": null
},
"BIBREF15": {
"ref_id": "b15",
"title": "A broadcoverage normalization system for social media language",
"authors": [
{
"first": "Fei",
"middle": [],
"last": "Liu",
"suffix": ""
},
{
"first": "Fuliang",
"middle": [],
"last": "Weng",
"suffix": ""
},
{
"first": "Xiao",
"middle": [],
"last": "Jiang",
"suffix": ""
}
],
"year": 2012,
"venue": "ACL",
"volume": "",
"issue": "",
"pages": "1035--1044",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Fei Liu, Fuliang Weng, and Xiao Jiang. 2012. A broad- coverage normalization system for social media lan- guage. In ACL, pages 1035-1044.",
"links": null
},
"BIBREF16": {
"ref_id": "b16",
"title": "Generating typed dependency parses from phrase structure parses",
"authors": [
{
"first": "Marie-Catherine De",
"middle": [],
"last": "Marneffe",
"suffix": ""
},
{
"first": "Bill",
"middle": [],
"last": "Maccartney",
"suffix": ""
},
{
"first": "Christopher",
"middle": [
"D"
],
"last": "Manning",
"suffix": ""
}
],
"year": 2006,
"venue": "LREC",
"volume": "",
"issue": "",
"pages": "449--454",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Marie-Catherine De Marneffe, Bill MacCartney, and Christopher D. Manning. 2006. Generating typed dependency parses from phrase structure parses. In LREC, pages 449-454.",
"links": null
},
"BIBREF17": {
"ref_id": "b17",
"title": "Normalization of text messages for text-to-speech",
"authors": [
{
"first": "Deana",
"middle": [],
"last": "Pennell",
"suffix": ""
},
{
"first": "Yang",
"middle": [],
"last": "Liu",
"suffix": ""
}
],
"year": 2010,
"venue": "ICASSP",
"volume": "",
"issue": "",
"pages": "4842--4845",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Deana Pennell and Yang Liu. 2010. Normalization of text messages for text-to-speech. In ICASSP, pages 4842-4845.",
"links": null
},
"BIBREF18": {
"ref_id": "b18",
"title": "A characterlevel machine translation approach for normalization of SMS abbreviations",
"authors": [
{
"first": "Deana",
"middle": [],
"last": "Pennell",
"suffix": ""
},
{
"first": "Yang",
"middle": [],
"last": "Liu",
"suffix": ""
}
],
"year": 2011,
"venue": "IJCNLP",
"volume": "",
"issue": "",
"pages": "974--982",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Deana Pennell and Yang Liu. 2011. A character- level machine translation approach for normalization of SMS abbreviations. In IJCNLP, pages 974-982.",
"links": null
},
"BIBREF19": {
"ref_id": "b19",
"title": "Named entity recognition in Tweets: An experimental study",
"authors": [
{
"first": "Alan",
"middle": [],
"last": "Ritter",
"suffix": ""
},
{
"first": "Sam",
"middle": [],
"last": "Clark",
"suffix": ""
},
{
"first": "Mausam",
"middle": [],
"last": "",
"suffix": ""
},
{
"first": "Oren",
"middle": [],
"last": "Etzioni",
"suffix": ""
}
],
"year": 2011,
"venue": "EMNLP",
"volume": "",
"issue": "",
"pages": "1524--1534",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Alan Ritter, Sam Clark, Mausam, and Oren Etzioni. 2011. Named entity recognition in Tweets: An ex- perimental study. In EMNLP, pages 1524-1534.",
"links": null
},
"BIBREF20": {
"ref_id": "b20",
"title": "A graph-based approach for contextual text normalization",
"authors": [
{
"first": "Cagil",
"middle": [],
"last": "Sonmez",
"suffix": ""
},
{
"first": "Arzucan",
"middle": [],
"last": "Ozgur",
"suffix": ""
}
],
"year": 2014,
"venue": "Proceedings of the 2014 Conference on Empirical Methods in Natural Language Processing (EMNLP)",
"volume": "",
"issue": "",
"pages": "313--324",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Cagil Sonmez and Arzucan Ozgur. 2014. A graph-based approach for contextual text normalization. In Pro- ceedings of the 2014 Conference on Empirical Meth- ods in Natural Language Processing (EMNLP), pages 313-324, Doha, Qatar, October. Association for Com- putational Linguistics.",
"links": null
},
"BIBREF21": {
"ref_id": "b21",
"title": "Normalization of non-standard words",
"authors": [
{
"first": "Richard",
"middle": [],
"last": "Sproat",
"suffix": ""
},
{
"first": "Alan",
"middle": [
"W"
],
"last": "Black",
"suffix": ""
},
{
"first": "Stanley",
"middle": [
"F"
],
"last": "Chen",
"suffix": ""
},
{
"first": "Shankar",
"middle": [],
"last": "Kumar",
"suffix": ""
},
{
"first": "Mari",
"middle": [],
"last": "Ostendorf",
"suffix": ""
},
{
"first": "Christopher",
"middle": [],
"last": "Richards",
"suffix": ""
}
],
"year": 2001,
"venue": "Computer Speech & Language",
"volume": "15",
"issue": "3",
"pages": "287--333",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Richard Sproat, Alan W. Black, Stanley F. Chen, Shankar Kumar, Mari Ostendorf, and Christopher Richards. 2001. Normalization of non-standard words. Com- puter Speech & Language, 15(3):287-333.",
"links": null
},
"BIBREF22": {
"ref_id": "b22",
"title": "A beam-search decoder for normalization of social media text with application to machine translation",
"authors": [
{
"first": "Pidong",
"middle": [],
"last": "Wang",
"suffix": ""
},
{
"first": "Hwee Tou",
"middle": [],
"last": "Ng",
"suffix": ""
}
],
"year": 2013,
"venue": "NAACL-HLT",
"volume": "",
"issue": "",
"pages": "471--481",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Pidong Wang and Hwee Tou Ng. 2013. A beam-search decoder for normalization of social media text with application to machine translation. In NAACL-HLT, pages 471-481, Atlanta, Georgia, June. Association for Computational Linguistics.",
"links": null
},
"BIBREF23": {
"ref_id": "b23",
"title": "A log-linear model for unsupervised text normalization",
"authors": [
{
"first": "Yi",
"middle": [],
"last": "Yang",
"suffix": ""
},
{
"first": "Jacob",
"middle": [],
"last": "Eisenstein",
"suffix": ""
}
],
"year": 2013,
"venue": "Proceedings of the 2013 Conference on Empirical Methods in Natural Language Processing",
"volume": "",
"issue": "",
"pages": "61--72",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Yi Yang and Jacob Eisenstein. 2013. A log-linear model for unsupervised text normalization. In Proceedings of the 2013 Conference on Empirical Methods in Natu- ral Language Processing, pages 61-72, Seattle, Wash- ington, USA, October. Association for Computational Linguistics.",
"links": null
},
"BIBREF24": {
"ref_id": "b24",
"title": "Adaptive parsercentric text normalization",
"authors": [
{
"first": "Congle",
"middle": [],
"last": "Zhang",
"suffix": ""
},
{
"first": "Tyler",
"middle": [],
"last": "Baldwin",
"suffix": ""
},
{
"first": "Howard",
"middle": [],
"last": "Ho",
"suffix": ""
},
{
"first": "Benny",
"middle": [],
"last": "Kimelfeld",
"suffix": ""
},
{
"first": "Yunyao",
"middle": [],
"last": "Li",
"suffix": ""
}
],
"year": 2013,
"venue": "ACL",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Congle Zhang, Tyler Baldwin, Howard Ho, Benny Kimelfeld, and Yunyao Li. 2013. Adaptive parser- centric text normalization. In ACL, Sofia, Bulgaria, August. Association for Computational Linguistics.",
"links": null
}
},
"ref_entries": {
"TABREF2": {
"num": null,
"text": "",
"html": null,
"type_str": "table",
"content": "<table/>"
},
"TABREF4": {
"num": null,
"text": "",
"html": null,
"type_str": "table",
"content": "<table/>"
},
"TABREF6": {
"num": null,
"text": "",
"html": null,
"type_str": "table",
"content": "<table/>"
},
"TABREF8": {
"num": null,
"text": "",
"html": null,
"type_str": "table",
"content": "<table/>"
}
}
}
} |