search

MicrosoftDocs / azure-docs

Open source documentation of Microsoft Azure
https://docs.microsoft.com/azure
Creative Commons Attribution 4.0 International
10.3k stars 21.48k forks source link

Please clarify if GPT-35-Turbo should be GPT-3.5-Turbo instead throughout this article #118913

Closed QueryCoordinator closed 10 months ago

QueryCoordinator commented 10 months ago

Hello,

please check if GPT-35-Turbo should be GPT-3.5-Turbo instead throughout this article. Both are used.

Kind regards, Anne H., QC

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

mrbullwinkle commented 10 months ago

The model name in Azure OpenAI is technically “GPT-35-Turbo”.

The model name with regular OpenAI is “GPT-3.5 Turbo.”

These models are essentially equivalent though the first 0301 release did have some unique additional capabilities as far as API usage that was unique between Azure OpenAI and OpenAI.

By convention we have used both names in the docs, but when we are referring specifically to the Azure OpenAI model we tend to use the actual underlying model name since it is not possible to refer to the model by the OpenAI name programmatically with Azure. We would prefer if both names were identical but there is a limitation with Azure Resource Manager not supporting the “.” character.

With that said it looks like some inconsistency has crept into this article with it alternating between different headings. We have been experimenting with using GPT-3.5 Turbo more often particular in headings for SEO reasons, but in general the usage should be consistent. Thanks for calling this out.

QueryCoordinator commented 10 months ago

Hello @mrbullwinkle,

thank you very much for clarifying this. I was thinking something similar myself, but I had to ask in order to have a proper answer for the translator who was going to add the periods into the strings containing "GPT-35-Turbo", although I said that there must be a reason for the two writing styles.

I also appreciate very much the very fast response I get here.

Kind regards, Anne H., QC

SaibabaBalapur-MSFT commented 10 months ago

@mrbullwinkle Thank for your quick response.

@QueryCoordinator We are going to close this thread as resolved but if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.