Usage
To use our universal classification endpoint, all you need is a text and a statement to evaluate the text against. The API will then return a score between and representing the model’s estimation of the likelihood that the text supports the statement, with a score over indicating a positive classification. As an example, if you wanted to pull out confidentiality clauses from a contract, you could pass our universal classification endpoint the contract alongside the statement “This is a confidentiality clause.”, as shown below (consult our quickstart guide first if you haven’t set up your Isaacus account and API client).response.classifications[0].
chunking_options parameter to null). Typically, these chunks will correspond to individual clauses in the document.
Chunks are stored in the classification.chunks attribute and come with their own text, score, start, and end attributes, with start and end representing the start and end character indices of the chunk in the original text.
classification.score contains the overall classification score of the document. This score is currently set to the largest score of any chunk.
You can think of the score as the classifier’s estimation of the likelihood that the query is supported by the document. A score over indicates a positive classification.
When passing multiple documents to the classifier, you can access each document’s classification via the response.classifications array, which is sorted from highest to lowest classification score. You can use the classification.index attribute to recover the index of documents in the original input array.
Now, let’s print out the results.
Isaacus Query Language (IQL)
In the previous example, we used a simple, plain English query to classify confidentiality clauses. That worked fine for our purposes, but what if you needed to absolutely maximize the accuracy of your classifications? One way is to construct a test dataset and then repeatedly evaluate differently worded queries on that dataset until you find the best one. This is a time-consuming process, but it can yield excellent results. The good news is that, for a whole bunch of legal classification problems, we’ve already done that work for you. Each of our models comes with a set of pre-optimized queries that you can use to classify legal documents with high accuracy and minimal effort. These queries can be accessed using the Isaacus Query Language or IQL. IQL is the world’s first legal AI query language — that is, a query language designed specifically for analyzing legal documents with AI systems. Any statement you can think of, including the one we used earlier, qualifies as an IQL statement. You just need to wrap it in curly brackets like so:{This is a confidentiality clause.}.
To invoke a pre-optimized query template, we can express our query in the format {IS <template name>}. You can find a list of available templates here.
For example, we could’ve invoked the {IS confidentiality clause} template to classify confidentiality clauses in the GitHub terms of service instead of trying to write our own query from scratch. Let’s do that now.
{IS <template name> "<template argument>"}.
For example, if you wanted to identify clauses that specifically obligate the party referred to as “you” in the document, you could use the {IS clause obligating "<party name>"} template like so: {IS clause obligating "You"}.
{IS clause called "<clause name>"} (e.g., {IS clause called "confidentiality"}) or {IS clause that "<clause description>"} (e.g., {IS clause that "imposes a duty of confidentiality"}). We don’t yet have very many templates for non-contractual classifications, however, our models have been trained on an equal mix of contracts, cases and legislation, so you can always write your own queries for anything not covered by an existing template.
In addition to allowing you to invoke query templates, IQL also enables you to string statements together using logical operators like AND, OR, and NOT, as well as the > and < comparison operators and the + operator for averaging.
For example, if we wanted to identify confidentiality clauses that apply to you and you alone, we could use this query: {IS confidentiality clause} AND {IS clause obligating "You"} AND {IS unilateral clause}.