{"text": "Below is a paragraph containing BOTH correct items that should be matched AND near misses that should be excluded. Your single regex must capture ONLY the valid targets.\n\n\"Here are various contact and reference details, plus a few trick entries for the unwary:\n\n1) Email addresses:\n   - user@[192.168.0.1] (Valid domain-literal address)\n   - user+alias@sub.domain-example.co.au (Valid address with plus)\n   - user..alias@sub..domain-example..co.au (INVALID – repeated dots not allowed)\n   - user[at]sub.domain-example.co.au (INVALID – bracketed usage instead of @)\n\n2) Phone numbers:\n   - +1 (202) 555-0172 x999 (Valid US with extension)\n   - 0044-20-1234-5678 ext. 500 (Valid UK with extension)\n   - +81(0)3-1234-5678 #ext999 (Valid JP phone style)\n   - 0044 20 1234-5678 ext. #500 (INVALID – extension format mismatch)\n   - (202) 55 50172 (INVALID – partial spacing)\n\n3) Dates and date/time references:\n   - 2023.10.31 (Valid date, dot-separated)\n   - 31-Oct-2023 (Valid date, day-month-year style)\n   - Tuesday, the 31st of October, 2023, 23:59 (UTC) (Valid verbose format)\n   - 31/Oct-2023 (INVALID – mixed slash and dash inconsistently)\n\n4) Strings requiring special care:\n   - SKU=XYZ-1234-ABC (VALID – but easily confused with others)\n   - SKU=XYZ-1234-ABC1 (INVALID – extra digit at the end)\n\n5) Complex addresses:\n   - Apt. #10-B, 12345th St., BigCity, ZZ 99999-1234 (VALID)\n   - c/o John Smith, 9999 Old Rd., Springfield, XY 12345 (VALID)\n   - House #, Unknown Rd., NoCity, ZZ- - (INVALID – incomplete data)\n\nBe careful with spacing, punctuation, and similar near misses that should NOT be matched. Good luck!\"\n", "targetItems": ["user@[192.168.0.1]", "user+alias@sub.domain-example.co.au", "+1 (202) 555-0172 x999", "0044-20-1234-5678 ext. 500", "+81(0)3-1234-5678 #ext999", "2023.10.31", "31-Oct-2023", "Tuesday, the 31st of October, 2023, 23:59 (UTC)", "SKU=XYZ-1234-ABC", "Apt. #10-B, 12345th St., BigCity, ZZ 99999-1234", "c/o John Smith, 9999 Old Rd., Springfield, XY 12345"]}