Sophia Luo

Getting data to train and evaluate your large language models has never been more Rapid! Introducing&hellip;Scale&rsquo;s Large Language Model Toolkit!&nbsp;
<img src="https://drive.tiny.cloud/1/0lbhu31lrngl0y5eo8e6p0jckqgeikc94mnkaig43yuahupv/6b85a60e-339a-46fd-bcb7-ce485df871de" width="624" height="391">
We&rsquo;ve developed expedited workflows to help you set up projects within Rapid, Scale&rsquo;s self-serve data labeling tool. <a href="https://scale.com/rapid">Sign up</a> today to try it out and get $20 in free credits.
After signing up, you&rsquo;ll see all of our available project templates and our &ldquo;LLM Training Toolkit&rdquo; front and center. We&rsquo;ve divided our LLM toolkit into three buckets according to different workflows:&nbsp;
<ol>
<li dir="ltr" aria-level="1">
Demonstration Data: Collect human-generated text over various domains and use cases
</li>
<li dir="ltr" aria-level="1">
Comparison Data: Evaluate your model outputs with human feedback
</li>
<li dir="ltr" aria-level="1">
Trust &amp; Safety: Align your model to produce factually correct and safe content&nbsp;
</li>
</ol>
Demonstration Data&nbsp;
We have two subcategories of project types under the &ldquo;Demonstration Data&rdquo; bucket.&nbsp;
<img src="https://drive.tiny.cloud/1/0lbhu31lrngl0y5eo8e6p0jckqgeikc94mnkaig43yuahupv/09a3aa9a-f570-4ee7-93f8-42d2f47a9795" width="624" height="319">
(1) InstructGPT-style presets: Each of these comes with expert-written instructions, a preset taxonomy with the ability to add a customization section for your specific use case, the ability to upload your own prompts or have Scale create them for you, and a pre-trained workforce that has significant experience in these types of prompts. Check out Section 3.4 of the&nbsp;<a href="https://arxiv.org/pdf/2203.02155.pdf">InstructGPT paper</a> for yourself! 😉
(2) Demonstration corrections: If you have demonstrations or model outputs that need corrections, we can also assist you. Just upload your data or hook up your model endpoint and setup your taxonomy accordingly so that our labelers can get that done for you quickly.&nbsp;
<img src="https://drive.tiny.cloud/1/0lbhu31lrngl0y5eo8e6p0jckqgeikc94mnkaig43yuahupv/ef708a53-23de-49b1-ac2c-f0b744870c68">
Comparison Data&nbsp;
With our workflows, you can easily customize comparison annotation projects and quickly scale to production. You can ask a labeler to rank, rate on a Likert scale, and classify model outputs. You can either upload these model outputs or configure a model endpoint for labelers to interact with as they are making the comparisons.&nbsp;
<img src="https://drive.tiny.cloud/1/0lbhu31lrngl0y5eo8e6p0jckqgeikc94mnkaig43yuahupv/7eeab0fb-3f99-4b29-821e-5dcff793cfdb">
<img src="https://drive.tiny.cloud/1/0lbhu31lrngl0y5eo8e6p0jckqgeikc94mnkaig43yuahupv/d27084b0-472c-417d-89e0-ea1364ef2e9f">
Trust &amp; Safety&nbsp;
Aligning your models with Rapid speed has never been easier. With our expertise and specialized workforce, we can work with you to identify problematic model output.&nbsp;
We support several use cases, including Grounded Generation, Red Teaming, Completion Citation, and Research-Based Correction.&nbsp;
<ul>
<li dir="ltr" aria-level="1">
Grounded Generation: Ask a labeler to research or read certain sources to verify uploaded model output.
</li>
<li dir="ltr" aria-level="1">
Red Teaming*: Provide an endpoint for labelers to chat with and elicit unsafe model outputs.&nbsp;
</li>
<li dir="ltr" aria-level="1">
Completion Citation*: Ask a labeler to attribute various phrases to sources that the information came from.&nbsp;
</li>
<li dir="ltr" aria-level="1">
Research-Based Correction*: Upload model output for labelers to find better sources for, edit/rewrite completions given any linked sources, add/edit/remove missing citations, etc.&nbsp;&nbsp;&nbsp;
</li>
</ul>
*Note: Use cases marked with * are currently not available via our self-serve platform. If you are interested, please contact sales to learn more.&nbsp;
For our Grounded Generation use case, we offer two self-serve, popular verification methods.
(1) Multi-class Classification: This involves selecting all error classes that pertain to the text via confidence-based consensus.&nbsp;
(2) Named Entity Recognition:&nbsp; This involves highlighting spans of erroneous text and indicating the relevant error types for each span.
<img src="https://drive.tiny.cloud/1/0lbhu31lrngl0y5eo8e6p0jckqgeikc94mnkaig43yuahupv/a35f53ff-4fae-48e1-b8f1-674fbcf3f752">
<img src="https://drive.tiny.cloud/1/0lbhu31lrngl0y5eo8e6p0jckqgeikc94mnkaig43yuahupv/079d3f20-4345-4797-a4e3-31ba66781b0b"> And this is just the beginning! Our toolkit is constantly expanding, and we are excited to continuously be solving some of the world&rsquo;s hardest data annotation problems. Not seeing what you&rsquo;re looking for in the toolkit today or have other questions? Email us at: scale_rapid@scale.com.

