Introducing Evaluations, a powerful feature designed to enable you to effortlessly test and compare a selection of AI models against your datasets.
Whether you're fine-tuning models or evaluating performance metrics, Oxen evaluations simplifies the process, allowing you to quickly and easily run prompts through an entire dataset.
Once you're happy with the results, output the resulting dataset to a new file, another branch, or directly as a new commit.
4833fdf4-332f-4280-817b-1bbb60903baa

ox
2 weeks agoTranslate the user query to a sql statement given the table schema. Return only the SQL and nothing else no markdown. Schema: {schema} Query: {query}
bbacf907-8971-45d9-b4c4-90161606d12e

ox
3 weeks agoclassify the query into "has_date" or "no_date". reply with one word {query}
main
c8026cdb-6a01-40bf-b532-57ceb0f3200b

ox
3 weeks agoCompare the following SQL statements given the database table to see if they are equivalent. If they are not the same, give a reason as to why. Format your response with two xml tags, one for the reasoning, and one a true or false statement indicating whether or not the statements are the same. Do not include any markdown surrounding the xml. For example: <reason> The reason the statements differ. </reason> <answer> true or false </answer> Are these two SQL statements equivalent given the schema: Schema: {schema} Statement 1: {sql} Statement 2: {prediction}
8855a3b6-d78f-47f7-b587-37742443f693

ox
3 weeks agoCompare the following SQL statements given the database table to see if they are equivalent. If they are not the same, give a reason as to why. Format your response with two xml tags, one for the reasoning, and one a true or false statement indicating whether or not the statements are the same. Do not include any markdown surrounding the xml. For example: <reason> The reason the statements differ. </reason> <answer> true or false </answer> Are these two SQL statements equivalent given the schema: Schema: {schema} Statement 1: {sql} Statement 2: {prediction}
211c9d8d-5450-4afa-a2be-bf75fa802218

ox
3 weeks agoWrite a SQL statement that is equivalent to the natural language user query below given the schema in the format of a CREATE TABLE SQL statement. Assume the table is called "df". DO NOT give any preamble or extra characters or markdown just the SQL query in plain text. Make sure the SQL query is on one line. Schema: {schema} User Query: {query} SQL Query:
ff98baff-87ba-4a8b-80e0-84180930d60f

ox
3 weeks agoWrite a SQL statement that is equivalent to the natural language user query below given the schema in the format of a CREATE TABLE SQL statement. Assume the table is called "df". DO NOT give any preamble or extra characters or markdown just the SQL query in plain text. Make sure the SQL query is on one line. Schema: {schema} User Query: {query} SQL Query:
error An exception occurred indexing, getting dataframe and running evaluation: %Req.TransportError{reason: :closed} 200 rows30564 tokens$ 0.1080 2 iterations
6c10db23-ffb9-4b02-992f-5515440c818c

ox
3 weeks agoWrite a SQL statement that is equivalent to the natural language user query below. You are given the schema in the format of a CREATE TABLE SQL statement. Assume the table is called "df". DO NOT give any preamble or extra characters or markdown just the SQL query in plain text. Make sure the SQL query is on one line. Schema: {schema} User Query: {query} SQL Query:
main
N/A
error An exception occurred indexing, getting dataframe and running evaluation: %Req.TransportError{reason: :closed} 500 rows105981 tokens$ 0.0848 3 iterations
3fd776ec-6942-43d1-b56f-b4def7d67c13

ox
3 weeks agoWrite a SQL statement that is equivalent to the natural language user query. You are given the schema in the format of a CREATE TABLE SQL statement. Assume the table is called "df". DO NOT give any preamble or extra characters or markdown just the SQL query in plain text. Make sure the SQL query is on one line. Schema: {schema} User Query: {query} SQL Query:
main
ba7fe81e-be16-4413-91d3-fa092ed4df28

ox
4 weeks agoCompare the following SQL statements given the database table to see if they are equivalent. If they are not the same, give a reason as to why. Format your response with two xml tags, one for the reasoning, and one a true or false statement indicating whether or not the statements are the same. Do not include any markdown surrounding the xml. For example: <reason> The reason the statements differ. </reason> <answer> true or false </answer> Are these two SQL statements equivalent given the schema: Schema: {schema} Statement 1: {sql} Statement 2: {prediction}
error An exception occurred indexing, getting dataframe and running evaluation: %Req.TransportError{reason: :closed} 200 rows68095 tokens$ 0.0135 2 iterations
705e9f92-b4e5-4692-9465-4fd2caeb9f2b

