Siksha Sarovar

Siksha Sarovar (sikshasarovar.com) is a free educational web application that helps students in India learn programming and prepare for academic and competitive exams. The platform offers structured coding courses (C, C++, Python, Java, HTML, CSS, PHP, Power BI, AI, Machine Learning, Data Science), complete university curriculum notes for BCA/MCA students with previous year question papers, Class 10 and Class 12 CBSE/HBSE school notes, and dedicated preparation material for SSC, UPSC, Banking, Railway and other government exams. Browsing the site is completely free and requires no account. Users may optionally sign in with Google solely to save their learning progress, quiz scores and personal preferences across devices.

Privacy Policy | Terms of Service | Contact Siksha Sarovar | About Siksha Sarovar

v4.0.9 · PWA
Siksha Sarovar logo
Siksha Sarovar
Your Learning Universe

Siksha Sarovar is a free e-learning platform for coding courses, BCA university notes and competitive exam preparation. Optional Google sign-in saves your learning progress across devices.

Initializing knowledge base…
Compiling modules 0%

Unit 3 — Explanation-Based Learning

Lesson 29 of 34 in the free Artificial Intelligence notes on Siksha Sarovar, written by Rohit Jangra.

Explanation-Based Learning (EBL)

Explanation-Based Learning generalises from just one training example — instead of needing many examples like induction, EBL uses a domain theory (existing background knowledge) to explain why the example is an instance of the target concept, and then generalises that explanation.

EBL vs Induction

Inductive learningExplanation-based learning
Number of examples neededManyJust one (in principle)
Requires prior domain knowledge?NoYes — a domain theory is essential
What is generalisedStatistical regularities across examplesThe logical explanation of the single example
RiskWrong generalisation from insufficient/biased dataGeneralisation is only as correct as the domain theory

The Four Inputs to EBL

InputMeaning
Target conceptThe concept to be learned (a definition to acquire, e.g., "safe-to-stack")
Training exampleOne instance of the target concept
Domain theoryA set of rules/facts sufficient to explain why the example satisfies the target concept
Operationality criterionA description of the form the final learned rule must take, so it is efficiently usable later

The EBL Process

Worked Example: "Safe to Stack"

Training example: a specific cup is safe to stack on a specific table.

A domain theory contains general facts such as: an object is stackable on another if the supporting object's top is flat and the supported object's weight is less than the support's strength.

EBL constructs the specific proof for this one example (this particular cup, this particular table), then generalises the proof by replacing the specific objects with variables wherever the proof did not depend on their exact identity — yielding a reusable rule: any lightweight object with a flat base is safe to stack on any object whose top is flat and strong enough. Only the properties that the proof actually used (flat top, sufficient strength, low weight) survive into the generalised rule — irrelevant details of the one example (colour, exact size) are dropped.

Why "Explanation-Based" Rather Than "Example-Based"

The real work is done by the domain theory's explanation, not by statistically pooling many examples — the single example merely triggers the system to construct and then generalise a proof it could, in principle, have constructed without any example at all, given enough time. EBL is therefore sometimes described as "learning by deduction" rather than learning by generalisation from data.

Strengths and Limitations

StrengthsLimitations
Learns correctly from a single exampleRequires a domain theory that is already complete and correct
Produces provably correct generalisations (given a correct domain theory)Cannot learn anything genuinely new that the domain theory couldn't already, in principle, derive
Speeds up future problem solving by caching the generalised, operational ruleDomain theories are often expensive or impossible to build for real-world domains