Liability With Regard to Artificial Intelligence - Fordham Intellectual Property, Media & Entertainment Law Journal
post-template-default,single,single-post,postid-27159,single-format-standard,ajax_fade,page_not_loaded,,select-theme-ver-3.3,wpb-js-composer js-comp-ver-6.6.0,vc_responsive

Liability With Regard to Artificial Intelligence

Liability With Regard to Artificial Intelligence

In 2016, Microsoft developed a chatbot—a piece of artificial intelligence (“AI”) software created to “develop conversational understanding by interacting with humans”—named Tay to engage with users on Twitter.1 Tay was designed to appeal to millennial users and learn from other users’ posts.2 However, within 24 hours, Twitter users manipulated Tay into posting right-wing and anti-Semitic hate speech.3 In response, Microsoft shut Tay down, explained that users “exploited a vulnerability in Tay” which developed from “a critical oversight [by Microsoft] for this specific attack,” and took “full responsibility” for not anticipating this vulnerability.4 But how exactly were Twitters users able to do this? And what would Microsoft taking responsibility mean in a legal sense?

A very brief overview of how AI software like Tay may be helpful to unpacking both questions. Basic AI networks involve code which resembles a series of layered “neurons” that use linear algebra to processes data.5 The initial layer of neurons, which are the code’s vessels for holding values, receive the information and assigns each input a value from zero to one.6 They then pass these values along to further “hidden” layers of neurons which refine it in some desired way.7 After a series of hidden layer refine these inputs and attribute some new value, these hidden layer neurons then activate the output layer neurons (which correspond to outputs designated by the code) to varying degrees.8 The values of the output neurons represent the confidence the network has in that output, where zero indicates no confidence that this output is correct, and one being complete confidence.9 The output with the most confidence is then selected as the network’s “answer.”10

However, issues arise when the network either chooses the wrong answer or is uncertain about its answer (usually denoted by middling confidence amongst many different outcomes).11. To rectify these issues, the system undergoes a process called “deep learning” where it tries to minimize the “cost function” that measures the system’s output inaccuracy; the greater a cost function, the more inaccurate the system.12 The system then undergoes “backpropagation” in order to change values of the prior neurons to conform to the minimization of its cost function.13 Backpropagation changes how the system’s neurons interpret the input data in hopes of producing more accurate outputs.14 After this process is complete, the system will do the same thing after a new batch of input data is achieved.

This process allows the programmers to control how the AI “learns,” but not exactly what they “learn.” With Tay, too many right-wing posts manipulated her algorithm to make it “think” that this was the proper way to have conversations.15 Its algorithm essentially told it that these were the correct inputs and, consequently, its further communications attempted to mirror these inputs responses as outputs. The network’s ability to “learn” and then act on this learning—without further input from the developers—creates an issue for assigning liability: if a program “learns” and then “chooses” to do something without the developer’s input, can the developer be held liable?

Very little litigation has occurred to develop a uniform framework to address this issue of how to assign liability for AI software like Tay.16 Some courts have heard cases regarding breach of warranty liability, categorizing non-AI software as a service rather than a product.17 Meanwhile, others have found software to be a product, rather than a service.18 Categorizing software as property could subject developers to product liability claims, and thus hold them strictly liable for the “decisions” of an AI robot.19

Some state legislatures have adopting autonomous vehicle laws to address similar liability concerns.20 California has opted to require autonomous vehicle manufactures to purchase a $5,000,000 surety bond to protect citizens if the manufacturer “fails to pay any final judgement for damages for personal injury, death or property damage arising from an accident an autonomous vehicle operated by the manufacturer before are allowed….”21 Florida, like California, also puts the liability of autonomous vehicles onto the manufacturers, requiring that they hold a $1,000,000 insurance policy.22 While it seems these regulations take a stance as to where liability falls, some academic authors are advocating for some AI (like IBM’s Watson) to be treated differently than autonomous vehicles, and to instead be given personhood designations.23 While the conversation about liability for some forms of AI software is being had, we will have to wait for courts and legislatures to address this issue directly.

  1. Amy Kraft, Microsoft shuts down AI chatbot after it turned into a Nazi, CBS News (last updated Mar. 25, 2016, 7:53 PM), [].

  2. Id.

  3. Id.

  4. Id.

  5. Grant Sanderson, But what is a Neural Network? | Deep learning, chapter 1, YouTube (Oct. 5, 2017),

  6. Id.

  7. Id.

  8. Id.

  9. Id.

  10. Id.

  11. Id.

  12. Grant Sanderson, Gradient descent, how neural networks learn | Deep learning, chapter 2, YouTube (Oct. 16, 2017),

  13. Grant Sanderson, What is backpropagation really doing? | Deep learning, chapter 3, YouTube (Nov. 3, 2017),

  14. Id.

  15. See Kraft, supra note 1.

  16. Article: Artificial Intelligence Litigation: Can the Law Keep Pace with The Rise of the Machines?, Quinn Emanuel Urquhart & Sullivan, LLP (Dec. 2016), [].

  17. See Motorola Mobility, Inc. v. Myriad France SAS, 850 F. Supp. 2d 878, 885 (N.D. Ill. 2012).

  18. See South Cent. Bell Tel. Co. v. Barthelemy, 643 So. 2d 1240, 1244 (La. 1994) (holding that computer software constitutes “corporeal property”); Schafer v. State Farm Fire & Cas. Co., 507 F. Supp. 2d 587, 601 (E.D. La. 2007) (approving of the Barthelemy court’s classification of software as a product and constituting the software in this case as software); Gilreath v. General Elec. Co., 751 So. 2d 705, 708 (Fla. Dist. Ct. App. 2000) (disagreeing with the Barthelemy court’s classification of software as tangible property, but rather accepting software as intangible personal property).

  19. See Quinn Emanuel Urquhart & Sullivan, LLP, supra note 16.

  20. Id.

  21. Cal. Code Regs. tit. 13, § 227.10 (2014).

  22. CS/HB 311 Autonomous Vehicles, 2019 Legis. Bill Hist. FL H.B. 311.

  23. Jason Chung & Amanda Zink, Hey Watson, Can I Sue You for Malpractice? Examining the Liability of Artificial Intelligence in Medicine, 11 Asia Pac. J. Health L. & Ethics 51, 51 (2018).

Pearse Walsh

Pearse Walsh is a 2LE staff member on the IPLJ and graduated from Fordham College at Rose Hill in 2019 with a B.S. in General Science and Philosophy. At FLS, he is also a TA for Professor Denno’s Crim class, one of the co-VPs on the FEDS E-Board, and the EVP of the SBA E-Board.