ox
4 weeks agoCompare the following SQL statements given the database table to see if they are equivalent. If they are not the same, give a reason as to why. Format your response with two xml tags, one for the reasoning, and one a true or false statement indicating whether or not the statements are the same. Do not include any markdown surrounding the xml. For example: <reason> The reason the statements differ. </reason> <answer> true or false </answer> Are these two SQL statements equivalent given the schema: Schema: {schema} Statement 1: {sql} Statement 2: {prediction}
64e34075-866e-4126-a2d7-76539d44da2d

ox
4 weeks agoWrite a SQL statement that is equivalent to the natural language user query below given the schema in the format of a CREATE TABLE SQL statement. Assume the table is called "df". DO NOT give any preamble or extra characters or markdown just the SQL query in plain text. Make sure the SQL query is on one line. Schema: {schema} User Query: {query} SQL Query:
main
main
0784f09b-b22a-48aa-aaec-82a53c4ffb70

ox
4 weeks agoCompare the following SQL statements given the database table to see if they are equivalent. If they are not the same, give a reason as to why. Format your response with two xml tags, one for the reasoning, and one a true or false statement indicating whether or not the statements are the same. Do not include any markdown surrounding the xml. For example: <reason> The reason the statements differ. </reason> <answer> true or false </answer> Are these two SQL statements equivalent given the schema: Schema: {schema} Statement 1: {sql} Statement 2: {prediction}
8857547b-8b58-49e7-8ab0-6ddd9b66e532

ox
4 weeks agoCompare the following SQL statements given the database table to see if they are equivalent. If they are not the same, give a reason as to why. Format your response with two xml tags, one for the reasoning, and one a true or false statement indicating whether or not the statements are the same. Do not include any markdown surrounding the xml. For example: <reason> The reason the statements differ. </reason> <answer> true or false </answer> Are these two SQL statements equivalent given the schema: Schema: {schema} Statement 1: {sql} Statement 2: {prediction}
5c8cd72a-6cd2-45de-8d11-82c44741cfdc

ox
4 weeks agoWrite a SQL statement that is equivalent to the natural language user query below given the schema in the format of a CREATE TABLE SQL statement. Assume the table is called "df". DO NOT give any preamble or extra characters or markdown just the SQL query in plain text. Make sure the SQL query is on one line. Schema: {schema} User Query: {query} SQL Query:
8bca8680-9c3c-48f5-8755-20b34af4063a

ox
4 weeks agoCompare the following SQL statements given the database table to see if they are equivalent. If they are not the same, give a reason as to why. Format your response with two xml tags, one for the reasoning, and one a true or false statement indicating whether or not the statements are the same. Do not include any markdown surrounding the xml. For example: <reason> The reason the statements differ. </reason> <answer> true or false </answer> Are these two SQL statements equivalent given the schema: Schema: {schema} Statement 1: {sql} Statement 2: {prediction}
c387a9df-596a-4552-a944-b5c1a191ff31

ox
4 weeks agoCompare the following SQL statements given the database table to see if they are equivalent. If they are not the same, give a reason as to why. Format your response with two xml tags, one for the reasoning, and one a true or false statement indicating whether or not the statements are the same. Do not include any markdown surrounding the xml. For example: <reason> The reason the statements differ. </reason> <answer> true or false </answer> Are these two SQL statements equivalent given the schema: Schema: {schema} Statement 1: {sql} Statement 2: {prediction}
87362804-02ca-4391-93be-f45739087e04

ox
4 weeks agoCompare the following SQL statements given the database table to see if they are equivalent. If they are not the same, give a reason as to why. Format your response with two xml tags, one for the reasoning, and one a true or false statement indicating whether or not the statements are the same. Do not include any markdown surrounding the xml. For example: <reason> The reason the statements differ. </reason> <answer> true or false </answer> Are these two SQL statements equivalent given the schema: Schema: {schema} Statement 1: {sql} Statement 2: {prediction}
9a7c84ae-e782-402c-af17-c66cbab91c5e

ox
4 weeks agoWrite a SQL statement that is equivalent to the natural language user query below given the schema in the format of a CREATE TABLE SQL statement. Assume the table is called "df". DO NOT give any preamble or extra characters or markdown just the SQL query in plain text. Make sure the SQL query is on one line. Schema: {schema} User Query: {query} SQL Query:
68786e5e-1383-430a-a0b8-cdf5088ab2a2

ox
1 month agoCompare the following SQL statements given the database table to see if they are equivalent. If they are not the same, give a reason as to why. Format your response with two xml tags, one for the reasoning, and one a true or false statement indicating whether or not the statements are the same. For example: <reason> The reason the statements differ. </reason> <answer> true or false </answer> Are these two SQL statements equivalent given the schema: Schema: {schema} Statement 1: {sql} Statement 2: {prediction}
67719af1-b878-4498-8907-68de58673310

