``` { "preference": "Database", "value": "sqlite3" } ```

but it (or a different model) may later request the user preference using a subtly different key:

``` { "action": "get_user_preference", "preference": "Database System" } ```

If we parse these responses and store them in a standard dictionary, we'll miss the similarity between the two preference keys "Database" and "Database System", whereas with SemanticDictionary, an embedding model would calculate the distance between the embedding vectors corresponding to the the preference keys prior to lookup.

I figured others may have similar needs so I thought I'd package it up for distribution. Hope you find something cool to do with this!