Skip to main content

Structured output with Ollama

I talked about Structured Output before in the context of Semantic Kernel. Structured Outputs is a feature that ensures the model will always generate responses that follow a supplied JSON Schema, so you can process the responses in automated fashion without worrying about getting invalid JSON back.

Recently support for Structured Output was announced by Ollama. In this post I want to show you how you can use this in combination with OllamaSharp, the C# client for Ollama.

Using Structured Ouput in OllamaSharp

Remark: Make sure you have latest Ollama version running on your local machine before you continue.

  • Add the OllamaSharp client to your project:

dotnet add package OllamaSharp

  • Now let’s first define our response model:
  • Afterwards we need to initiate a new OllamaSharp client instance:
  • We create a new request object.
    • Notice that we specify a JSON schema object based on the Recipe model we created earlier
  • If we now invoke the application we get a JSON response back in the provided format:

The full example can be found here: wullemsb/SemanticKernelStructuredOutput at OllamaClient

What about using the Semantic Kernel Ollama connector?

At the moment of writing this blog post, I couldn’t get the Structured Output working when combining Semantic Kernel and Ollama.

I explicitly referenced the correct OllamaSharp version:

And used the Ollama connector:

But when calling the api, I still got a response back in an unstructured format:

More information

Semantic Kernel - Structured output

awaescher/OllamaSharp: The easiest way to use the Ollama API in .NET

Support for 'Structured outputs' · awaescher/OllamaSharp · Discussion #152

Structured outputs · Ollama Blog

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...