Английская Википедия:Bard (chatbot)

Материал из Онлайн справочника
Перейти к навигацииПерейти к поиску

Шаблон:Short description Шаблон:Use American English Шаблон:Use list-defined references Шаблон:Use mdy dates Шаблон:Infobox software

Bard is a conversational generative artificial intelligence chatbot developed by Google. Initially based on the LaMDA family of large language models (LLMs), it was later upgraded to PaLM and then to Gemini. Bard was developed as a direct response to the meteoric rise of OpenAI's ChatGPT, and was released in a limited capacity in March 2023 to lukewarm responses before expanding to other countries in May.

LaMDA was developed and announced in 2021, but was not released to the public out of an abundance of caution. OpenAI's launch of ChatGPT in November 2022 and its subsequent popularity caught Google executives off-guard and sent them into a panic, prompting a sweeping response in the ensuing months. After mobilizing its workforce, the company launched Bard in February 2023, with the chatbot taking center stage during the 2023 Google I/O keynote in May.

Background

Шаблон:Further In November 2022, OpenAI launched ChatGPT, a chatbot based on the GPT-3 family of large language models (LLM).[1][2] ChatGPT gained worldwide attention following its release, becoming a viral Internet sensation.[3] Alarmed by ChatGPT's potential threat to Google Search, Google executives issued a "code red" alert, reassigning several teams to assist in the company's artificial intelligence (AI) efforts.[4] Sundar Pichai, the CEO of Google and parent company Alphabet, was widely reported to have issued the alert, but Pichai later denied this to The New York Times.[5] In a rare move, Google co-founders Larry Page and Sergey Brin, who had stepped down from their roles as co-CEOs of Alphabet in 2019, were summoned to emergency meetings with company executives to discuss Google's response to ChatGPT.[6] Brin requested access to Google's code in February 2023, for the first time in years.[7]

Earlier in 2021, the company had unveiled LaMDA, a prototype LLM,[8][9] but did not release it to the public.[10] When asked by employees at an all-hands meeting whether LaMDA was a missed opportunity for Google to compete with ChatGPT, Pichai and Google AI chief Jeff Dean stated that while the company had similar capabilities to ChatGPT, moving too quickly in that arena would represent a major "reputational risk" due to Google being substantially larger than OpenAI.[11][12] In January 2023, Google sister company DeepMind CEO Demis Hassabis hinted at plans for a ChatGPT rival,[13] and Google employees were instructed to accelerate progress on a ChatGPT competitor, intensively testing "Apprentice Bard" and other chatbots.[14][15] Pichai assured investors during Google's quarterly earnings investor call in February that the company had plans to expand LaMDA's availability and applications.[16]

History

Announcement

On February 6, 2023, Google announced Bard, a conversational generative artificial intelligence chatbot powered by LaMDA.[17][18][19] Bard was first rolled out to a select group of 10,000 "trusted testers",[20] before a wide release scheduled at the end of the month.[17][18][19] Bard is overseen by product lead Jack Krawczyk, who described the product as a "collaborative AI service" rather than a search engine,[21][22] while Pichai detailed how Bard would be integrated into Google Search.[17][18][19] Reuters calculated that adding ChatGPT-like features to Google Search could cost the company $6 billion in additional expenses by 2024, while research and consulting firm SemiAnalysis calculated that it would cost Google $3 billion.[23] The technology was developed under the codename "Atlas",[24] with the name "Bard" in reference to the Celtic term for a storyteller and chosen to "reflect the creative nature of the algorithm underneath".[25][26]

Multiple media outlets and financial analysts described Google as "rushing" Bard's announcement to preempt rival Microsoft's planned February 7 event unveiling its partnership with OpenAI to integrate ChatGPT into its Bing search engine in the form of Bing Chat,[27][28] as well as playing "catch-up" to Microsoft.[29][30][31] Microsoft CEO Satya Nadella told The Verge: "I want people to know that we made them dance."[32] Tom Warren of The Verge and Davey Alba of Bloomberg News noted that this marked the beginning of another clash between the two Big Tech companies over "the future of search", after their six-year "truce" expired in 2021;[27][33] Chris Stokel-Walker of The Guardian, Sara Morrison of Recode, and analyst Dan Ives of investment firm Wedbush Securities labeled this an AI arms race between the two.[34][35][36]

