Queries a benchmark's prompt ratings — a page of prompts, each with its ranked entries and the pairwise win matrix over them.
Changed onFilters apply to the underlying votes with the standings query's field set. A rating is an entry's standing against the other entries on its prompt, so a participant filter narrows the entries but does not refit, and a prompt with no matching votes yields no entries. groupBy decides what competes: per participant, a participant's images become one entry rated from their pooled wins, and comparisons between its own images are excluded from the rating, both matrices, and responseCount. Grouping never changes which prompts the page holds.
Request
- Base URLhttps://api.rapidata.ai
- URLhttps://api.rapidata.ai/benchmark/{benchmarkId}/prompt-ratings/query
- AuthOpenID Connect (https://auth.rapidata.ai/.well-known/openid-configuration, scopes: openid, profile, email, offline_access, api)
Path parameters
The id of the benchmark.
Query parameters
Whether to weight ratings by annotator reliability.
What each rated entry of a prompt represents.
What each rated entry represents.
The 1-based page index.
The number of items per page.
Sort fields. Prefix with - for descending order (e.g. -created_at).
Filter by country.
Filter by language.
Filter by gender.
Filter by age_bucket.
Filter by occupation.
Filter by tags.
Filter by participant_id.
Filter by leaderboard_id.
Filter by run_id.
Filter by prompt_identifier.
Filter by voted_at.
How to combine the field filters: "and" (default) requires every filter to match, "or" requires any of them to match.
Response
OK
Changes
- info
added the optional property
////////////////to the response with the status - info
added the optional property
/////////////////to the response with the status
- info
- breaking
the
//////////////////////response's property format changed fromdate-timeto no format for status - breaking
the
//////////////////////response's property format changed fromdate-timeto no format for status - breaking
the
//////////////////////response's property format changed fromdate-timeto no format for status - breaking
the
//////////////////////response's property format changed fromdate-timeto no format for status - breaking
the
///////////////////////response's property format changed fromdate-timeto no format for status - breaking
the
///////////////////////response's property format changed fromdate-timeto no format for status - breaking
the
///////////////////////response's property format changed fromdate-timeto no format for status - breaking
the
///////////////////////response's property format changed fromdate-timeto no format for status - info
the
//////////////////////response's property pattern^-?(\d+\.)?\d{2}:\d{2}:\d{2}(\.\d{1,7})?$was added for the status - info
the
//////////////////////response's property pattern^-?(\d+\.)?\d{2}:\d{2}:\d{2}(\.\d{1,7})?$was added for the status - info
the
//////////////////////response's property pattern^-?(\d+\.)?\d{2}:\d{2}:\d{2}(\.\d{1,7})?$was added for the status - info
the
//////////////////////response's property pattern^-?(\d+\.)?\d{2}:\d{2}:\d{2}(\.\d{1,7})?$was added for the status - info
the
///////////////////////response's property pattern^-?(\d+\.)?\d{2}:\d{2}:\d{2}(\.\d{1,7})?$was added for the status - info
the
///////////////////////response's property pattern^-?(\d+\.)?\d{2}:\d{2}:\d{2}(\.\d{1,7})?$was added for the status - info
the
///////////////////////response's property pattern^-?(\d+\.)?\d{2}:\d{2}:\d{2}(\.\d{1,7})?$was added for the status - info
the
///////////////////////response's property pattern^-?(\d+\.)?\d{2}:\d{2}:\d{2}(\.\d{1,7})?$was added for the status
- breaking