explosion/spaCy
1
1
Fork 0
mirror of https://github.com/explosion/spaCy.git synced 2025-04-20 00:51:58 +03:00
Code Issues Packages Projects Releases Wiki Activity

Attempt to fix netlify check fails.

Browse Source
This commit is contained in:
Raphael Mitsch 2023-10-05 12:49:43 +02:00
parent 3ff4d53153
commit affa21ac40
1 changed files with 0 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
website/docs/api/large-language-models.mdx
View File

@ -1027,23 +1027,6 @@ Currently, these models are provided as part of the core library:
To use these models, make sure that you've [set the relevant API](#api-keys)
keys as environment variables.
**⚠️ A note on `spacy.Azure.v1`** Working with Azure OpenAI is slightly
different than working with models from other providers:
- In Azure LLMs have to be made available by creating a _deployment_ of a given
model (e. g. GPT-3.5). This deployment can have an arbitrary name. The `name`
argument, which everywhere else denotes the model name (e. g. `claude-1.0`,
`gpt-3.5`), here denotes the _deployment name_.
- Deployed Azure OpenAI models are reachable via a resource-specific base URL,
usually of the form https://{resource}.openai.azure.com. Hence the URL has to
be specified via the `base_url` argument.
- Azure further expects the _API version_ to be specified. The default value for
this, via the `api_version` argument, is currently `2023-05-15` but may be
updated in the future.
- Finally, since we can't infer information about the model from the deployment
name, `spacy-llm` requires the `model_type` to be set to either
`"completions"` or `"chat"`, depending on whether the deployed model is a
completion or chat model.
#### API Keys {id="api-keys"}