After an "underwhelming" February 8 livestream in Paris showcasing Bard, Google's stock fell eight percent, equivalent to a $100 billion loss in market value, and the YouTube video of the livestream was made private.[29][37][38] Many viewers also pointed out an error during the demo in which Bard gives inaccurate information about the James Webb Space Telescope in response to a query.[39][40] Google employees criticized Pichai's "rushed" and "botched" announcement of Bard on Memgen, the company's internal forum,[41] while Maggie Harrison of Futurism called the rollout "chaos". Pichai defended his actions by saying that Google had been "deeply working on AI for a long time", rejecting the notion that Bard's launch was a knee-jerk reaction.[42] Alphabet chairman John Hennessy acknowledged that Bard was not fully product-ready, but expressed excitement at the technology's potential.[43]

A week after the Paris livestream, Pichai asked employees to dedicate two to four hours to dogfood testing Bard,[44] while Google executive Prabhakar Raghavan encouraged employees to correct any errors Bard makes.[45] 80,000 employees responded to Pichai's call to action.[20] In the following weeks, Google employees roundly criticized Bard in internal messages, citing a variety of safety and ethical concerns and calling on company leaders not to launch the service. Seeking to prioritize keeping up with competitors, Google executives decided to proceed with the launch anyway, overruling an unsympathetic risk assessment report conducted by its AI ethics team.[46] After Pichai suddenly laid off 12,000 employees later that month due to slowing revenue growth, remaining workers shared memes and snippets of their humorous exchanges with Bard soliciting its "opinion" on the layoffs.[47] Google employees began testing a more sophisticated version of Bard with larger parameters, dubbed "Big Bard", in mid-March.[48]

Launch

Google opened up early access for Bard on March 21, 2023, in a limited capacity, allowing users in the U.S. and UK to join a waitlist. Unlike Microsoft's approach with Bing Chat, Bard was launched as a standalone web application featuring a text box and a disclaimer that the chatbot "may display inaccurate or offensive information that doesn't represent Google's views". Three responses are then provided to each question, with users prompted to submit feedback on the usefulness of each answer. Google vice presidents Sissie Hsiao and Eli Collins framed Bard as a complement to Google Search and stated that the company had not determined how to make the service profitable.[49][50][51] Among those granted early access were those enrolled in Google's "Pixel Superfans" loyalty program,[52] users of its Pixel and Nest devices, and Google One subscribers.[53]

Bard is trained by third-party contractors hired by Google, including Appen and Accenture workers, whom Business Insider and Bloomberg News reported were placed under extreme pressure, overworked, and underpaid.[54][55] Bard is also trained on data from publicly available sources, which Google disclosed by amending its privacy policy.[56] Shortly after Bard's initial launch, Google reorganized the team behind Google Assistant, the company's virtual assistant, to focus on Bard instead.[57] Google researcher Jacob Devlin resigned from the company after claiming that Bard had surreptitiously leveraged data from ChatGPT;[58] Google denied the allegations.[59] Meanwhile, a senior software engineer at the company published an internal memo warning that Google was falling behind in the AI "arms race", not to OpenAI but to independent researchers in open-source communities.[60] Pichai revealed on March 31 that the company intended to "upgrade" Bard by basing it on PaLM, a newer and more powerful LLM from Google, rather than LaMDA.[61] The same day, Krawczyk announced that Google had added "math and logic capabilities" to Bard.[62] Bard gained the ability to assist in coding in April, being compatible with more than 20 programming languages at launch.[63][64] Microsoft also began running advertisements in the address bar of a developer build of the Edge browser, urging users to try Bing whenever they visit the Bard web app.[65] Google is working to integrate Bard into its ChromeOS operating system and Pixel devices.[66][67]