Learn how to collect human-generated text, evaluate your model outputs with human feedback, and align your model to produce factually correct and safe content. 

Getting data to train and evaluate large language models (LLMs) has never been easier

Introducing: Scale’s Large Language Model Toolkit

When setting up a new machine learning (ML) system, collecting and annotating data can be a time-consuming process that requires a significant upfront investment. Since data quality is strongly correlated with ML model performance, it’s crucial to invest in high-quality solutions for data annotation from the onset of your project. The process of annotating data for an ML project can be surprisingly complicated – There are a variety of factors you’ll need to consider, from how you’ll manage your approach to annotation to what tooling and automation approaches you’ll use.<h2>How to Build Your Data Annotation Pipeline</h2>Annotating data at high quality requires significant upfront and continued investment over the lifespan of your ML system. While there are automated solutions to speed up and streamline the data annotation process, having humans-in-the-loop is key to producing high-quality results. When setting up a data annotation pipeline, your company will need to decide how you’ll find and train annotators, as well as how you’ll measure their performance. To ensure annotators produce high-quality annotations, you’ll need to provide them with performance incentives that align with your most important annotation metrics, whether that’s throughput or quality, or a combination of both. You’ll also need to provide annotation tools for your workers, as well as design a pipeline that encourages your annotators to output consistent, high-quality annotations.<h3>Hiring Annotators While Minimizing Overhead</h3>Finding annotators to complete your task is one of the first challenges you’ll face in the data annotation process. You’ll need to identify workers who are well-suited to annotate your data, whether that involves selecting people who speak a certain language, are from a specific location, or have a particular type of expertise. You’ll also need to decide how to approach the hiring process. Your choice of workforce influences whether you have access to a large selection of annotators who work fewer hours, or a small selection of annotators who work longer hours and generate more consistent results. If you expect a continuous flow of production-quality data, you’ll also need to potentially hire workers across time zones to meet the demands of your project.&nbsp;You should decide whether to hire a larger pool of diverse annotators versus a smaller set of consistent annotators based on your use case. If you anticipate that you’ll need annotations for small, irregular projects, for example, you’ll likely want to rely on a larger selection of annotators that can accommodate short-term surges in need. Alternatively, if you’re pursuing a long-term production project with consistent annotation needs, a smaller team of annotators with regular annotation hours may deliver better results.Once you’ve hired annotators, you’ll also need to devote resources to communication and expectation setting to ensure that your annotators provide you high-quality results. In short, just finding workers to annotate your data and keeping them on your platform can be a time-consuming process with logistical overhead! These challenges are often why many ML teams opt to outsource the entire process to an external company.<h3>Training Annotators and Monitoring Performance</h3>Once you’ve hired your annotators, your work is not yet over – You need to provide training to teach them to accurately annotate your data across different use cases, task types, and annotation types. To ensure high-quality annotations, you’ll need to provide workers with clear and comprehensive instructions, so that different workers can annotate data consistently. You may also find over time that there are several edge cases within your data that your instructions do not cover, as it can be difficult to write non-ambiguous and comprehensive instructions that cover all potential edge cases.As the administrator of the data pipeline, you’ll need to create a “golden dataset” that has accurate annotations for a subset of your data. You can use this dataset to check that workers understand the instructions, as well as to periodically re-evaluate their performance against a gold standard. You should also regularly update this dataset with new examples to provide annotators with up-to-date examples that reflect real-world data.&nbsp;Suppose your goal is to achieve 95%+ quality in your overall dataset. If all your annotators consistently achieve 95% quality, you should be able to achieve this goal. However, if there is a particular edge case that only appears 1% of the time, your annotators can get 100% of that 1% wrong and still average 95% quality overall. While you are still hitting your goal of 95%+ quality, this is not ideal, as your model will not be able to account for this edge case if trained on this dataset.To mitigate this challenge, you will need to add examples to your golden dataset to ensure that it remains well-balanced across all classes and edge cases. By updating and adding new examples to your dataset, you can effectively assess annotator performance over time, and achieve a holistic view of their performance across various classes and edge cases.<h3>Reviewing Annotations for Quality</h3>After your annotators complete tasks, you’ll need to evaluate the final output. To do this, there are two main methods for evaluating annotation quality. For classification or text-based tasks where there is more subjectivity, you can implement a consensus algorithm. Suppose you want to develop a sentiment analysis model, you can have multiple people determine if a person in an image looks happy or sad and the option the majority selected will win. If there isn’t enough confidence in the voted result, you can have a higher-level reviewer determine the final result. In some cases, you may also not want to weigh every person’s vote the same. If you have higher confidence in some people’s votes over others, you may want to implement a weighted voting system that biases the final response more towards the votes of people you have higher confidence in.&nbsp;For image-based or other computer vision tasks, you can have one preliminary attempter annotate the task, then have a higher-level reviewer either review the work and accept the results or review the work and fix annotations.&nbsp;You can select reviewers from past annotators who consistently produce high-quality results. Selecting reviewers, however, can be complicated, since someone’s annotation performance can fluctuate over time. You’ll need to constantly identify reviewers who are no longer performing well so that you can demote them to attempts, while also identifying well-performing annotators so that you can promote them to reviewers. Since this approach removes high-quality annotators from the labeling pool, it will naturally reduce your throughput, so you’ll want to find a balance between quality and throughput.Whatever approach you follow for evaluating label quality, you’ll need to be on the lookout for people who consistently underperform and label data poorly. You should automatically identify underperforming annotators, and either retrain them so they produce higher-quality labels, or remove them from the project entirely.<h3>Selecting the Best Annotation Tool For Your Task</h3>Another big decision you’ll need to make is on what labeling tools your workers will use. You can either build your own tool set or use available commercial tools. While you can specialize in-house tools for your specific task, they can be difficult and time-consuming to build, especially if they need to support different annotation types. For example, image, audio, and text data all require different annotation approaches – For image annotation, you’ll need a system to draw boxes, polygons, or other geometries around identified objects; whereas, for audio annotation, your system will need to support transcription and associating timestamps with event attributes. For classification tasks, on the other hand, your system will need to permit multiple-choice selections and potentially large taxonomies. For video annotation tasks, video files can be very large in size, making them technically challenging to support, especially if your workers have less powerful laptops or slow internet connections.&nbsp;&nbsp;Compared to in-house tooling, commercial data tools make it easier to jump into labeling your data, although they may be less specialized for your use case. Another consideration when selecting the right annotation tool is ML-assisted tooling. Some tools may have ML-assisted tooling, like our <a href="https://scale.com/blog/autosegment" rel="noopener noreferrer" target="_blank">Autosemseg tool</a>, to improve annotation efficiency and speed while others do not. Building and selecting the appropriate labeling tools is vital for optimizing labeler efficiency, so you should ensure the tools you select are well-suited for your use case.<h2>What Next?</h2>Needless to say, getting data annotation right can be a challenging and time-consuming process. You’ll need to consider a wide range of factors, from how you’ll manage your labeling workforce to what automation approaches you’ll use. Your data labeling pipeline is a process that’s incredibly important to get right since ML system performance is correlated with data quality.Instead of building a data pipeline from scratch, you can leverage a product like <a href="https://scale.com/rapid" rel="noopener noreferrer" target="_blank">Scale Rapid</a> or <a href="https://scale.com/studio" rel="noopener noreferrer" target="_blank">Scale Studio</a> to quickly create production-level ratings. It’s designed so that you can set up your projects in minutes and get high-quality labels within hours. Trusted by AI teams like OpenAI, Square, and Pinterest, this tool can help you hit the ground running on your next ML project!

Data annotation, or data labeling, is a more challenging problem than most teams realize but investing in annotation is key to unlocking the power of AI.

Sophia Luo

Introducing: Scale’s Large Language Model Toolkit

How to Setup Data Annotation Pipelines