What Is Vocabulary | Semantic Relations — Synonyms, Antonyms, Hypernyms, Hyponyms, Meronyms and Word Networks

SEMANTIC RELATIONS · LEXICAL RELATIONS · SYNONYMY · ANTONYMY · HYPERNYMY · HYPONYMY · MERONYMY · HOLONYMY · WORD RELATIONSHIPS

Semantic relations are relationships among meanings or word senses, while lexical relations describe systematic relationships involving lexical items themselves. In vocabulary learning, the most useful relations include synonymy (similarity), antonymy (contrast), hypernymy and hyponymy (category relationships such as animal → dog), meronymy and holonymy (part–whole relationships such as wheel → bicycle), co-hyponymy, incompatibility, converse relations and semantic fields. These relationships help explain why vocabulary is not a bag of isolated definitions but a structured network of concepts, categories and contrasts.

The search questions what are semantic relations, what are lexical relations, what is the difference between a hypernym and a hyponym, what is meronymy, what are synonyms and antonyms, what is a word relationship, and how are words connected in the mental lexicon all point to the same underlying idea: knowing a word includes knowing how its meaning sits beside other meanings. A learner who knows that a sparrow is a kind of bird, that a wing is part of a bird, that hot contrasts with cold, and that purchase is similar but not identical to buy possesses richer vocabulary knowledge than a learner who knows only one-line definitions.

This guide explains semantic relations, lexical relations, synonymy, antonymy, complementaries, gradable opposites, converse terms, hypernyms, hyponyms, co-hyponyms, taxonomies, meronyms, holonyms, semantic fields, lexical fields, incompatibility and word networks. It also shows why some relations are more accurately relations among concepts or senses than between word forms, how WordNet-style lexical networks organise meanings, how semantic relations support reading comprehension and writing precision, and how teachers can turn word lists into connected vocabulary systems rather than isolated memorisation.

A vocabulary becomes powerful when a word arrives with neighbours: what it resembles, what it opposes, what contains it, what it contains, and where it belongs.

This is a new worldwide umbrella article in eduKateSG’s What Is Vocabulary | ##### series. Existing specialist articles remain untouched. The separate Meronymy and Holonymy, Lexical Incompatibility and Co-hyponymy, Semantic Fields and Lexical Fields, and Polysemy and Multiple Meanings pages keep their narrower jobs. This page owns the umbrella question: how vocabulary meanings are related to one another.

1. Semantic relations in one table

Relation	Question	Example	What it teaches
Synonymy	Which meanings are similar?	begin / start	Similarity with boundaries
Antonymy	Which meanings contrast?	hot / cold	Opposition and scale
Hyponymy	What is a kind of what?	rose → flower	Category inclusion
Hypernymy	What broader category contains this item?	vehicle → car	Generalisation
Co-hyponymy	Which items share a category?	cat / dog / horse under animal	Sibling concepts
Meronymy	What is part of what?	wheel → bicycle	Part–whole structure
Holonymy	What whole contains this part?	bicycle → wheel	System organisation
Converse relation	Which words describe the same relation from opposite roles?	buy / sell	Perspective
Semantic field	Which words belong to a shared domain?	judge, court, verdict, appeal	Domain structure

These labels are useful learning tools, but they should not be treated as if every relation is literally stored in the mind as a rigid arrow. Linguistic theories disagree about how such relationships are represented. Cambridge lexical-semantics work is especially careful that relations such as hyponymy and meronymy may often reflect relations among concepts or denoted things rather than simple links between word forms.

2. Semantic relations and lexical relations are not exactly the same

A semantic relation is a relation between meanings or senses. A lexical relation is a relation involving lexical items and may include not only meaning but form, conventional pairing or distribution.

This distinction matters because two word forms can each have several senses. The relation may hold between one sense of word A and one sense of word B, not between the entire words in every context.

For example, bank in the financial sense is related to lender and finance, while bank in the river sense belongs to a different semantic neighbourhood. Treating the spelling as one undivided object hides the structure.

A practical learner does not need to settle theoretical debates. The useful habit is to ask: “Which sense is related to which other sense, and what kind of relationship connects them?”

3. Paradigmatic relations: words that could occupy the same slot

Paradigmatic relations connect items that can contrast or substitute within a structural position. Synonyms, antonyms and co-hyponyms often behave this way.

In the sentence “She bought a ___,” words such as car, bicycle, ticket, book can occupy the same grammatical slot while belonging to different conceptual categories. If the context narrows to “vehicle,” car, bicycle, truck become a more coherent contrast set.

Paradigmatic knowledge helps vocabulary choice because the learner does not search the entire lexicon equally. A concept activates a neighbourhood of plausible alternatives.

This is one reason vocabulary depth includes knowing contrasts. A word is easier to choose accurately when the learner knows what nearby words were rejected and why.

4. Syntagmatic relations: words that naturally occur together

Syntagmatic relations concern how words combine in sequences. Collocation, grammatical patterns and multiword expressions live here.

Although collocation is not the same as synonymy or hyponymy, it is part of the larger architecture of lexical knowledge. A learner who knows decision deeply knows not only its category relations but also phrases such as make a decision and reverse a decision.

Paradigmatic relations help answer “Which alternative word belongs here?” Syntagmatic relations help answer “Which words naturally stand beside this one?”

Strong vocabulary integrates both axes: alternatives and partners.

5. Synonymy: similarity without perfect interchangeability

Synonymy concerns words or expressions with the same or very similar meanings. Cambridge Dictionary notes that perfect synonymy is difficult to establish, while many pairs are similar enough to be treated as synonyms in practice.

Words such as begin and start overlap strongly, yet other synonym pairs differ in register, collocation, intensity or connotation.

This is why synonym learning should focus on semantic neighbourhoods rather than equality signs. Purchase and buy share a core transaction meaning, but their register differs.

A learner who treats synonyms as exact replacements may produce sentences that are technically understandable but unnatural or socially wrong.

6. Near-synonyms are often more educational than perfect synonyms

Most useful synonym work involves near-synonyms: words whose meanings overlap substantially but whose boundaries differ.

Consider look, glance, stare, gaze, peer and observe. All relate to seeing, but duration, intention, effort and social meaning vary.

Comparing near-synonyms builds depth because the learner must identify dimensions of contrast rather than memorise duplicate labels.

The strongest question is not “What is a synonym?” but “When would the other word change the meaning?”

7. Antonymy: opposition and contrast

Antonymy concerns conventional opposition between meanings or words. Cambridge Dictionary describes it as the state of having opposite meanings, while lexical-semantics research treats contrast as one of the strongest organising relations in vocabulary.

Opposition is not one single structure. Alive/dead, hot/cold and buy/sell are all “opposites,” but they behave differently.

This variety matters because students who memorise antonym pairs may miss the logic of the contrast.

A good antonymy lesson identifies the type of opposition and the dimension on which the two items contrast.

8. Complementary opposites: either–or contrasts

Complementary antonyms divide a domain into contrasting states that are treated as mutually exclusive in the relevant context. Alive/dead is the classic example.

If something is fully alive in the ordinary biological sense, it is not dead; if it is dead, it is not alive. The contrast does not normally use a middle degree in the same way as hot and cold.

Real language can still produce metaphorical or borderline uses such as “half-dead,” which reminds us that natural language resists perfectly rigid logical boxes.

The teaching value lies in understanding the structural difference from gradable opposites.

9. Gradable opposites: endpoints on a scale

Gradable antonyms such as hot/cold, tall/short, rich/poor lie on a scale. Intermediate values are possible.

Something can be neither particularly hot nor particularly cold. A person can be taller than one person and shorter than another.

Gradable opposites support comparative language, degree modifiers and scalar inference.

Vocabulary learning deepens when learners map the scale rather than memorise two endpoints.

10. Converse relations: the same situation from opposite roles

Converse terms describe the same relational event from different participant perspectives. Buy/sell, lend/borrow, employer/employee, parent/child are familiar examples.

If A buys something from B, B sells it to A. The event is shared, but the lexical choice encodes role.

This relation is extremely useful in reading and writing because changing viewpoint can change the appropriate word without changing the underlying event.

Learners should practise transforming sentences across perspectives to strengthen relational vocabulary.

11. Hyponymy: kind-of relations

Hyponymy is the relation between a more specific concept and a broader category. A rose is a kind of flower; a sparrow is a kind of bird.

The specific item is the hyponym. The broader category is the hypernym or superordinate.