ox
1 month agoCompare the following SQL statements given the database table to see if they are equivalent. If they are not the same, give a reason as to why. Format your response with two xml tags, one for the reasoning, and one a true or false statement indicating whether or not the statements are the same. For example: <reason> The reason the statements differ. </reason> <answer> true or false </answer> Are these two SQL statements equivalent given the schema: Schema: {schema} Statement 1: {sql} Statement 2: {prediction}
00278494-61a3-4237-9548-a0808ac1feaa

ox
1 month agoCompare the following SQL statements given the database table to see if they are equivalent. If they are not the same, give a reason as to why. Format your response with two xml tags, one for the reasoning, and one a true or false statement indicating whether or not the statements are the same. For example: <reason> The reason the statements differ. </reason> <answer> true or false </answer> Are these two SQL statements equivalent given the schema: Schema: {schema} Statement 1: {sql} Statement 2: {prediction}
427b9bd9-159c-4275-aaee-3010ed11a394

ox
1 month agoCompare the following SQL statements given the database table to see if they are equivalent. If they are not the same, give a reason as to why. Format your response with two xml tags, one for the reasoning, and one a true or false statement indicating whether or not the statements are the same. For example: <reason> The reason the statements differ. </reason> <answer> true or false </answer> Are these two SQL statements equivalent given the schema: Schema: {schema} Statement 1: {sql} Statement 2: {prediction}
1c2fc383-99ae-4ee0-8875-7e5c6dcf7242

ox
1 month agoWrite a SQL statement that is equivalent to the natural language user query below given the schema in the format column_name:type. Assume the table is called "df". Do not give any preamble or extra characters just the SQL query in plain text. Make sure the SQL query is on one line. Schema: {schema} User Query: {query} SQL Query:
main
53b1ee1c-1761-4309-8c13-7196f8c05d08

ox
1 month agoCompare the following SQL statements given the database table to see if they are equivalent. If they are not the same, give a reason as to why. Format your response with two xml tags, one for the reasoning, and one a true or false statement indicating whether or not the statements are the same. For example: <reason> The reason the statements differ. </reason> <answer> true or false </answer> Are these two SQL statements equivalent given the schema: Schema: {schema} Statement 1: {sql} Statement 2: {prediction}
3bd0d0de-f348-46af-81fc-2265bcac8377

ox
1 month agoYou will be given a user query, a list of CREATE TABLE sql statements, a single table name that the query is interested in, and a corresponding SQL statement. You will do several transformations on the input. 1) Extract the the single CREATE TABLE statement that references the given table. 2) Replace the table name with "df" in both the sql statement and the CREATE TABLE statement 3) Format the response into three sections like below <query> The user query goes here </query> <schema> The CREATE TABLE statement goes here on one line </schema> <sql> The SQL statement goes here </sql> Make sure both the schema with the CREATE TABLE statement and the sql statement reference "df" instead of the original table name. Only extract one CREATE TABLE STATEMENT and format it onto a single line without any newlines. Think before responding with the proper xml tags. Here are the original inputs: <query> {instruction} </query> <schema> {input} </schema> <sql> {response} </sql> Your output goes here:
main
N/A
error no case clause matching: {:error, "resource_not_found", 0, 0} 7833 / 7834 rows3640759 tokens$ 0.8710 3 iterations
ff76deda-2ba9-4047-ba15-a063e0de496d

ox
1 month agoDetermine the number of tables used in the following SQL statement given the CREATE TABLE statements below it. Output the table names in a comma separated list. The output format should be xml tags containing the number of tables used and the table names. For example: <num_tables>2</num_tables> <tables>table_1,table_2</tables> {schema} {output}
main
6b31ff74-cc0b-414e-b4f4-3d4913257f5d

ox
2 months agoFormat the following SQL statement properly onto one line. Respond with the formatted SQL statement and nothing else. {output} SQL:
num_tables
num_tables
c1c2168f-d6cb-48cd-b8be-6333263ee9b8

ox
2 months agoDetermine the number of tables used in the following SQL statement given the CREATE TABLE statements below it. Output the table names in a comma separated list. The output format should be xml tags containing the number of tables used and the table names. For example: <num_tables>2</num_tables> <tables>table_1,table_2</tables> {input} {response}
conflict/main/ox-536
6bd3b681-4ae3-4181-94f2-190e72cd2529

ox
2 months agoDetermine the number of tables used in the following SQL statement given the CREATE TABLE statements below it. Output the table names in a comma separated list. The output format should be xml tags containing the number of tables used and the table names. For example: <num_tables>2</num_tables> <tables>table_1,table_2</tables> {schema} {output}
main
num_tables