YAML Metadata
Warning:
empty or missing yaml metadata in repo card
(https://huggingface.co/docs/hub/model-cards#model-card-metadata)
Prompt
{input}
{output}
Example: of entry used for finetuning
Your task is to write an API request for a new schema given the API reference and an example. The user command is: "Get me the details of 2 music tracks that are similar to the given vector." Here is the API reference for a query that will help with this command and an example of how to use it: {Get {JeopardyQuestion (limit: 2,nearVector: {vector: [-0.0125526935, -0.021168863, -0.01076519, ...]}}}}} Could you please formulate this query for the following schema? {"class": "Track","description": "A music track.","properties": [{"name": "trackId","dataType": ["uuid"],"description": "A unique identifier for each track.","moduleConfig": {"text2vec-transformers": {"skip": true,"vectorizeClassName": false,"vectorizePropertyName": false}}{"name": "title","dataType": ["text"],"description": "The title of the track.","moduleConfig": {"text2vec-transformers": {"skip": false,"vectorizeClassName": false,"vectorizePropertyName": false}}{"name": "duration","dataType": ["int"],"description": "The duration of the track in seconds.","moduleConfig": {"text2vec-transformers": {"skip": true,"vectorizeClassName": false,"vectorizePropertyName": false}}{"name": "artist","dataType": ["Artist"],"description": "The artist of the track.","moduleConfig": {"text2vec-transformers": {"skip": true,"vectorizeClassName": false,"vectorizePropertyName": false}}{"name": "album","dataType": ["Album"],"description": "The album of the track.","moduleConfig": {"text2vec-transformers": {"skip": true,"vectorizeClassName": false,"vectorizePropertyName": false}}}} VERY IMPORTANT! Please only output the GraphQL for the query and nothing else!
{ Get { Track ( limit: 2, nearVector: { vector: [-0.0125526935, -0.021168863, -0.01076519, ...] } ) { trackId title duration artist { artistId name } album { albumId title } } }}
- Downloads last month
- 10
This model does not have enough activity to be deployed to Inference API (serverless) yet. Increase its social
visibility and check back later, or deploy to Inference Endpoints (dedicated)
instead.