One diagnostic frame is “X is a kind of Y.” If the sentence works naturally and preserves the intended sense, hyponymy may be present.

Hyponymy helps learners organise vocabulary hierarchically instead of storing hundreds of unrelated nouns.

12. Hypernyms allow generalisation

A hypernym names a broader class that includes more specific members. Animal is a hypernym of dog; vehicle is a hypernym of car.

Hypernyms support summarisation because they compress several specific items into one category label.

They also support inference. If a text says something is a mammal, category knowledge activates expectations that can help interpret unfamiliar hyponyms.

Writing often moves between hypernyms and hyponyms to control specificity: general claim first, specific example second.

13. Co-hyponyms: siblings inside one category

Co-hyponyms share the same broader category. Rose, tulip, orchid are co-hyponyms under flower.

Co-hyponyms often contrast with one another because selecting one category member excludes others in a particular context.

This makes co-hyponym sets useful for precision exercises. If an animal is specifically a sparrow, calling it a pigeon is wrong even though both are birds.

eduKateSG’s existing Lexical Incompatibility and Co-hyponymy article owns the deeper specialist treatment.

14. Taxonomies turn vocabulary into nested category systems

A taxonomy is a structured classification in which broader categories contain narrower ones. Vocabulary in biology, libraries, computing and education often depends on taxonomic thinking.

A learner can organise organism → animal → vertebrate → mammal → primate as successive levels of specificity.

Taxonomies reduce memory load because each new word enters an existing structure. The learner does not need to invent a separate world for every item.

However, real categories can be fuzzy, contested or purpose-dependent. Not every lexical field forms a perfect tree.

15. Meronymy: part-of relations

Meronymy relates a part to a whole. A wheel is part of a bicycle; a chapter is part of a book.

The part term is the meronym. The whole is the holonym.

Meronymy is conceptually different from hyponymy. A wheel is not a kind of bicycle; it is part of one.

This distinction is important in science and systems thinking because category errors and part–whole errors lead to different misunderstandings.

16. Holonymy: whole-of relations

Holonymy is the inverse of meronymy. A bicycle is the whole that contains wheels; a tree is the whole that contains branches.

Holonyms help learners organise components into systems. The word does not merely name an object; it becomes a container for relationships.

This is useful in technical learning where parts have functions: engine–car, nucleus–cell, keyboard–computer.

The existing eduKateSG Meronymy and Holonymy article owns the full part–whole taxonomy.

17. Part–whole relations are not all the same

Parts can relate to wholes in several ways. A component can be physically attached, a member can belong to a group, a substance can compose an object, or an area can belong to a larger place.

Wheel–car, soldier–army, steel–bridge, room–house all express part–whole structure, but the relation differs.

Recognising these differences strengthens conceptual vocabulary and prevents overgeneralisation.

Advanced learners can ask what kind of “part” relationship is actually being described rather than using meronymy as a vague label.

18. Incompatibility: related concepts that exclude one another

Incompatibility occurs when words share a semantic domain but cannot normally apply simultaneously to the same referent in the same respect.

Colour terms offer familiar examples: an object cannot be entirely red and entirely blue in the same place and sense at the same moment, though mixed or patterned objects complicate the picture.

Co-hyponyms are often incompatible because choosing one member rules out another member of the same contrast set.

Incompatibility helps learners understand why related vocabulary can be close without being synonymous.

19. Semantic fields: vocabularies organised around domains

A semantic field is a set of meanings connected by a shared domain such as law, weather, emotion, transport or cooking.

The words need not stand in one simple relation. A legal field can contain people, actions, institutions, documents and outcomes.

Semantic fields support learning because domain knowledge creates multiple connections among new words.

The existing Semantic Fields and Lexical Fields article owns that specialist lane.

20. Lexical fields and lexical sets

Lexical fields organise words around related areas of meaning. In classroom use, terms such as lexical field, semantic field and lexical set sometimes overlap, though linguistic traditions may define them differently.

A lexical set can be useful pedagogically even without a perfect theoretical boundary: weather words, movement verbs, emotion adjectives, classroom nouns.

The danger is learning too many very similar words simultaneously, which can produce interference.

Good field-based learning combines grouping with contrast and spaced reuse.

21. Polysemy changes semantic relationships by sense

Polysemy occurs when one lexical form has several related senses. Each sense can enter different semantic relations.

Head as a body part relates meronymically to body; head as a leader relates to organisational hierarchy.

A learner must therefore resolve the sense before identifying the relevant word network.

The existing Polysemy and Multiple Meanings article owns that specialist mechanism.

22. Homonymy reminds us that identical forms can belong to unrelated networks

Homonyms share form while having unrelated meanings. A word form can therefore connect to several entirely different semantic neighbourhoods.

Bat as an animal belongs with mammals and flight; bat as sporting equipment belongs with games and tools.

This means a lexical network should be built around senses rather than spellings alone.

Sense-first organisation prevents learners from linking unrelated meanings just because the forms look the same.

23. Morphological relations are not the same as semantic relations

Words can be related by form because they share a root or affix: act, action, active, activate. This is a morphological relation.

Morphological relatives often share semantic material, but not every form-related word preserves exactly the same meaning.

Learners should therefore distinguish “same family” from “same meaning.”

The best word-family instruction combines morphological structure with semantic comparison and grammatical role.

24. Collocation connects partners rather than categories

Collocation concerns habitual co-occurrence: strong evidence, heavy rain, reach a conclusion.

Unlike hyponymy or antonymy, collocation does not primarily classify the meanings as similar, opposite or part–whole.

It describes a combinational relationship that becomes part of lexical competence.

Vocabulary mastery therefore includes both semantic relations among alternatives and collocational relations among partners.

25. Semantic relations and the mental lexicon

The mental lexicon is often described metaphorically as a network rather than an alphabetical dictionary. Related concepts can activate one another during comprehension and retrieval.

Semantic priming research shows that related items can influence processing, although the exact architecture of lexical memory is more complex than a simple concept map.

For education, the useful implication is that connected learning is usually more meaningful than isolated memorisation.

A new word becomes easier to retrieve when it attaches to categories, contrasts, examples, morphology and phrases already known.

26. WordNet shows one computational model of lexical relations

WordNet is a major lexical database that groups word senses into synonym sets and connects those sets through semantic relations such as hypernymy, hyponymy, meronymy and holonymy.

Computational resources make relations explicit so software can navigate from a concept to broader categories, narrower categories or parts.

Human lexical knowledge is not identical to WordNet, but the model makes the idea of a structured lexicon concrete.

It also shows why sense distinctions matter: one spelling may belong to several different synsets and relational paths.

27. Dictionary thinking and thesaurus thinking

A dictionary typically foregrounds definitions and senses. A thesaurus foregrounds relationships among words and concepts.

Strong vocabulary needs both forms of knowledge. Definitions establish what the word means; relational knowledge shows where it sits among alternatives.

Cambridge lexical-semantics work explicitly contrasts dictionary-like and thesaurus-like approaches to representing meaning.

Learners can imitate both: write a short definition, then build a relation map around the word.

28. Semantic relations support reading comprehension

Readers constantly use category and contrast knowledge. If a passage says an unfamiliar creature is a marsupial, knowing the hypernymic category constrains interpretation.

Antonymic contrast helps decode sentence structure when conjunctions such as but or whereas signal opposition.

Part–whole knowledge helps readers build models of systems described in science and technical texts.

Semantic relations therefore support inference because they reduce the number of plausible meanings and connect new information to existing knowledge.

29. Semantic relations support precise writing

Writers move between general and specific vocabulary. Hypernyms create broad claims; hyponyms supply precise examples.

Synonym networks help avoid awkward repetition, but only when alternatives preserve meaning and register.

Antonymic contrasts create argument structure, while meronymic language helps explain systems and components.

A writer with rich relational vocabulary can zoom in, zoom out, compare and classify with greater control.

30. Semantic relations support fluent speaking

During speaking, a missing word can sometimes be reached through neighbours: category, opposite, part, function or near-synonym.

If the exact word thermometer is unavailable, a speaker may retrieve the category instrument or describe its function.

This relational redundancy makes communication resilient.

Practice that asks learners to paraphrase through hypernyms, hyponyms and contrasts therefore strengthens flexible oral vocabulary.

31. Semantic relations are a major component of vocabulary depth

Vocabulary breadth asks how many words are known; depth asks how richly each is represented.

