02 · See it in action
A familiar example
Show a model fictional messages labelled billing, access or other. After training, test it on new messages it has not seen. Label guidelines matter: two people should be able to agree on what each category means.
Break it down
- Identify the input: what information is available?
- Describe the operation or pattern being used.
- Identify the output and how you would check it.
- Name one mistake the system could make.
Change one detail in this example and consider whether the same idea still applies. This helps separate the underlying concept from one specific application.
Sign in to save your reading progress.
Sign in