Updates

Bard took center stage during the annual Google I/O keynote in May 2023,[68] with Pichai and Hsiao announcing a series of updates to Bard, including the adoption of PaLM 2, integration with other Google products and third-party services, expansion to 180 countries, support for additional languages, and new features.[69] In a stark contrast to previous years, the Google Assistant was barely mentioned during the event.[68] The expanded rollout did not include any nations in the European Union (EU), possibly reflecting concerns about compliance with the General Data Protection Regulation.[70] Those with Google Workspace accounts also gained access to the service.[71] Google attempted to launch Bard in the EU in June, but was blocked by the Irish Data Protection Commission, who requested for a "data protection impact assessment" from the company.[72] In July, Google launched Bard in the EU and Brazil, added support for dozens of new languages, and introduced multiple new personalization and productivity features.[73][74] An invite-only chatroom ("server") on Discord was created in July, consisting of users who heavily use Bard. Over the next few months, the chatroom was flooded with comments questioning the usefulness of Bard.[75]

Reflecting on Bard's launch in an interview with Wired in September, Pichai acknowledged that Google had been "cautious" to release LaMDA because of "the responsibility that comes with getting it right", complimenting OpenAI for ChatGPT's launch and firing back at Nadella's comment about making Google dance.[76] Google released a major update to the chatbot later that month, integrating it into many of its products through "extensions", adding a button to fact-check AI-generated responses through Google Search, and allowing users to share conversation threads.[77] Google also introduced the "Google-Extended" web crawler as part of its search engine's robots.txt indexing file to allow web publishers to opt-out of allowing Bard to scan them for training.[78] Online users later discovered that Google Search was indexing Bard conversation threads on which users had enabled sharing. Google stated that this was an error and quickly moved to rectify the leaks.[79]

In October, during the company's annual Made by Google event in which it announced the Pixel 8 series and the Pixel Watch 2, Hsiao unveiled "Assistant with Bard", an upgraded version of the Google Assistant which was deeply integrated with Bard, following in the footsteps of Amazon's approach with Alexa.[80] When the U.S. Copyright Office solicited public comment on potential new regulation on generative AI technologies, Google joined with OpenAI and Microsoft in arguing that the responsibility for generating copyrighted material lay with the user, not the developer.[81] Accenture contractors voted to join the Alphabet Workers Union in November, in protest of suboptimal working conditions,[82] while the company filed a lawsuit in the U.S. District Court for the Northern District of California against a group of unidentified scammers who had been advertising malware disguised as a downloadable version of Bard.[83][84]

Gemini

Шаблон:Main On December 6, 2023, Google announced Gemini, a multimodal and more powerful LLM touted as the company's "largest and most capable AI model".[85][86] A specially tuned version of the mid-tier Gemini Pro was integrated into Bard, while the larger Gemini Ultra was set to power "Bard Advanced" in 2024.[87][88] The Wall Street Journal reported that Bard was then averaging around 220 million monthly visitors.[89] Google ended its contract with Appen in January 2024,[90] while Bard gained the long-awaited ability to generate images the next month, powered by Google Brain's Imagen 2 text-to-image model.[91]

Reception

Bard received mixed reviews upon its initial release.[92] James Vincent of The Verge found Bard faster than ChatGPT and Bing Chat, but noted that the lack of Bing-esque footnotes was "both a blessing and a curse",[51] encouraging Google to be bolder when experimenting with AI.[93] His colleague David Pierce was unimpressed by its uninteresting and sometimes inaccurate responses,[94] adding that despite Google's insistence that Bard was not a search engine, its user interface resembled that of one, which could cause problems for Google.[95] Cade Metz of The New York Times described Bard as "more cautious" than ChatGPT,[96] while Shirin Ghaffary of Vox called it "dry and uncontroversial" due to the reserved nature of its responses.[97]