Knowing semantic relations is part of depth because the learner can place the word inside a network rather than retrieve one isolated definition.

A learner who knows sparrow as “a small bird” has more depth than one who recognises only a picture, and still more depth if the learner can contrast sparrows with pigeons and identify wings and beaks as parts.

Relational depth supports both comprehension and productive precision.

32. New words become easier when they attach to known relations

A completely isolated lexical item has few retrieval routes. A new word linked to a familiar hypernym, contrast and example becomes easier to organise.

If learners encounter arboreal, connecting it to tree, terrestrial and known animal habitats gives the item conceptual structure.

Relation-building is especially helpful for abstract academic vocabulary because pictures alone are often insufficient.

The educational aim is not to force every word into every relation, but to build enough meaningful links to stabilise the concept.

33. Semantic relations across languages

Languages do not carve conceptual space in exactly the same way. One language may use one broad word where another language uses several more specific terms.

This means hypernymic, synonymic and antonymic relationships may not translate one-to-one.

Bilingual learners benefit from comparing category boundaries rather than assuming dictionary equivalents occupy identical networks.

Cross-language comparison can deepen both languages by making hidden conceptual distinctions visible.

34. How to assess semantic-relation knowledge

Matching words to definitions tests one dimension of vocabulary. Relation tasks can reveal deeper organisation.

Useful tasks include choosing a hypernym, generating a hyponym, naming a part of a whole, identifying an antonym type, sorting co-hyponyms or explaining why two near-synonyms are not interchangeable.

Production tasks are especially informative because learners must reconstruct the network without seeing all the answers.

Assessment should be selective: not every word has a useful antonym, clear meronym or simple taxonomic position.

35. How to teach semantic relations

Start with a small set of familiar words and make one relation visible. For hyponymy, use “X is a kind of Y.” For meronymy, use “X is part of Y.”

Then ask learners to generate additional members and identify incorrect examples.

Move later to ambiguous or abstract vocabulary where relations depend on sense and context.

The teacher’s job is to reveal structure without pretending language is a perfectly tidy classification system.

36. Concept maps make relations visible

Concept maps can label arrows such as is a kind of, is part of, causes, contrasts with, is similar to.

This externalises the structure learners need to internalise.

A map also reveals missing knowledge. A word with no links may be memorised but poorly integrated.

The existing eduKateSG article How Concept Mapping Works owns the general mapping method.

37. Common errors when teaching word relationships

The first error is treating all related words as synonyms. Words can share a field without sharing denotation.

The second is confusing kind-of and part-of relations: a wheel is not a kind of car.

The third is assuming every word has a clean opposite.

The fourth is building taxonomies without checking the active word sense.

38. Semantic relations in the age of AI

AI systems can generate semantic maps, synonyms, category hierarchies and examples almost instantly.

The danger is confident but incorrect classification. A generated hypernym may be too broad, a meronym may reflect only one object type, or a synonym may ignore register.

Use AI as a proposal engine, then verify important relations with dictionaries, corpora and domain knowledge.

Learners should still explain the relation themselves. The educational gain comes from understanding why the link holds.

39. Semantic-relation laboratory: 100 worked word relationships

The examples below deliberately include clean cases and messy cases. Clean cases teach the relation; messy cases teach the limits. Natural-language semantics is useful precisely because it requires judgement rather than mechanical labelling.

1. rose / flower

Relation: hyponymy. Why: rose is a kind of flower. Caution: Do not reverse the claim: every flower is not a rose.

Practice: Add tulip and orchid as co-hyponyms. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

2. sparrow / bird

Relation: hyponymy. Why: sparrow is a kind of bird. Caution: The relation concerns the intended animal sense.

Practice: Add eagle, pigeon and penguin under bird. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

3. car / vehicle

Relation: hyponymy. Why: car is a kind of vehicle. Caution: Vehicle is broader than car.

Practice: Contrast with wheel, which is a part, not a kind. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

4. violin / instrument

Relation: hyponymy. Why: violin is a kind of musical instrument. Caution: Instrument can have other senses, so specify the musical sense.

Practice: Add cello and flute as co-hyponyms. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

5. oak / tree

Relation: hyponymy. Why: oak is a kind of tree. Caution: Tree is the hypernym.

Practice: Add maple and pine as sibling categories. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

6. laptop / computer

Relation: hyponymy. Why: laptop is a kind of computer. Caution: Computer is the broader category.

Practice: Contrast laptop with desktop and tablet depending on taxonomy. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

7. triangle / polygon

Relation: hyponymy. Why: triangle is a kind of polygon. Caution: The hierarchy is mathematical and definitional.

Practice: Add quadrilateral and pentagon. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

8. novel / book

Relation: hyponymy. Why: a novel is a kind of book. Caution: Book is a broader publishing category.

Practice: Add biography and textbook as other book types. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

9. doctor / professional

Relation: hyponymy. Why: doctor can be classified as a professional. Caution: Context determines whether profession or qualification is foregrounded.

Practice: Add lawyer and engineer. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

10. democracy / political system

Relation: hyponymy. Why: democracy is a kind of political system. Caution: Real political systems may be hybrids.

Practice: Compare category labels carefully in civics. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

11. wheel / bicycle

Relation: meronymy. Why: wheel is part of a bicycle. Caution: A wheel is not a type of bicycle.

Practice: Name frame, chain and pedal as other parts. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

12. chapter / book

Relation: meronymy. Why: chapter is part of a book. Caution: Not all books have chapters.

Practice: Distinguish optional structural parts from necessary components. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

13. keyboard / computer

Relation: meronymy. Why: keyboard can be part of a computer system. Caution: Some computers lack physical keyboards.

Practice: Relation depends on system configuration. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

14. nucleus / cell

Relation: meronymy. Why: nucleus is part of many eukaryotic cells. Caution: Not every cell type has a nucleus.

Practice: Science knowledge constrains the relation. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

15. branch / tree

Relation: meronymy. Why: branch is part of a tree. Caution: Branch also has organisational senses.

Practice: Resolve the sense first. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

16. room / house

Relation: meronymy. Why: room is part of a house. Caution: Not every room belongs to a house.

Practice: Holonym depends on context. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

17. member / team

Relation: member–collection. Why: a member belongs to a team. Caution: This is not physical component meronymy.

Practice: Compare player–team and soldier–army. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

18. soldier / army

Relation: member–collection. Why: a soldier is a member of an army. Caution: The army is a collective whole.

Practice: Avoid saying soldier is a ‘part’ in exactly the same sense as wheel–car. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

19. steel / bridge

Relation: substance–object. Why: steel can compose part of a bridge. Caution: The relation is material composition.

Practice: Distinguish substance from detachable component. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

20. water / lake

Relation: substance–container. Why: water constitutes much of a lake. Caution: The relation is not taxonomic.

Practice: A lake is not a kind of water. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

21. begin / start

Relation: near-synonymy. Why: meanings overlap strongly. Caution: Register and constructions can differ.

Practice: Test substitutions in several sentences. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

22. big / large

Relation: near-synonymy. Why: both describe size. Caution: Collocations differ: big mistake vs large amount.

Practice: Meaning similarity does not guarantee phrase interchangeability. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

23. buy / purchase

Relation: near-synonymy. Why: same core transaction. Caution: Purchase is usually more formal.

Practice: Compare conversation and legal/business prose. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

24. ask / request

Relation: near-synonymy. Why: both seek information/action. Caution: Request is more formal and noun-compatible.

Practice: Check grammar and social distance. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

25. child / kid

Relation: near-synonymy. Why: same broad referent. Caution: Kid is more informal.

Practice: Register is part of lexical relation knowledge. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

26. angry / furious

Relation: near-synonymy. Why: both express anger. Caution: Furious is stronger.

Practice: This is similarity plus gradation. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

27. thin / slim

Relation: near-synonymy. Why: both describe small width. Caution: Connotation differs.

Practice: Semantic overlap coexists with evaluation. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

28. mistake / error

Relation: near-synonymy. Why: both denote incorrectness. Caution: Error is often more formal/technical.

Practice: Context can favour one strongly. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

29. job / occupation

Relation: near-synonymy. Why: both concern work. Caution: Occupation is more formal and classificatory.

Practice: Career is related but not synonymous. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

30. help / assist

Relation: near-synonymy. Why: both denote giving support. Caution: Assist is often more formal.

Practice: Collocations and register differ. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

