{"id":259,"date":"2025-11-06T12:00:28","date_gmt":"2025-11-06T11:00:28","guid":{"rendered":"https:\/\/ms-associes.com\/?p=259"},"modified":"2026-01-22T12:55:45","modified_gmt":"2026-01-22T11:55:45","slug":"unfair-competition-and-free-riding-on-social-networks-3","status":"publish","type":"post","link":"https:\/\/www.ms-associes.com\/en\/concurrence-deloyale-et-parasitisme-sur-les-reseaux-sociaux-3\/","title":{"rendered":"GPT is not a trademark!"},"content":{"rendered":"<p><strong>You are all familiar with ChatGPT, the famous AI tool developed by OpenAI that can generate text autonomously.<\/strong><\/p>\n\n\n\n<p>However, \u201cChatGPT\u201d is in itself only a term describing the service offered by OpenAI, since it is a chat tool using \u2018Generative Pre-trained Transformer\u201d technology, and whose acronym is none other than \u201cG.P.T. \u201d.<\/p>\n\n\n\n<p>As a result, when OpenAI sought to protect the \u201cGPT\u201d sign it attaches to its \u201cChat\u201d under trademark law in 2022, it encountered numerous obstacles that it had probably not anticipated.<\/p>\n\n\n\n<p>The saga of the \u201cGPT\u201d trademarks began in the United States. OpenAI suffered successive refusals of its \u201cGPT\u201d trademark applications by the United States Patent and Trademark Office (USPTO). Admittedly, following the USPTO's latest refusal in February 2024, OpenAI asked it to reconsider its decision and the proceedings are still ongoing, but the trend towards refusal is not only national, it is more global.<\/p>\n\n\n\n<p>In fact, on 17 October 2025, the Cancellation Division of the European Union Intellectual Property Office (EUIPO) issued four decisions (C 64 174, C 64 300, C 64 301 and C 64 175) concerning the trademarks GPT, GPT-3, GPT-4 and GPT-5 registered by OpenAI, in particular for software and computer services related to artificial intelligence (classes 9 and 42). The EUIPO declared the GPT, GPT-3 and GPT-4 trademarks to be completely invalid and the GPT-5 trademark to be partially invalid.<\/p>\n\n\n\n<p>The EUIPO's reasoning is similar to that of the USPTO: it considers that the acronym \u201cGPT\u201d has become a generic technical term designating a language model (LLM) architecture based on machine learning, which has become a standard in the field of artificial intelligence.<\/p>\n\n\n\n<p>The distinctiveness of a trademark is assessed in relation to the relevant public, i.e. those to whom the trademark is addressed.<\/p>\n\n\n\n<p>The EUIPO refers here to an English-speaking public consisting of IT professionals and specialised users, who would perceive the sign \u201cGPT\u201d as describing a technical feature of the software covered by the protection of that trademark. As such, it is not a distinctive sign but a descriptive sign.<\/p>\n\n\n\n<p>OpenAI put forward several arguments to challenge this distinctiveness, in particular by arguing that the generalisation of the term GPT (Generative Pre-trained Transformer) was subsequent to its trademark applications. However, the EUIPO points out that the term was already in use within the scientific and technical community prior to or at the same time as its trademark applications. As for numbers 3, 4 and 5, they do not have any distinctive character of their own and correspond to version numbers used in IT development.<\/p>\n\n\n\n<p>The nuance introduced by the only partial invalidity of the \u201cGPT-5\u201d trademark relates to the protection of other products that are distinct from the three other trademarks and have no connection with artificial intelligence (e.g. diving equipment, etc.). The EUIPO may therefore partially cancel a trademark when it is not descriptive for some of the goods and\/or services covered, which was the case with the trademark \u201cGPT-5\u201d.<\/p>\n\n\n\n<p>Through these four decisions, the EUIPO thus reiterates that the role of a trademark is to identify the commercial origin of goods and services and that, as such, any attempt to include a technical description is futile.&nbsp;<\/p>\n\n\n\n<p>The direct consequence of the cancellation of these \u201cGPT\u201d trademarks is the lack of protection for the term \u201cGPT\u201d used by OpenAI. As such, if these decisions become final, any competitor will be able to use the term \u201cChatGPT\u201d to offer competing solutions. An appeal is still possible for OpenAI and, given what is at stake, it would be surprising if OpenAI had said its last word in the \u201cGPT\u201d trademark saga.<\/p>\n\n\n\n<p>These EUIPO decisions are an opportunity to recall that, in itself, it is not too complicated to file a trademark, but it is more difficult to file a good trademark that will pass the registration stages and withstand the test of time. Once you have launched your products or services under a trademark, it is difficult to backtrack and change it. It is therefore preferable to anticipate problems as early as the trademark filing stage.<\/p>\n\n\n\n<p><\/p>","protected":false},"excerpt":{"rendered":"<p>Vous connaissez tous ChatGPT, ce c\u00e9l\u00e8bre outil d\u2019IA d\u00e9velopp\u00e9 par OpenAI qui permet de g\u00e9n\u00e9rer du texte de mani\u00e8re autonome. Toutefois, \u00ab ChatGPT \u00bb n\u2019est en soi qu\u2019un terme d\u00e9crivant le service propos\u00e9 par OpenAI, puisqu\u2019il s\u2019agit d\u2019un outil de chat utilisant une technologie \u00ab Generative Pre-trained Transformer \u00bb, qui pourrait se traduire par \u00ab [&hellip;]<\/p>\n","protected":false},"author":3,"featured_media":1898,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[10],"tags":[],"class_list":["post-259","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-publications"],"_links":{"self":[{"href":"https:\/\/www.ms-associes.com\/en\/wp-json\/wp\/v2\/posts\/259","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.ms-associes.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.ms-associes.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.ms-associes.com\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.ms-associes.com\/en\/wp-json\/wp\/v2\/comments?post=259"}],"version-history":[{"count":2,"href":"https:\/\/www.ms-associes.com\/en\/wp-json\/wp\/v2\/posts\/259\/revisions"}],"predecessor-version":[{"id":1891,"href":"https:\/\/www.ms-associes.com\/en\/wp-json\/wp\/v2\/posts\/259\/revisions\/1891"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.ms-associes.com\/en\/wp-json\/wp\/v2\/media\/1898"}],"wp:attachment":[{"href":"https:\/\/www.ms-associes.com\/en\/wp-json\/wp\/v2\/media?parent=259"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.ms-associes.com\/en\/wp-json\/wp\/v2\/categories?post=259"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.ms-associes.com\/en\/wp-json\/wp\/v2\/tags?post=259"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}