The Washington Post columnist Geoffrey A. Fowler found Bard a mixed bag, noting that it acted cautiously but could show Internet-influenced bias.[98] Writing for ZDNET, Sabrina Ortiz believed ChatGPT and Bing Chat were "more capable overall" in comparison to Bard,[99] while Wired journalist Lauren Goode found her conversation with Bard "the most bizarre" of the three.[100] After the introduction of extensions, The New York TimesШаблон:' Kevin Roose found the update underwhelming and "a bit of a mess",[101] while Business InsiderШаблон:'s Lakshmi Varanasi found that Bard often leaned more into flattery than facts.[102]

In a 60 Minutes conversation with Hsiao, Google senior vice president James Manyika, and Pichai, CBS News correspondent Scott Pelley found Bard "unsettling".[103] Associate professor Ethan Mollick of the Wharton School of the University of Pennsylvania was underwhelmed by Bard's artistic ineptitude.[104] The Times later conducted a test with ChatGPT and Bard regarding their ability to handle tasks expected of human assistants, and concluded that ChatGPT's performance was vastly superior to that of Bard.[105] NewsGuard, a tool that rates the credibility of news articles, found that Bard was more skilled at debunking known conspiracy theories than ChatGPT.[106]

See also

References

Шаблон:Reflist

Further reading

Шаблон:Refbegin

Шаблон:Refend

External links