31. hot / cold

Relation: gradable antonymy. Why: opposite ends of temperature scale. Caution: Intermediate values exist.

Practice: Add warm and cool to map the scale. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

32. tall / short

Relation: gradable antonymy. Why: opposite ends of height scale. Caution: Relative to comparison class.

Practice: A tall child may be shorter than a short adult. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

33. rich / poor

Relation: gradable antonymy. Why: contrast in wealth/resources. Caution: Social definitions vary.

Practice: Use context and criteria. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

34. fast / slow

Relation: gradable antonymy. Why: contrast in speed. Caution: Intermediate speed exists.

Practice: Scale can apply to processes and objects. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

35. bright / dark

Relation: gradable antonymy. Why: contrast in light. Caution: Also metaphorical senses exist.

Practice: Resolve literal vs metaphorical relation. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

36. alive / dead

Relation: complementary antonymy. Why: binary biological contrast. Caution: Borderline and metaphorical language complicate strict logic.

Practice: Treat as a useful model, not absolute natural-language law. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

37. present / absent

Relation: complementary antonymy. Why: presence vs non-presence. Caution: Context defines the relevant location/event.

Practice: Useful in attendance language. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

38. legal / illegal

Relation: complementary-like contrast. Why: permitted by law vs not permitted. Caution: Legal systems can contain grey areas.

Practice: Morphological negation does not guarantee perfect logical complementarity. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

39. true / false

Relation: complementary contrast. Why: truth-value opposition in formal contexts. Caution: Everyday statements can be uncertain or partly specified.

Practice: Distinguish logical from conversational use. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

40. buy / sell

Relation: converse relation. Why: same transaction from opposite roles. Caution: Buyer and seller roles reverse perspective.

Practice: Transform sentence perspective. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

41. lend / borrow

Relation: converse relation. Why: same transfer from lender/borrower roles. Caution: Grammar changes with perspective.

Practice: Practise subject–object reversal. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

42. give / receive

Relation: converse-like relation. Why: transfer viewed from source vs recipient. Caution: Not every give event implies intended receiving.

Practice: Context matters. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

43. employer / employee

Relation: relational converse. Why: roles defined relative to employment relation. Caution: One organisation can employ many people.

Practice: Relation is role-based. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

44. parent / child

Relation: relational converse. Why: kinship roles define each other. Caution: Age and legal/social complexities exist.

Practice: Conceptual relation remains reciprocal. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

45. teacher / student

Relation: relational pair. Why: roles within teaching relation. Caution: One person can be both in different contexts.

Practice: Perspective depends on event. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

46. north / south

Relation: directional opposition. Why: opposite cardinal directions. Caution: Not gradable like hot/cold.

Practice: Useful spatial contrast. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

47. above / below

Relation: relational opposition. Why: relative vertical positions. Caution: Requires reference frame.

Practice: A can be above B while below C. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

48. before / after

Relation: temporal opposition. Why: relative temporal order. Caution: Requires event pair.

Practice: Converse perspective on sequence. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

49. cause / effect

Relation: relational pair. Why: cause precedes/contributes to effect. Caution: Not synonyms or antonyms.

Practice: Shows semantic relation beyond classic lexical opposites. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

50. question / answer

Relation: functional pair. Why: answer responds to question. Caution: Not opposites in strict semantics.

Practice: Useful thematic relation. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

51. lock / key

Relation: functional association. Why: key operates lock. Caution: Not meronymy or synonymy.

Practice: Semantic association is broader than lexical relation types. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

52. knife / cut

Relation: instrument–function. Why: knife typically used to cut. Caution: Not all knives always cut; other tools cut too.

Practice: Separate association from definition. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

53. bird / wing

Relation: whole–part. Why: wing is part of bird. Caution: Meronymy, not hyponymy.

Practice: Bird is holonym in this relation. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

54. forest / tree

Relation: collection–member-like. Why: trees constitute forests. Caution: Not every forest is simply a list of trees.

Practice: Ecological concept adds complexity. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

55. fleet / ship

Relation: collection–member. Why: ship can be member of fleet. Caution: Fleet is collective whole.

Practice: Compare army–soldier. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

56. class / student

Relation: collection–member. Why: student belongs to class. Caution: Institutional membership.

Practice: Not physical part. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

57. word / sentence

Relation: component–structure. Why: word can be component of sentence. Caution: Sentence structure also includes grammatical relations.

Practice: Part–whole plus syntax. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

58. paragraph / essay

Relation: structural part–whole. Why: paragraph can be part of essay. Caution: Not every paragraph belongs to essay.

Practice: Text structure context matters. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

59. wheel / vehicle

Relation: part vs category contrast. Why: wheel is part of vehicle, not kind of vehicle. Caution: Classic diagnostic for meronymy vs hyponymy.

Practice: Ask ‘kind of?’ and ‘part of?’ separately. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

60. dog / animal

Relation: category hierarchy. Why: dog is kind of animal. Caution: Animal is hypernym.

Practice: Add mammal between levels for richer taxonomy. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

61. dog / cat

Relation: co-hyponymy. Why: both kinds of animal. Caution: They are related but incompatible as species labels in ordinary classification.

Practice: Co-hyponyms can contrast. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

62. red / blue

Relation: co-hyponymy/incompatibility. Why: both colours. Caution: One surface can contain both, so incompatibility depends on same respect/area.

Practice: Context limits logical claims. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

63. Monday / Tuesday

Relation: ordered co-hyponymy. Why: both days of week. Caution: Mutually exclusive as labels for one calendar day.

Practice: Semantic field plus sequence. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

64. January / February

Relation: ordered co-hyponymy. Why: both months. Caution: Share hypernym month.

Practice: Order adds relation beyond category. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

65. piano / violin

Relation: co-hyponymy. Why: both musical instruments. Caution: Different subcategories: keyboard vs string.

Practice: Taxonomy can be multi-level. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

66. apple / banana

Relation: co-hyponymy. Why: both fruit. Caution: Category membership supports analogy and sorting.

Practice: Not synonyms. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

67. square / rectangle

Relation: hyponymy under one mathematical definition. Why: square is a special kind of rectangle. Caution: Every square is rectangle; not every rectangle is square.

Practice: Useful example of nested category definitions. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

68. whale / mammal

Relation: hyponymy. Why: whale is a mammal. Caution: Surface resemblance to fish does not control scientific taxonomy.

Practice: Knowledge determines relation. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

69. penguin / bird

Relation: hyponymy. Why: penguin is bird. Caution: Flight is not defining requirement.

Practice: Category knowledge corrects prototype bias. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

70. virus / organism

Relation: contested taxonomy. Why: classification depends on biological definitions. Caution: Not every semantic relation is universally settled.

Practice: Domain expertise can make category boundaries contested. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

71. planet / celestial body

Relation: hyponymy. Why: planet is a kind of celestial body. Caution: Scientific definitions constrain membership.

Practice: Category systems can change historically. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

72. pluto / dwarf planet

Relation: classification relation. Why: Pluto classified as dwarf planet. Caution: Taxonomies can be institutionally revised.

Practice: Vocabulary meaning follows conceptual change. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

73. keyboard / key

Relation: whole–part. Why: key is part of keyboard. Caution: Key also has many other senses.

Practice: Sense resolution before meronymy. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

74. book / cover

Relation: whole–part. Why: cover is part of physical book. Caution: E-book lacks physical cover in same sense.

Practice: Technology changes typical meronymy. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

75. car / engine

Relation: whole–part. Why: engine can be part of car. Caution: Electric vehicles challenge older default assumptions.

Practice: Part relations can change with technology. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

76. cell / membrane

Relation: whole–part. Why: membrane is component of many cells. Caution: Biological nuance required.

Practice: Domain knowledge supports lexical relation accuracy. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

77. sentence / clause

Relation: structural hierarchy. Why: clause can be part of sentence. Caution: Some clauses can stand as sentences.

Practice: Grammar relation depends on construction. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

78. country / city

Relation: containment/location. Why: city can be located within country. Caution: Not meronymy in every theoretical treatment.

Practice: Geographical inclusion differs from component part. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

79. company / department

Relation: organisational part–whole. Why: department can be part of company. Caution: Institutional meronymy-like relation.

Practice: Useful for systems vocabulary. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

80. computer / software

Relation: system relation. Why: software runs within/for computer system. Caution: Not simple physical part relation.

Practice: Modern systems require abstract components. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

