Data Types in Gen AI: Quality, Structured vs Unstructured, Labeled Data

Every generative AI capability an organization deploys is only as good as the data behind it, because data shapes the model at every stage: foundation models learn from the data they were trained on, customization techniques such as fine-tuning use company data to specialize behavior, and grounding techniques connect a model's answers to enterprise data at the moment a question is asked. If that data is wrong, stale, or missing, the model's fluent, confident output will be fluently and confidently wrong.

This is why Google Cloud frames data strategy as a leadership concern, not a technical detail. A leader deciding where to apply gen AI must ask two questions before choosing any model: do we have the data this use case needs, and can the AI actually reach it? Many organizations discover that their most valuable knowledge sits in formats a traditional analytics program never touched — contracts, emails, call recordings, support chats — and gen AI is often the first technology that can unlock it.

The exam approaches this topic from the business angle. You will not be asked to build a data pipeline; you will be asked to recognize what makes data usable for AI, to classify examples of data as structured or unstructured and labeled or unlabeled, and to predict the business consequences when data quality is poor. The rest of this lesson gives you exactly those tools.

Data quality describes whether data is fit to teach or ground an AI system, and its first three characteristics concern the content of the data itself. Completeness asks whether all the necessary information is present. If a retailer's product catalog is missing size, material, and care details for a third of its items, a gen AI shopping assistant trained or grounded on that catalog cannot answer a third of customer questions — and incomplete training data can also skew a model toward the examples it did see.

Consistency asks whether data is uniform across sources and over time. When one system records a customer as 'J. Perera', another as 'Jayani Perera', and a third under an old address, an AI assistant may treat one customer as three people and give contradictory answers. Inconsistent formats, duplicated records, and conflicting values are among the most common — and most expensive — data problems enterprises face when preparing for AI.

Relevance asks whether the data actually relates to the problem you are solving. A model intended to draft legal clauses gains nothing from terabytes of marketing analytics; a customer-service agent grounded on outdated policy documents is worse than none, because it answers confidently from the wrong material. Relevance is also a cost lever: collecting and preparing data that a use case does not need consumes budget without improving outcomes.

Data accessibility describes whether the right systems and people can actually use the data, and it has three characteristics of its own. Availability asks whether data can be reached when the AI needs it. Data locked in departmental silos, personal spreadsheets, or systems with no integration path is invisible to a gen AI application, however valuable it is. Availability also covers timeliness — a pricing assistant grounded on last quarter's price list gives answers that are precisely, and expensively, out of date.

Cost covers what it takes to acquire, store, clean, label, and maintain data. Data work is typically the largest hidden expense of an AI initiative: licensing third-party datasets, paying people to label examples, and storing large media libraries all add up. Leaders should weigh this cost against the value of the use case before committing — sometimes a narrower use case with cheaper data delivers a better return than an ambitious one with a huge preparation bill.

Format asks whether data is in a form the AI systems can process. A model may need scanned paper forms converted to digital text, audio transcribed, or inconsistent file types normalized before any of it becomes usable. Format is also where structured and unstructured data — the next two sections — enter the picture, because each demands different handling and different tools.

Structured data is data organized into a predefined model — typically rows and columns with fixed fields and data types — which makes it easy to store in relational databases, query precisely, and analyze at scale. Each piece of information has a defined place: a customer ID goes in one column, an order date in another, an amount in a third.

Real-world examples appear in every business function: sales transactions in a point-of-sale system, customer records in a CRM, inventory levels in a warehouse database, financial entries in an accounting ledger, sensor readings arriving as timestamped values, and website analytics events. On Google Cloud, structured data typically lives in databases and in BigQuery, where it can be queried and analyzed — increasingly in plain language, with Gemini translating a business question into a query.

For gen AI, structured data plays two main roles. It grounds factual answers: when an AI assistant reports a customer's order status or current stock level, that answer must come from a structured system of record, not from the model's general training. It also supplies the historical signal for personalization and prediction — purchase histories and behavioral events are the structured backbone behind a personalized experience. The business appeal of structured data is precision and trust: it is easy to validate, aggregate, and govern, which is why regulated reporting runs on it.

Unstructured data is data without a predefined model — free-form content such as text documents, images, audio, and video — and it makes up the large majority of the data most organizations hold. There are no fixed fields: the meaning is inside the content itself, which is why traditional analytics tools largely ignored it and why generative AI changes its value so dramatically.

Real-world examples surround every team: emails and chat threads, contracts and policy documents, presentations and reports, customer reviews and survey comments, support-call recordings, product photos, security footage, and social media posts. Semi-structured formats — data with some organizing tags but no rigid table structure, such as invoices with varying layouts — sit between the two categories, and the exam treats recognizing examples as the key skill.

Foundation models are the breakthrough technology for unstructured data because they understand language, images, audio, and video natively. A multimodal model like Gemini can read a contract and extract its obligations, listen to support calls and identify recurring complaints, or examine product photos for catalog errors. This is the strategic point leaders should internalize: the majority of enterprise knowledge — the reasoning in documents, the voice of the customer in reviews and calls — was effectively dark data before gen AI. Organizations that make their unstructured data available to AI convert an unused asset into answers, insight, and automation.

The distinction comes down to organization: structured data fits a predefined schema of rows and columns, while unstructured data is free-form content whose meaning lives inside it. The comparison below is the exam-ready summary.

Two exam cues are worth memorizing. First, classification questions give you an example — 'customer support call recordings', 'a spreadsheet of quarterly sales' — and ask which type it is. Second, value questions test whether you know that gen AI's distinctive advantage over earlier analytics is its ability to work with unstructured data, which is where most untapped business knowledge lives.

Labeled data is data that carries tags identifying the correct answer or meaningful attributes — an email marked 'spam', an image tagged 'defective part', a transaction flagged 'fraudulent' — while unlabeled data is raw data with no such annotations. The distinction matters because it determines which machine learning approach can use the data and what it will cost to prepare.

Labeling is a genuine business cost: accurate labels usually require paid human effort, and specialist domains — medical images, legal clauses — require expensive expert time. This is one reason foundation models are so economically attractive: they are pretrained largely on vast amounts of unlabeled data, so an organization can often adapt one with prompts, grounding, or a small labeled fine-tuning set instead of labeling millions of examples itself.

Poor data quality converts directly into business risk when gen AI is involved, because a generative model does not simply fail on bad data — it produces plausible, confident output built on it, which is harder to catch than an obvious error. The implications cluster into four areas leaders are expected to recognize.

Trust and accuracy. An assistant grounded on inconsistent or outdated data gives wrong answers to customers and employees, and every wrong answer erodes willingness to use the system. Flawed or unrepresentative data also introduces bias, producing outputs that are unfair to particular groups — a responsible-AI risk with reputational and regulatory consequences. Cost and delay. Data preparation is typically the largest single expense in an AI initiative; discovering mid-project that data is incomplete or badly formatted stalls timelines and inflates budgets. Decision quality. Summaries, forecasts, and insights generated from low-quality data mislead the leaders who rely on them — worse than no insight, because it arrives with confidence. Missed opportunity. Valuable use cases stay out of reach when the data they need is siloed or inaccessible.

Consider a bank deploying a gen AI assistant for relationship managers. With complete, consistent, current customer data, the assistant summarizes each client accurately and suggests relevant products; with duplicated records and stale balances, it recommends products clients already own and misstates their positions — damaging exactly the relationships it was meant to strengthen. The exam's underlying rule: assess and improve data quality and accessibility before scaling a gen AI use case, not after.