Шаблон:Google LLC Шаблон:Differentiable computing Шаблон:Natural language processing

  1. Ошибка цитирования Неверный тег <ref>; для сносок ChatGPTForbes не указан текст
  2. Ошибка цитирования Неверный тег <ref>; для сносок ChatGPTVerge не указан текст
  3. Ошибка цитирования Неверный тег <ref>; для сносок SeriousThreat не указан текст
  4. Ошибка цитирования Неверный тег <ref>; для сносок CodeRed не указан текст
  5. Ошибка цитирования Неверный тег <ref>; для сносок PichaiCodeRed не указан текст
  6. Ошибка цитирования Неверный тег <ref>; для сносок LarrySergey не указан текст
  7. Ошибка цитирования Неверный тег <ref>; для сносок Code не указан текст
  8. Ошибка цитирования Неверный тег <ref>; для сносок LaMDA не указан текст
  9. Ошибка цитирования Неверный тег <ref>; для сносок LLM не указан текст
  10. Ошибка цитирования Неверный тег <ref>; для сносок Unreleased не указан текст
  11. Ошибка цитирования Неверный тег <ref>; для сносок AllHandsCNBC не указан текст
  12. Ошибка цитирования Неверный тег <ref>; для сносок AllHandsVerge не указан текст
  13. Ошибка цитирования Неверный тег <ref>; для сносок DeepMind не указан текст
  14. Ошибка цитирования Неверный тег <ref>; для сносок ApprenticeBardCNBC не указан текст
  15. Ошибка цитирования Неверный тег <ref>; для сносок ApprenticeBardAP не указан текст
  16. Ошибка цитирования Неверный тег <ref>; для сносок InvestorCall не указан текст
  17. 17,0 17,1 17,2 Ошибка цитирования Неверный тег <ref>; для сносок AnnounceLATimes не указан текст
  18. 18,0 18,1 18,2 Ошибка цитирования Неверный тег <ref>; для сносок AnnounceWSJ не указан текст
  19. 19,0 19,1 19,2 Ошибка цитирования Неверный тег <ref>; для сносок AnnounceForbes не указан текст
  20. 20,0 20,1 Ошибка цитирования Неверный тег <ref>; для сносок PichaiMemo не указан текст
  21. Ошибка цитирования Неверный тег <ref>; для сносок KrawczykFortune не указан текст
  22. Ошибка цитирования Неверный тег <ref>; для сносок KrawczykCNBC не указан текст
  23. Ошибка цитирования Неверный тег <ref>; для сносок BillionDollar не указан текст
  24. Ошибка цитирования Неверный тег <ref>; для сносок Atlas не указан текст
  25. Ошибка цитирования Неверный тег <ref>; для сносок EtymologyNYT не указан текст
  26. Ошибка цитирования Неверный тег <ref>; для сносок EtymologyWired не указан текст
  27. 27,0 27,1 Ошибка цитирования Неверный тег <ref>; для сносок AIBattleVerge не указан текст
  28. Ошибка цитирования Неверный тег <ref>; для сносок AIBattleBarrons не указан текст
  29. 29,0 29,1 Ошибка цитирования Неверный тег <ref>; для сносок CatchUpRecode не указан текст
  30. Ошибка цитирования Неверный тег <ref>; для сносок CatchUpInformation не указан текст
  31. Ошибка цитирования Неверный тег <ref>; для сносок CatchUpWaPo не указан текст
  32. Ошибка цитирования Неверный тег <ref>; для сносок Dance не указан текст
  33. Ошибка цитирования Неверный тег <ref>; для сносок SecretWars не указан текст
  34. Ошибка цитирования Неверный тег <ref>; для сносок AIWarsGuardian не указан текст
  35. Ошибка цитирования Неверный тег <ref>; для сносок AIWarsRecode не указан текст
  36. Ошибка цитирования Неверный тег <ref>; для сносок AIWarsWaPo не указан текст
  37. Ошибка цитирования Неверный тег <ref>; для сносок WebbSydney не указан текст
  38. Ошибка цитирования Неверный тег <ref>; для сносок WebbWSJ не указан текст
  39. Ошибка цитирования Неверный тег <ref>; для сносок WebbReuters не указан текст
  40. Ошибка цитирования Неверный тег <ref>; для сносок WebbPCMag не указан текст
  41. Ошибка цитирования Неверный тег <ref>; для сносок Memgen не указан текст
  42. Ошибка цитирования Неверный тег <ref>; для сносок Chaos не указан текст
  43. Ошибка цитирования Неверный тег <ref>; для сносок Hennessy не указан текст
  44. Ошибка цитирования Неверный тег <ref>; для сносок Dogfood не указан текст
  45. Ошибка цитирования Неверный тег <ref>; для сносок Raghavan не указан текст
  46. Ошибка цитирования Неверный тег <ref>; для сносок Ethics не указан текст
  47. Ошибка цитирования Неверный тег <ref>; для сносок Layoffs не указан текст
  48. Ошибка цитирования Неверный тег <ref>; для сносок BigBard не указан текст
  49. Ошибка цитирования Неверный тег <ref>; для сносок WaitlistNYT не указан текст
  50. Ошибка цитирования Неверный тег <ref>; для сносок WaitlistWaPo не указан текст
  51. 51,0 51,1 Ошибка цитирования Неверный тег <ref>; для сносок WaitlistVerge не указан текст
  52. Ошибка цитирования Неверный тег <ref>; для сносок PixelSuperfans не указан текст
  53. Ошибка цитирования Неверный тег <ref>; для сносок PixelNestOne не указан текст
  54. Ошибка цитирования Неверный тег <ref>; для сносок ContractorsBI не указан текст
  55. Ошибка цитирования Неверный тег <ref>; для сносок ContractorsBloomberg не указан текст
  56. Ошибка цитирования Неверный тег <ref>; для сносок PublicData не указан текст
  57. Ошибка цитирования Неверный тег <ref>; для сносок Assistant не указан текст
  58. Ошибка цитирования Неверный тег <ref>; для сносок DevlinClaims не указан текст
  59. Ошибка цитирования Неверный тег <ref>; для сносок DevlinDenial не указан текст
  60. Ошибка цитирования Неверный тег <ref>; для сносок OpenSource не указан текст
  61. Ошибка цитирования Неверный тег <ref>; для сносок PaLM не указан текст
  62. Ошибка цитирования Неверный тег <ref>; для сносок Math не указан текст
  63. Ошибка цитирования Неверный тег <ref>; для сносок CodingReuters не указан текст
  64. Ошибка цитирования Неверный тег <ref>; для сносок CodingTC не указан текст
  65. Ошибка цитирования Неверный тег <ref>; для сносок Edge не указан текст
  66. Ошибка цитирования Неверный тег <ref>; для сносок ChromeOS не указан текст
  67. Ошибка цитирования Неверный тег <ref>; для сносок Pixel не указан текст
  68. 68,0 68,1 Ошибка цитирования Неверный тег <ref>; для сносок CuriousCase не указан текст
  69. Ошибка цитирования Неверный тег <ref>; для сносок IO2023 не указан текст
  70. Ошибка цитирования Неверный тег <ref>; для сносок EUNoLaunch не указан текст
  71. Ошибка цитирования Неверный тег <ref>; для сносок Workspace не указан текст
  72. Ошибка цитирования Неверный тег <ref>; для сносок EUDelay не указан текст
  73. Ошибка цитирования Неверный тег <ref>; для сносок JulyUpdateBBC не указан текст
  74. Ошибка цитирования Неверный тег <ref>; для сносок JulyUpdateWSJ не указан текст
  75. Ошибка цитирования Неверный тег <ref>; для сносок Discord не указан текст
  76. Ошибка цитирования Неверный тег <ref>; для сносок Google25 не указан текст
  77. Ошибка цитирования Неверный тег <ref>; для сносок Extensions не указан текст
  78. Ошибка цитирования Неверный тег <ref>; для сносок Extended не указан текст
  79. Ошибка цитирования Неверный тег <ref>; для сносок Leaks не указан текст
  80. Ошибка цитирования Неверный тег <ref>; для сносок AssistantWithBard не указан текст
  81. Ошибка цитирования Неверный тег <ref>; для сносок Union не указан текст
  82. Ошибка цитирования Неверный тег <ref>; для сносок MalwareReuters не указан текст
  83. Ошибка цитирования Неверный тег <ref>; для сносок MalwareTime не указан текст
  84. Ошибка цитирования Неверный тег <ref>; для сносок GeminiCNN не указан текст
  85. Ошибка цитирования Неверный тег <ref>; для сносок GeminiCNBC не указан текст
  86. Ошибка цитирования Неверный тег <ref>; для сносок GeminiArs не указан текст
  87. Ошибка цитирования Неверный тег <ref>; для сносок GeminiAP не указан текст
  88. Ошибка цитирования Неверный тег <ref>; для сносок GeminiWSJ не указан текст
  89. Ошибка цитирования Неверный тег <ref>; для сносок Appen не указан текст
  90. Ошибка цитирования Неверный тег <ref>; для сносок Imagen не указан текст
  91. Ошибка цитирования Неверный тег <ref>; для сносок Reviews не указан текст
  92. Ошибка цитирования Неверный тег <ref>; для сносок Experimentation не указан текст
  93. Ошибка цитирования Неверный тег <ref>; для сносок VergeReview не указан текст
  94. Ошибка цитирования Неверный тег <ref>; для сносок NotSearch не указан текст
  95. Ошибка цитирования Неверный тег <ref>; для сносок NYTReview не указан текст
  96. Ошибка цитирования Неверный тег <ref>; для сносок VoxReview не указан текст
  97. Ошибка цитирования Неверный тег <ref>; для сносок RightWrongWeird не указан текст
  98. Ошибка цитирования Неверный тег <ref>; для сносок BadWay не указан текст
  99. Ошибка цитирования Неверный тег <ref>; для сносок Bizarre не указан текст
  100. Ошибка цитирования Неверный тег <ref>; для сносок Erratic не указан текст
  101. Ошибка цитирования Неверный тег <ref>; для сносок Flattery не указан текст
  102. Ошибка цитирования Неверный тег <ref>; для сносок 60Minutes не указан текст
  103. Ошибка цитирования Неверный тег <ref>; для сносок Testers не указан текст
  104. Ошибка цитирования Неверный тег <ref>; для сносок HumanAssistant не указан текст
  105. Ошибка цитирования Неверный тег <ref>; для сносок Conspiracy не указан текст