81. body / mind

Relation: conceptual pair. Why: strongly associated but not simple lexical opposite or part–whole relation. Caution: Relation depends on philosophical framework.

Practice: Not every association fits a standard semantic relation label. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

82. freedom / constraint

Relation: conceptual contrast. Why: often opposed in argument. Caution: Not strict antonyms in all senses.

Practice: Rhetorical contrast can be context-built. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

83. risk / safety

Relation: conceptual contrast. Why: often positioned as opposites. Caution: Both can coexist in degrees.

Practice: Scale and framing matter. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

84. success / failure

Relation: contrast. Why: outcome categories often opposed. Caution: Partial success complicates binary treatment.

Practice: Natural categories allow intermediate states. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

85. increase / decrease

Relation: directional gradable antonymy. Why: opposite directions of change. Caution: Stable can sit between them.

Practice: Useful in graph language. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

86. enter / exit

Relation: directional opposition. Why: movement into vs out of space/system. Caution: Perspective and path matter.

Practice: Useful relational verbs. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

87. accept / reject

Relation: complementary-like opposition. Why: decision outcomes often opposed. Caution: Deferral or partial acceptance creates other possibilities.

Practice: Institutional systems add states. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

88. remember / forget

Relation: contrast. Why: opposed memory outcomes. Caution: Partial recall exists.

Practice: Psychological processes are graded. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

89. learn / unlearn

Relation: morphological contrast. Why: unlearn means undo/change learned behaviour. Caution: Not simple absence of learning.

Practice: Morphology and semantics interact. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

90. possible / impossible

Relation: morphological complementary-like relation. Why: negation creates strong contrast. Caution: Context and modality matter.

Practice: Affix-based opposition needs semantic checking. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

91. regular / irregular

Relation: morphological contrast. Why: irregular negates conformity to pattern. Caution: Irregular can have technical meanings.

Practice: Prefix relation plus domain semantics. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

92. moral / immoral

Relation: morphological antonymy. Why: evaluative contrast. Caution: Moral systems differ.

Practice: Lexical relation can depend on cultural framework. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

93. appear / disappear

Relation: morphological opposition. Why: emergence vs ceasing to be visible. Caution: Disappear need not mean cease to exist.

Practice: Opposition occurs on visibility dimension. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

94. connect / disconnect

Relation: morphological opposition. Why: establish vs remove connection. Caution: Can describe physical, digital or social relation.

Practice: Shared root helps learning. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

95. include / exclude

Relation: oppositional verbs. Why: membership inclusion vs non-inclusion. Caution: Partial inclusion possible in real systems.

Practice: Useful set-membership vocabulary. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

96. maximum / minimum

Relation: scalar endpoints. Why: highest vs lowest values. Caution: Exact definitions depend on domain.

Practice: Mathematical antonymy. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

97. ancestor / descendant

Relation: converse kinship. Why: same genealogical relation from opposite directions. Caution: Each term defined relative to another person.

Practice: Role relation rather than gradable opposite. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

98. predecessor / successor

Relation: converse temporal/order relation. Why: positions before vs after. Caution: Common in offices, sequences and technology.

Practice: Perspective and order encoded lexically. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

99. teacher / teaching

Relation: morphological/role relation. Why: person vs activity. Caution: Not semantic opposition.

Practice: Word-family link differs from lexical relation. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

100. nation / national

Relation: derivational relation. Why: noun concept vs adjective relation. Caution: Meaning related through morphology.

Practice: Do not confuse derivation with synonymy. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

101. science / scientific

Relation: derivational relation. Why: field vs adjective. Caution: Shared root, different grammatical function.

Practice: Morphology supports semantic network. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

102. decide / decision

Relation: derivational relation. Why: process verb vs result/event noun. Caution: Closely related but not interchangeable.

Practice: Word family enriches vocabulary depth. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

103. speak / speaker

Relation: derivational role relation. Why: action vs agent. Caution: Form relation maps participant role.

Practice: Morphology and semantics combine. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

104. teach / learn

Relation: relationally linked but not converse in every event. Why: teaching aims at learning. Caution: One can teach without learning occurring.

Practice: Conceptual relation is causal/intentional, not strict converse. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

105. doctor / hospital

Relation: domain association. Why: strongly related in healthcare field. Caution: Doctor is not kind of hospital or part in a fixed lexical sense.

Practice: Semantic-field membership differs from taxonomic relation. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

106. rain / umbrella

Relation: situational association. Why: umbrella used when raining. Caution: Not lexical-semantic relation in narrow sense.

Practice: Associative knowledge still supports comprehension. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

107. fire / smoke

Relation: causal association. Why: fire can cause smoke. Caution: Not synonymy or meronymy.

Practice: World knowledge links vocabulary. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

108. seed / plant

Relation: developmental relation. Why: seed can develop into plant. Caution: Temporal transformation relation.

Practice: Vocabulary networks include event knowledge. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

109. student / graduate

Relation: life-stage relation. Why: student can become graduate. Caution: Temporal/institutional relation.

Practice: Not simple antonymy. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

110. question / curiosity

Relation: conceptual association. Why: questions can express curiosity. Caution: Not definitional equivalence.

Practice: Semantic networks include looser links. Then create one second example with the same relation and one near-miss that looks related but belongs to a different relation. Explaining the near-miss is the depth test.

40. Diagnostic atlas: twenty failures in semantic-relation knowledge

1. Learner calls every related word a synonym

Likely gap: Relation-type confusion. First repair: Sort examples into similarity, contrast, category, part–whole and association. Why: Related does not mean same meaning. Retest with new vocabulary so the learner must reconstruct the relation rather than remember the example.

2. Learner says wheel is a type of car

Likely gap: Hyponymy–meronymy confusion. First repair: Use ‘kind of’ versus ‘part of’ diagnostic frames. Why: Category and component relations are different. Retest with new vocabulary so the learner must reconstruct the relation rather than remember the example.

3. Learner cannot move from specific examples to categories

Likely gap: Weak hypernymic structure. First repair: Practise naming superordinates and nested categories. Why: Generalisation supports summarisation and learning. Retest with new vocabulary so the learner must reconstruct the relation rather than remember the example.

4. Learner gives only broad category words in writing

Likely gap: Weak hyponymic precision. First repair: Generate more specific category members for key nouns and verbs. Why: Specificity depends on access to narrower terms. Retest with new vocabulary so the learner must reconstruct the relation rather than remember the example.

5. Learner repeats the same noun constantly

Likely gap: Limited synonym/hypernym options. First repair: Build a controlled relation map rather than random thesaurus substitutions. Why: Variation must preserve meaning. Retest with new vocabulary so the learner must reconstruct the relation rather than remember the example.

6. Learner chooses near-synonyms badly

Likely gap: Weak boundary knowledge. First repair: Compare contexts where substitution changes register or connotation. Why: Similarity is not interchangeability. Retest with new vocabulary so the learner must reconstruct the relation rather than remember the example.

7. Learner knows antonym pairs but not scales

Likely gap: Shallow contrast knowledge. First repair: Map intermediate values and degree language. Why: Gradable opposition is more than two endpoints. Retest with new vocabulary so the learner must reconstruct the relation rather than remember the example.

8. Learner treats buy/sell as ordinary opposites

Likely gap: Missing converse relation concept. First repair: Rewrite same event from different participant roles. Why: Perspective explains the lexical change. Retest with new vocabulary so the learner must reconstruct the relation rather than remember the example.

9. Learner memorises domain vocabulary as isolated list

Likely gap: Weak semantic-field integration. First repair: Connect items by category, function, part and contrast. Why: Domain structure reduces isolation. Retest with new vocabulary so the learner must reconstruct the relation rather than remember the example.

10. Learner confuses homonyms with polysemy

Likely gap: Sense-structure confusion. First repair: Ask whether meanings are historically/conceptually related and consult dictionaries. Why: One form can belong to separate networks. Retest with new vocabulary so the learner must reconstruct the relation rather than remember the example.

11. Learner builds wrong taxonomy from prototypes

Likely gap: Prototype bias. First repair: Use defining category features rather than surface resemblance. Why: Penguins are birds despite not flying. Retest with new vocabulary so the learner must reconstruct the relation rather than remember the example.

12. Learner assumes categories are always fixed

Likely gap: Over-rigid taxonomy. First repair: Use disputed scientific or social classifications. Why: Category systems can change or remain contested. Retest with new vocabulary so the learner must reconstruct the relation rather than remember the example.

