A.1.3: Case Study Topic Area #3: Datasets & Risks
The Building Blocks, Blind Spots & Consequences
Note 1: This outline provides guidance specific to Case Study #3, complementing the general case study rubric [link].
Note 2: See lecture note 3.1 Datasets & Risks of AI [link] for illustrative examples.
The Brief
Generative AI systems learn from data. What they can generate, recognise, or reason about is therefore shaped by what is represented in that data, what is missing, and how the data has been collected and curated.
In this case study, you will investigate:
Data → Model Behaviour → Risk → Response
Select a specific domain or task and use a market-ready Generative AI model or LLM to explore:
- What the model does well
- Where its capability begins to break down
- What these patterns might reveal about its underlying data
- What risks arise from these limitations
- What could be improved
You are NOT training a customised Generative AI model.
You are using controlled tests, comparisons, and available information about datasets to probe the boundaries of an existing AI system.
Examples:
• Ask a Generative AI model to transform daytime Hong Kong street images into realistic nighttime scenes, and investigate where local characteristics are preserved, distorted, or replaced by generic imagery.
• Test whether an LLM performs equally well across different locations, languages, cultures, disciplines, or types of knowledge.
• Identify another specific task in your own domain where you suspect the model’s performance may depend on what is well or poorly represented in its training data.
The goal is not simply to show that AI makes mistakes.
The goal is to investigate what those mistakes or boundaries may reveal about the data behind the system, and why this matters.
Your analysis should address the following questions.
1. What is the domain-specific task?
Define a specific and testable task.
(E.g., creating a realistic nighttime Hong Kong street scene from a daytime photograph, rather than simply generating an attractive nighttime image.)
• Problem / Function
– What is the main objective of the task?
– What would count as a successful result?
– Why is this problem important?
– Why might the available data matter?
2. What data might shape the model’s behaviour?
Investigate what is known about the data behind the selected AI system and identify the aspects most relevant to your task.
• Data & Representation
– What is publicly known about the model’s training data?
– Where might the data have come from?
– What kinds of examples are likely to be well represented?
– What might be missing or underrepresented?
• Data Quality
Consider where relevant:
– Coverage and diversity
– Accuracy and labelling
– Geographic or cultural representation
– Recency
– Filtering and curation
– Privacy, consent, copyright, or provenance
3. What does the model know, miss, or distort?
Systematically test the model on your chosen task.
Do not rely on only one successful and one unsuccessful example. Look for repeatable patterns.
• Capabilities
– What does the model consistently handle well?
– What knowledge or patterns appear to be well represented?
• Boundaries
– Where does the model begin to fail?
– What does it omit, simplify, substitute, hallucinate, or misrepresent?
– Are these failures random or systematic?
• Evidence
You may use:
– Controlled prompt changes
– Controlled input changes
– Repeated generations
– Comparisons across categories or conditions
– Comparisons between different models
– Real-world or documented reference material
Prompts may be used as an experimental probe, but the goal is not simply to demonstrate better prompt engineering.
4. What risk does this create?
Connect the behaviour you observed to at least one meaningful downstream risk.
Possible risks include:
- Representational bias
- Missing or unreliable knowledge
- Stereotyping
- Geographic or cultural misrepresentation
- Privacy or consent
- Copyright or provenance
- Unsafe or misleading outputs
- Exclusion of underrepresented users or contexts
• Consequences
– Who or what could be affected?
– When does the limitation become consequential?
– Could it influence judgement, representation, access, or decision-making?
Your analysis should connect a specific model behaviour to a specific consequence.
5. How might it be improved?
Propose a reasonable response to the limitation you identified.
Possible approaches include:
- Adding more diverse or representative data
- Improving labels or metadata
- Introducing specialised domain data
- Improving geographic, cultural, or linguistic coverage
- Filtering poor-quality or problematic data
- Retrieving information from trusted external sources
- Fine-tuning or adapting a model
- Introducing human review or verification
- Using prompts or guardrails where the underlying model cannot be changed
• Causal Reasoning
– What would you change?
– Why might this improve the behaviour you observed?
– What trade-offs or new risks might it introduce?
Your analysis should reveal one clear insight about how data shapes model behaviour and risk.
What a Strong Submission Demonstrates
A strong submission will:
- Define a clear domain-specific task
- Identify a meaningful issue related to data quality, coverage, or representation
- Use evidence to reveal a capability, bias, gap, or boundary
- Distinguish clearly between what is known, observed, and inferred
- Connect model behaviour to a meaningful risk or consequence
- Propose a plausible response or improvement
- Communicate the relationship clearly:
Data → Behaviour → Risk → Response
Your work should demonstrate data-centric AI thinking, not simply better use of an AI tool.
Deliverables
Your submission is built around a central artefact, which forms the backbone of the case study and provides the evidence from which your abstract, slides, video, and poster are constructed.
The Artefact — Data, Behaviour & Risk
The artefact is the core analytical and evidentiary material developed through your investigation.
Think of it as the body of evidence that makes the relationship between data, model behaviour, risk, and response visible.
Your artefact should make clear:
• Task & Context
– What specific task are you testing?
– What would count as successful or credible performance?
• Data & Representation
– What is known about the relevant training data or data pipeline?
– What kinds of information appear well represented, missing, or underrepresented?
– Where necessary, distinguish clearly between what is known and what is inferred.
• Testing & Evidence
– Use controlled tests, comparisons, repeated outputs, or reference material to reveal patterns in model behaviour.
– Show both capabilities and boundaries, rather than relying on isolated examples.
• Risk & Consequence
– Connect an observed behaviour to a meaningful downstream risk.
– Explain who or what may be affected, and why the behaviour matters.
• Response
– Propose a plausible intervention addressing the limitation you identified.
– Explain why the intervention might improve the behaviour, and what trade-offs it may introduce.
Use evidence from your investigation to support these claims.
This may include:
• Input examples
• Prompts and outputs
• Controlled comparisons
• Repeated generations
• Dataset documentation
• Screenshots
• Diagrams
• Tables or quantitative observations
• Real-world reference material
• Model comparisons
• Annotations identifying specific patterns or failures
Each piece of evidence should be carefully selected and captioned to explain what it shows, what you infer from it, and why it matters.
The artefact should allow the reader to follow the central chain:
What data? → What did you test? → What happened? → What risk does it create? → What could change?
i. Abstract
Provide a concise written abstraction of no more than 300 words.
Distil the task investigated, the relevant data issue, your method of testing, the key behavioural finding, the resulting risk, and your principal insight about how data shapes AI behaviour.
ii. Slides
Develop a sequence of portrait-format slides that uses your artefact and supporting evidence to construct a clear visual story.
The sequence should make the progression from data → testing → behaviour → risk → response legible.
iii. Video
Develop a short-form video presentation of no more than 90 seconds using your slides and artefact as its visual foundation.
Use the video to connect the strongest evidence and communicate your central insight about how data shapes what the AI system can, cannot, or should not be trusted to do.
iv. Poster
Bring the strongest elements of your artefact and evidence together into a complete A2-format poster.
The poster should function as a self-contained visual argument, making the relevant data issue, observed model behaviour, resulting risk, and principal insight clearly legible.
You may include supplementary materials in an appendix, such as:
- Additional test cases
- Prompt comparisons
- Model comparisons
- Dataset documentation
- Code snippets
- Additional diagrams or tables
- Experimental results
Grading Criteria
In a nutshell
We are not grading:
- Advanced mathematics
- Sophisticated coding
- The complexity of the AI tool
- The aesthetic quality of AI outputs in isolation
- Complete knowledge of a proprietary training dataset
We are grading:
| Criterion | What It Means |
|---|---|
| Data Understanding | Do you understand how data quality, coverage, or representation may shape the model? |
| Evidence & Reasoning | Do you support your argument with observable evidence and distinguish evidence from speculation? |
| Risk Analysis | Do you explain why the behaviour matters and what consequences may follow? |
| Response | Do you propose a plausible way to address the identified issue? |
| Communication | Can you construct a clear and visually coherent argument? |
Rubric
| Criterion | Excellent | Adequate | Insufficient |
|---|---|---|---|
| Data Understanding | Clearly identifies and explains a meaningful issue in data quality, coverage, representation, or provenance | Identifies a relevant data issue but with limited depth | Data is treated superficially or its relevance is unclear |
| Evidence & Reasoning | Uses systematic evidence to connect data-related factors to model behaviour while distinguishing observation from inference | Provides some evidence but the connection is underdeveloped | Makes unsupported claims or relies on isolated outputs |
| Risk Analysis | Clearly connects observed behaviour to a specific and meaningful downstream risk | Identifies a relevant risk but connection is weak | Mentions generic risks without linking them to the investigation |
| Response | Proposes a convincing response and explains why it could address the identified issue | Suggests a plausible response with limited justification | Suggests generic fixes without addressing the underlying issue |
| Clarity & Visual Argument | Evidence is carefully selected and organised into a clear visual narrative | Argument is understandable but uneven | Submission is difficult to follow or visually disconnected |
The Standard
The goal is not simply to show that AI sometimes gets things wrong.
The goal is to ask:
What does the system appear to know?
What is missing or distorted?
What might the data have to do with this?
What risk does this create?
Distinguish what you know, what you observe, and what you infer.
Don’t just use AI.
Probe what it has learned—and what it has not.