13. Learner cannot explain systems

Likely gap: Weak meronymic structure. First repair: Map whole, components and functions. Why: Part–whole vocabulary supports causal explanation. Retest with new vocabulary so the learner must reconstruct the relation rather than remember the example.

14. Learner uses broad words where precise ones exist

Likely gap: Weak hyponym access. First repair: Move down the taxonomy deliberately. Why: Specific writing often needs narrower category members. Retest with new vocabulary so the learner must reconstruct the relation rather than remember the example.

15. Learner uses very narrow words without audience support

Likely gap: Over-specificity. First repair: Move up to a hypernym when shared knowledge is uncertain. Why: Generalisation can improve accessibility. Retest with new vocabulary so the learner must reconstruct the relation rather than remember the example.

16. Learner groups similar words and confuses them

Likely gap: Semantic interference. First repair: Separate learning sessions and contrast boundaries explicitly. Why: Grouping can help organisation but increase competition. Retest with new vocabulary so the learner must reconstruct the relation rather than remember the example.

17. Learner identifies semantic field but not relation

Likely gap: Field-vs-relation confusion. First repair: Label exact link inside the field. Why: Belonging to same domain is weaker than synonymy or hyponymy. Retest with new vocabulary so the learner must reconstruct the relation rather than remember the example.

18. Learner uses morphology as proof of meaning

Likely gap: Form–meaning confusion. First repair: Check derived forms individually. Why: Shared roots support but do not guarantee semantic equivalence. Retest with new vocabulary so the learner must reconstruct the relation rather than remember the example.

19. Learner accepts AI-generated relation maps uncritically

Likely gap: Verification gap. First repair: Check relation with diagnostic frames and authoritative sources. Why: Fluent output can still classify incorrectly. Retest with new vocabulary so the learner must reconstruct the relation rather than remember the example.

20. Learner cannot paraphrase when word retrieval fails

Likely gap: Network access gap. First repair: Practise hypernym, function and contrast circumlocution. Why: Relational knowledge provides alternate retrieval routes. Retest with new vocabulary so the learner must reconstruct the relation rather than remember the example.

41. Thirty-five semantic-relation practice routines

1. Kind-of test

Ask whether ‘X is a kind of Y’ works naturally. Success criterion: the learner should name the relation and justify why it holds. A correct-looking pair without an explanation can still hide guessing.

2. Part-of test

Ask whether ‘X is part of Y’ describes the relation. Success criterion: the learner should name the relation and justify why it holds. A correct-looking pair without an explanation can still hide guessing.

3. Sibling sort

Give one hypernym and sort possible co-hyponyms under it. Success criterion: the learner should name the relation and justify why it holds. A correct-looking pair without an explanation can still hide guessing.

4. Category ladder

Move from very general to very specific labels. Success criterion: the learner should name the relation and justify why it holds. A correct-looking pair without an explanation can still hide guessing.

5. Zoom-out summary

Replace several hyponyms with one hypernym to compress a paragraph. Success criterion: the learner should name the relation and justify why it holds. A correct-looking pair without an explanation can still hide guessing.

6. Zoom-in precision

Replace a broad hypernym with the correct hyponym where detail matters. Success criterion: the learner should name the relation and justify why it holds. A correct-looking pair without an explanation can still hide guessing.

7. Part–whole map

Draw a system and label components with meronymic arrows. Success criterion: the learner should name the relation and justify why it holds. A correct-looking pair without an explanation can still hide guessing.

8. Whole-from-part inference

Given a component, identify likely holonyms and compare possibilities. Success criterion: the learner should name the relation and justify why it holds. A correct-looking pair without an explanation can still hide guessing.

9. Near-synonym boundary

Write two contexts where only one near-synonym sounds right. Success criterion: the learner should name the relation and justify why it holds. A correct-looking pair without an explanation can still hide guessing.

10. Antonym type sort

Classify opposites as gradable, complementary, converse or directional. Success criterion: the learner should name the relation and justify why it holds. A correct-looking pair without an explanation can still hide guessing.

11. Scale building

Place gradable antonyms and intermediate words on a continuum. Success criterion: the learner should name the relation and justify why it holds. A correct-looking pair without an explanation can still hide guessing.

12. Converse rewrite

Rewrite buy/sell, lend/borrow or employer/employee from the other participant’s perspective. Success criterion: the learner should name the relation and justify why it holds. A correct-looking pair without an explanation can still hide guessing.

13. Semantic field web

Build a domain network and label exact relations inside it. Success criterion: the learner should name the relation and justify why it holds. A correct-looking pair without an explanation can still hide guessing.

14. Sense-first relation

Choose one polysemous word, separate senses, then map each sense independently. Success criterion: the learner should name the relation and justify why it holds. A correct-looking pair without an explanation can still hide guessing.

15. Homonym split

Place unrelated senses of the same form into separate concept maps. Success criterion: the learner should name the relation and justify why it holds. A correct-looking pair without an explanation can still hide guessing.

16. Morphology check

Connect word-family forms while noting which relation is morphological rather than synonymic. Success criterion: the learner should name the relation and justify why it holds. A correct-looking pair without an explanation can still hide guessing.

17. Collocation overlay

Add common phrase partners to a semantic network. Success criterion: the learner should name the relation and justify why it holds. A correct-looking pair without an explanation can still hide guessing.

18. Category error hunt

Find statements that confuse part-of with kind-of and repair them. Success criterion: the learner should name the relation and justify why it holds. A correct-looking pair without an explanation can still hide guessing.

19. Prototype challenge

Use atypical category members such as penguin or whale to test definitions. Success criterion: the learner should name the relation and justify why it holds. A correct-looking pair without an explanation can still hide guessing.

20. Domain taxonomy

Build a classification for one school subject or profession. Success criterion: the learner should name the relation and justify why it holds. A correct-looking pair without an explanation can still hide guessing.

21. Reading relation hunt

Underline hypernyms, examples, contrasts and parts in an explanatory text. Success criterion: the learner should name the relation and justify why it holds. A correct-looking pair without an explanation can still hide guessing.

22. Writing specificity ladder

Draft one sentence at three levels of categorical specificity. Success criterion: the learner should name the relation and justify why it holds. A correct-looking pair without an explanation can still hide guessing.

23. Paraphrase by hypernym

Explain a forgotten word using its broader category and distinguishing feature. Success criterion: the learner should name the relation and justify why it holds. A correct-looking pair without an explanation can still hide guessing.

24. Paraphrase by function

Explain a forgotten object by what it does and what system it belongs to. Success criterion: the learner should name the relation and justify why it holds. A correct-looking pair without an explanation can still hide guessing.

25. WordNet comparison

Compare a learner’s category map with a lexical database and discuss mismatches. Success criterion: the learner should name the relation and justify why it holds. A correct-looking pair without an explanation can still hide guessing.

26. Dictionary–thesaurus pair

Read a definition, then inspect relational alternatives in a thesaurus. Success criterion: the learner should name the relation and justify why it holds. A correct-looking pair without an explanation can still hide guessing.

27. False synonym check

Take three thesaurus suggestions and eliminate the ones that alter register or meaning. Success criterion: the learner should name the relation and justify why it holds. A correct-looking pair without an explanation can still hide guessing.

28. Co-hyponym memory game

Retrieve as many members of one category as possible, then group by subcategory. Success criterion: the learner should name the relation and justify why it holds. A correct-looking pair without an explanation can still hide guessing.

29. Meronym function task

Name a component and explain what role it performs in the whole. Success criterion: the learner should name the relation and justify why it holds. A correct-looking pair without an explanation can still hide guessing.

30. Cross-language taxonomy

Compare how two languages divide one semantic domain. Success criterion: the learner should name the relation and justify why it holds. A correct-looking pair without an explanation can still hide guessing.

31. Semantic relation journal

Record a new word with one hypernym, one contrast, one phrase and one example. Success criterion: the learner should name the relation and justify why it holds. A correct-looking pair without an explanation can still hide guessing.

32. Relation retrieval

Given the hypernym, retrieve the target; later reverse the cue. Success criterion: the learner should name the relation and justify why it holds. A correct-looking pair without an explanation can still hide guessing.

33. Delayed network recall

Recreate a concept map days later without the original notes. Success criterion: the learner should name the relation and justify why it holds. A correct-looking pair without an explanation can still hide guessing.

34. AI audit

Ask AI for a semantic network, then mark verified, questionable and wrong links. Success criterion: the learner should name the relation and justify why it holds. A correct-looking pair without an explanation can still hide guessing.

35. Concept-map transfer

Use the same relation structure in a new topic. Success criterion: the learner should name the relation and justify why it holds. A correct-looking pair without an explanation can still hide guessing.

42. Frequently asked questions about semantic and lexical relations

What is a semantic relation?

A relationship between meanings or word senses, such as similarity, opposition, category inclusion or part–whole structure.

What is a lexical relation?

A systematic relationship involving lexical items; some lexical relations are semantic, while lexical knowledge can also include form and collocational patterns.

What is synonymy?

A relation of same or very similar meaning.

Are synonyms perfectly interchangeable?

Usually not. Register, collocation, connotation and sense boundaries often differ.

What is antonymy?

A relation of semantic opposition or conventional contrast.

What are gradable antonyms?

Opposites on a scale, such as hot/cold or tall/short.

What are complementary antonyms?

Contrasts commonly treated as mutually exclusive states, such as alive/dead in ordinary biological use.

What are converse terms?

Words describing the same relation from opposite participant roles, such as buy/sell or lend/borrow.

What is a hyponym?

A more specific item inside a broader category, such as rose under flower.

What is a hypernym?

A broader category term that contains more specific hyponyms, such as animal above dog.

What are co-hyponyms?

Category members sharing the same hypernym, such as cat and dog under animal.

What is meronymy?

A part–whole relation where one concept is a part of another, such as wheel and bicycle.

What is holonymy?

The inverse whole–part relation: bicycle is the holonym of wheel in that example.

What is a semantic field?

A network of meanings connected to a shared domain such as law, weather or emotion.

Is a semantic field the same as synonymy?

No. Words can belong to the same field while having completely different meanings and grammatical roles.

Is a wheel a hyponym of car?

No. A wheel is typically a part of a car, so the relation is meronymic rather than hyponymic.

Is dog a hyponym of animal?

Yes. Dog is a more specific category member under the broader category animal.

Why are word relationships useful for vocabulary?

They organise meanings into networks, improve retrieval and help learners distinguish similar concepts.

Do semantic relations exist between words or concepts?

Different theories answer differently. Many relations are most safely described between senses or concepts rather than bare word forms.

What is incompatibility?

A relation where related category members exclude one another in the same respect, such as different species labels in a simple classification.

What is the difference between polysemy and semantic relations?

Polysemy concerns multiple related senses of one lexical form; semantic relations connect senses to other senses or concepts.

What is the difference between morphology and semantic relation?

Morphology relates word forms structurally; semantic relations concern meanings. The two often overlap but are not identical.

What is WordNet?

A lexical database that groups word senses into synonym sets and links those sets with semantic relations.

How do semantic relations help reading?

They support category inference, contrast, system understanding and integration with prior knowledge.

How do semantic relations help writing?

They give writers ways to move between general and specific vocabulary and choose precise contrasts.

How do teachers assess semantic relations?

Through sorting, hypernym/hyponym tasks, part–whole maps, synonym contrasts and relation explanations.

Can AI build semantic maps?

Yes, but important links should be checked because AI can misclassify categories, senses or part–whole relations.

What is the simplest relation test?

Ask whether the relation is similarity, contrast, kind-of, part-of, role-perspective, or merely general association.

43. Research and reference grounding

Cambridge’s Lexical Meaning treats semantic relations as relations between senses and discusses synonymy, antonymy, hyponymy, hyperonymy, meronymy, holonymy and semantic fields as core parts of lexical semantics. It also distinguishes semantic relations from broader lexical relationships involving form or collocational behaviour.

Cambridge’s Introducing Semantics similarly highlights antonymy, meronymy, hyponymy/taxonomy and synonymy as especially useful meaning relations for semantic description. Importantly, Cambridge work on Semantic Relations and the Lexicon cautions that inclusion and part–whole relations such as hyponymy and meronymy may often be better analysed as relations among concepts or denoted things rather than simple direct links between word forms.

This is why the article consistently uses phrases such as “word senses and concepts” rather than pretending that every semantic relation is a mechanical dictionary arrow. The educational model remains valuable: category, contrast and part–whole structure give learners a usable map of vocabulary while the theoretical caveat protects accuracy.

• Cambridge University Press — Lexical and semantic relations
• Cambridge University Press — Analysing and distinguishing meanings
• Cambridge University Press — Semantic Relations and the Lexicon
• Cambridge Dictionary — Synonymy
• Cambridge Dictionary — Antonymy

44. Where to go next in the eduKate vocabulary ecosystem

• What Is Vocabulary? — broad vocabulary definition.
• Vocabulary | Word Knowledge — dimensions of knowing a word.
• Vocabulary | Mental Lexicon — storage, activation and retrieval.
• Vocabulary | Polysemy and Multiple Meanings — sense variation within one form.
• Meronymy and Holonymy — part–whole relations.
• Lexical Incompatibility and Co-hyponymy — sibling category relations and exclusion.
• Semantic Fields and Lexical Fields — domain organisation.
• What Is Vocabulary | Denotation and Connotation — core meaning and association.
• Vocabulary | Primary 1 to Adult & Career Vocabulary — master router.
• Vocabulary Learning Hub — level-based vocabulary routes.

45. Final model: vocabulary is a network of distinctions

A word is easier to understand when we know what is similar to it, what contrasts with it, what broader category contains it and what parts or members belong around it. Semantic relations turn vocabulary from a flat inventory into a structured conceptual system.

Synonymy supplies similarity, antonymy supplies contrast, hyponymy supplies category inclusion, meronymy supplies part–whole structure and semantic fields supply broader domain organisation. These relations do different jobs, and confusing them produces predictable errors.

The deeper lesson is that lexical knowledge is relational. Definitions remain essential, but definitions alone do not show the neighbourhood in which the word functions. Mature vocabulary combines meaning, relation, usage and retrieval.

Do not only ask, “What does this word mean?” Ask, “Where does this meaning live?”

46. Second-stage semantic-relation transfer lab

The first laboratory identifies relationships. This second stage tests whether the learner can carry those relationships into new vocabulary rather than memorising labels.

1. Transfer extension: rose / flower

Reconstruct: hide the original relation label hyponymy and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

2. Transfer extension: sparrow / bird

Reconstruct: hide the original relation label hyponymy and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

3. Transfer extension: car / vehicle

Reconstruct: hide the original relation label hyponymy and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

4. Transfer extension: violin / instrument

Reconstruct: hide the original relation label hyponymy and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

5. Transfer extension: oak / tree

Reconstruct: hide the original relation label hyponymy and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

6. Transfer extension: laptop / computer

Reconstruct: hide the original relation label hyponymy and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

7. Transfer extension: triangle / polygon

Reconstruct: hide the original relation label hyponymy and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

8. Transfer extension: novel / book

Reconstruct: hide the original relation label hyponymy and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

9. Transfer extension: doctor / professional

Reconstruct: hide the original relation label hyponymy and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

10. Transfer extension: democracy / political system

Reconstruct: hide the original relation label hyponymy and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

11. Transfer extension: wheel / bicycle

Reconstruct: hide the original relation label meronymy and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

12. Transfer extension: chapter / book

Reconstruct: hide the original relation label meronymy and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

13. Transfer extension: keyboard / computer

Reconstruct: hide the original relation label meronymy and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

14. Transfer extension: nucleus / cell

Reconstruct: hide the original relation label meronymy and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

15. Transfer extension: branch / tree

Reconstruct: hide the original relation label meronymy and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

16. Transfer extension: room / house

Reconstruct: hide the original relation label meronymy and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

17. Transfer extension: member / team

Reconstruct: hide the original relation label member–collection and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

18. Transfer extension: soldier / army

Reconstruct: hide the original relation label member–collection and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

19. Transfer extension: steel / bridge

Reconstruct: hide the original relation label substance–object and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

20. Transfer extension: water / lake

Reconstruct: hide the original relation label substance–container and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

21. Transfer extension: begin / start

Reconstruct: hide the original relation label near-synonymy and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

22. Transfer extension: big / large

Reconstruct: hide the original relation label near-synonymy and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

23. Transfer extension: buy / purchase

Reconstruct: hide the original relation label near-synonymy and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

24. Transfer extension: ask / request

Reconstruct: hide the original relation label near-synonymy and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

25. Transfer extension: child / kid

Reconstruct: hide the original relation label near-synonymy and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

26. Transfer extension: angry / furious

Reconstruct: hide the original relation label near-synonymy and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

27. Transfer extension: thin / slim

Reconstruct: hide the original relation label near-synonymy and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

28. Transfer extension: mistake / error

Reconstruct: hide the original relation label near-synonymy and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

29. Transfer extension: job / occupation

Reconstruct: hide the original relation label near-synonymy and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

30. Transfer extension: help / assist

Reconstruct: hide the original relation label near-synonymy and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

31. Transfer extension: hot / cold

Reconstruct: hide the original relation label gradable antonymy and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

32. Transfer extension: tall / short

Reconstruct: hide the original relation label gradable antonymy and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

33. Transfer extension: rich / poor

Reconstruct: hide the original relation label gradable antonymy and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

34. Transfer extension: fast / slow

Reconstruct: hide the original relation label gradable antonymy and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

35. Transfer extension: bright / dark

Reconstruct: hide the original relation label gradable antonymy and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

36. Transfer extension: alive / dead

Reconstruct: hide the original relation label complementary antonymy and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

37. Transfer extension: present / absent

Reconstruct: hide the original relation label complementary antonymy and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

38. Transfer extension: legal / illegal

Reconstruct: hide the original relation label complementary-like contrast and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

39. Transfer extension: true / false

Reconstruct: hide the original relation label complementary contrast and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

40. Transfer extension: buy / sell

Reconstruct: hide the original relation label converse relation and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

41. Transfer extension: lend / borrow

Reconstruct: hide the original relation label converse relation and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

42. Transfer extension: give / receive

Reconstruct: hide the original relation label converse-like relation and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

43. Transfer extension: employer / employee

Reconstruct: hide the original relation label relational converse and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

44. Transfer extension: parent / child

Reconstruct: hide the original relation label relational converse and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

45. Transfer extension: teacher / student

Reconstruct: hide the original relation label relational pair and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

46. Transfer extension: north / south

Reconstruct: hide the original relation label directional opposition and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

47. Transfer extension: above / below

Reconstruct: hide the original relation label relational opposition and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

48. Transfer extension: before / after

Reconstruct: hide the original relation label temporal opposition and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

49. Transfer extension: cause / effect

Reconstruct: hide the original relation label relational pair and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

50. Transfer extension: question / answer

Reconstruct: hide the original relation label functional pair and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

51. Transfer extension: lock / key

Reconstruct: hide the original relation label functional association and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

52. Transfer extension: knife / cut

Reconstruct: hide the original relation label instrument–function and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

53. Transfer extension: bird / wing

Reconstruct: hide the original relation label whole–part and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

54. Transfer extension: forest / tree

Reconstruct: hide the original relation label collection–member-like and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

55. Transfer extension: fleet / ship

Reconstruct: hide the original relation label collection–member and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

56. Transfer extension: class / student

Reconstruct: hide the original relation label collection–member and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

57. Transfer extension: word / sentence

Reconstruct: hide the original relation label component–structure and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

58. Transfer extension: paragraph / essay

Reconstruct: hide the original relation label structural part–whole and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

59. Transfer extension: wheel / vehicle

Reconstruct: hide the original relation label part vs category contrast and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

60. Transfer extension: dog / animal

Reconstruct: hide the original relation label category hierarchy and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

61. Transfer extension: dog / cat

Reconstruct: hide the original relation label co-hyponymy and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

62. Transfer extension: red / blue

Reconstruct: hide the original relation label co-hyponymy/incompatibility and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

63. Transfer extension: Monday / Tuesday

Reconstruct: hide the original relation label ordered co-hyponymy and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

64. Transfer extension: January / February

Reconstruct: hide the original relation label ordered co-hyponymy and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

65. Transfer extension: piano / violin

Reconstruct: hide the original relation label co-hyponymy and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

66. Transfer extension: apple / banana

Reconstruct: hide the original relation label co-hyponymy and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

67. Transfer extension: square / rectangle

Reconstruct: hide the original relation label hyponymy under one mathematical definition and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

68. Transfer extension: whale / mammal

Reconstruct: hide the original relation label hyponymy and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

69. Transfer extension: penguin / bird

Reconstruct: hide the original relation label hyponymy and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

70. Transfer extension: virus / organism

Reconstruct: hide the original relation label contested taxonomy and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

71. Transfer extension: planet / celestial body

Reconstruct: hide the original relation label hyponymy and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

72. Transfer extension: pluto / dwarf planet

Reconstruct: hide the original relation label classification relation and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

73. Transfer extension: keyboard / key

Reconstruct: hide the original relation label whole–part and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

74. Transfer extension: book / cover

Reconstruct: hide the original relation label whole–part and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

75. Transfer extension: car / engine

Reconstruct: hide the original relation label whole–part and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

76. Transfer extension: cell / membrane

Reconstruct: hide the original relation label whole–part and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

77. Transfer extension: sentence / clause

Reconstruct: hide the original relation label structural hierarchy and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

78. Transfer extension: country / city

Reconstruct: hide the original relation label containment/location and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

79. Transfer extension: company / department

Reconstruct: hide the original relation label organisational part–whole and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

80. Transfer extension: computer / software

Reconstruct: hide the original relation label system relation and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

81. Transfer extension: body / mind

Reconstruct: hide the original relation label conceptual pair and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

82. Transfer extension: freedom / constraint

Reconstruct: hide the original relation label conceptual contrast and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

83. Transfer extension: risk / safety

Reconstruct: hide the original relation label conceptual contrast and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

84. Transfer extension: success / failure

Reconstruct: hide the original relation label contrast and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

85. Transfer extension: increase / decrease

Reconstruct: hide the original relation label directional gradable antonymy and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

86. Transfer extension: enter / exit

Reconstruct: hide the original relation label directional opposition and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

87. Transfer extension: accept / reject

Reconstruct: hide the original relation label complementary-like opposition and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

88. Transfer extension: remember / forget

Reconstruct: hide the original relation label contrast and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

89. Transfer extension: learn / unlearn

Reconstruct: hide the original relation label morphological contrast and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

90. Transfer extension: possible / impossible

Reconstruct: hide the original relation label morphological complementary-like relation and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

91. Transfer extension: regular / irregular

Reconstruct: hide the original relation label morphological contrast and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

92. Transfer extension: moral / immoral

Reconstruct: hide the original relation label morphological antonymy and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

93. Transfer extension: appear / disappear

Reconstruct: hide the original relation label morphological opposition and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

94. Transfer extension: connect / disconnect

Reconstruct: hide the original relation label morphological opposition and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

95. Transfer extension: include / exclude

Reconstruct: hide the original relation label oppositional verbs and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

96. Transfer extension: maximum / minimum

Reconstruct: hide the original relation label scalar endpoints and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

97. Transfer extension: ancestor / descendant

Reconstruct: hide the original relation label converse kinship and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

98. Transfer extension: predecessor / successor

Reconstruct: hide the original relation label converse temporal/order relation and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

99. Transfer extension: teacher / teaching

Reconstruct: hide the original relation label morphological/role relation and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

100. Transfer extension: nation / national

Reconstruct: hide the original relation label derivational relation and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

101. Transfer extension: science / scientific

Reconstruct: hide the original relation label derivational relation and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

102. Transfer extension: decide / decision

Reconstruct: hide the original relation label derivational relation and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

103. Transfer extension: speak / speaker

Reconstruct: hide the original relation label derivational role relation and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

104. Transfer extension: teach / learn

Reconstruct: hide the original relation label relationally linked but not converse in every event and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

105. Transfer extension: doctor / hospital

Reconstruct: hide the original relation label domain association and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

106. Transfer extension: rain / umbrella

Reconstruct: hide the original relation label situational association and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

107. Transfer extension: fire / smoke

Reconstruct: hide the original relation label causal association and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

108. Transfer extension: seed / plant

Reconstruct: hide the original relation label developmental relation and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

109. Transfer extension: student / graduate

Reconstruct: hide the original relation label life-stage relation and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.

110. Transfer extension: question / curiosity

Reconstruct: hide the original relation label conceptual association and explain the connection in ordinary language first. Then choose the technical label and justify it. This prevents terminology from replacing understanding.

Transform: build a new example with the same relation, then alter one member so the relation changes. Explain what new relation now holds. The learner succeeds only when the structure transfers beyond the memorised pair.