Output of KDD: Data, Information, Queries, and Useful Information
Knowledge Discovery in Databases (KDD ) is commonly described as a pipeline that transforms raw data into actionable, domain-relevant knowledge. In that sense, the output is not merely “data again,” but useful information/knowledge derived from data through cleaning, integration, mining, and interpretation. Core references describe KDD as producing patterns and knowledge that are meaningful and usable for the target domain after interpretation and evaluation steps. These outputs are best characterized as useful information rather than “query” results alone.3
Key terms you’ll see throughout this section:
- KDD
- Data mining
- Pattern
- Knowledge
Footnotes
-
Knowledge discovery in databases — Wikipedia - Describes KDD as the overall process to extract knowledge from data; emphasizes knowledge discovery framing. ↩
-
Fayyad, Piatetsky-Shapiro, Smyth (KDD): From data mining to knowledge discovery in databases - Foundational framing of KDD steps and the goal of extracting useful knowledge from data. ↩
-
Data mining vs. knowledge discovery in databases — Wikipedia (KDD context) - Discusses data mining as part of KDD and the need for interpretation/evaluation for useful outcomes. ↩
KDD (Knowledge Discovery in Databases) overview: steps and output
Why the correct option is “useful information”
In the KDD process, raw data is transformed into intermediate representations (e.g., cleaned/integrated datasets and mined patterns), and then into interpreted knowledge that satisfies the goal of the application (e.g., decision support, prediction, or understanding). Foundational descriptions emphasize that KDD outputs knowledge that is valid, novel, potentially useful, and understandable after mining and interpretation, not just data or generic mining artifacts.2
- (i) data: This is an input (raw/cleaned datasets). While cleaned data may be produced as an intermediate artifact, KDD’s “output” is not defined as the final output being raw data itself.2
- (ii) information: “Information” is sometimes used informally for derived results, but in KDD literature the final deliverable is better grounded as interpreted knowledge derived from patterns.2
- (iii) query: A “query” is typically part of information retrieval or database querying, not the final goal of KDD. KDD can involve query-like tasks (e.g., selecting records), but it is not defined as producing “a query” as its output.2
- (iv) useful information: This aligns directly with KDD’s emphasis on potentially useful knowledge/information resulting from pattern extraction plus interpretation and evaluation.3
Footnotes
-
Knowledge discovery in databases — Wikipedia - Describes KDD as the overall process to extract knowledge from data; emphasizes knowledge discovery framing. ↩ ↩2 ↩3
-
Fayyad, Piatetsky-Shapiro, Smyth (KDD): From data mining to knowledge discovery in databases - Foundational framing of KDD steps and the goal of extracting useful knowledge from data. ↩ ↩2 ↩3
-
SQL (Structured Query Language) — Wikipedia - Explains SQL as a querying language used to retrieve/filter data, contrasting with KDD’s discovery/knowledge goals. ↩ ↩2
-
Data mining vs. knowledge discovery in databases — Wikipedia (KDD context) - Discusses data mining as part of KDD and the need for interpretation/evaluation for useful outcomes. ↩ ↩2
-
Information retrieval — Wikipedia - Defines retrieval as finding relevant information via queries, helping distinguish it from KDD’s knowledge discovery output. ↩
How KDD turns data into useful information (conceptual pipeline)
- 1Step 1
Choose a target domain goal and identify the relevant dataset to support the discovery task.
- 2Step 2
Clean, integrate, and transform data to support reliable pattern discovery.
- 3Step 3
Use mining algorithms to find candidate patterns/models from the prepared data.
- 4Step 4
Convert patterns into understandable, valid, and potentially useful knowledge for the domain objective.
- 5Step 5
Deliver results as interpreted knowledge—often described as useful information—to support decisions/insights.
Connecting the multiple-choice options to KDD stages
The following mapping shows why the output is best described as useful information:
| Option | Best KDD stage association | Why it’s not the final KDD output (or is) |
|---|---|---|
| (i) data | Input / intermediate datasets | KDD consumes and transforms data; it is not defined as producing “data” as the final output.2 |
| (ii) information | Interpretation/evaluation | “Information” may appear as an informal synonym, but the formal KDD framing emphasizes interpreted knowledge that is potentially useful.2 |
| (iii) query | Selection/filtering (possible) | Queries are primarily database operations; KDD’s output is patterns/knowledge, not a query.2 |
| (iv) useful information | Final interpreted knowledge | KDD explicitly targets potentially useful, understandable knowledge—i.e., useful information delivered to the application.3 |
Footnotes
-
Fayyad, Piatetsky-Shapiro, Smyth (KDD): From data mining to knowledge discovery in databases - Foundational framing of KDD steps and the goal of extracting useful knowledge from data. ↩ ↩2 ↩3
-
SQL (Structured Query Language) — Wikipedia - Explains SQL as a querying language used to retrieve/filter data, contrasting with KDD’s discovery/knowledge goals. ↩ ↩2
-
Knowledge discovery in databases — Wikipedia - Describes KDD as the overall process to extract knowledge from data; emphasizes knowledge discovery framing. ↩ ↩2
-
Information retrieval — Wikipedia - Defines retrieval as finding relevant information via queries, helping distinguish it from KDD’s knowledge discovery output. ↩
-
Data mining vs. knowledge discovery in databases — Wikipedia (KDD context) - Discusses data mining as part of KDD and the need for interpretation/evaluation for useful outcomes. ↩
Exam-friendly phrasing
When asked about KDD’s output, choose the option closest to “interpreted, potentially useful knowledge/information.” That corresponds to (iv) useful information in typical KDD MCQs.3.
Footnotes
-
Knowledge discovery in databases — Wikipedia - Describes KDD as the overall process to extract knowledge from data; emphasizes knowledge discovery framing. ↩
-
Fayyad, Piatetsky-Shapiro, Smyth (KDD): From data mining to knowledge discovery in databases - Foundational framing of KDD steps and the goal of extracting useful knowledge from data. ↩
-
Data mining vs. knowledge discovery in databases — Wikipedia (KDD context) - Discusses data mining as part of KDD and the need for interpretation/evaluation for useful outcomes. ↩
Common confusion: data mining vs KDD
Data mining is a sub-step of KDD focused on pattern extraction. KDD also includes preprocessing and—critically—interpretation/evaluation to ensure the result is meaningful and useful. So “useful information” reflects the full KDD lifecycle, not only mining.3.
Footnotes
-
Knowledge discovery in databases — Wikipedia - Describes KDD as the overall process to extract knowledge from data; emphasizes knowledge discovery framing. ↩
-
Fayyad, Piatetsky-Shapiro, Smyth (KDD): From data mining to knowledge discovery in databases - Foundational framing of KDD steps and the goal of extracting useful knowledge from data. ↩
-
Data mining vs. knowledge discovery in databases — Wikipedia (KDD context) - Discusses data mining as part of KDD and the need for interpretation/evaluation for useful outcomes. ↩
KDD lifecycle (where the output emerges)
Goal framing
1. Task & data selectionSet the discovery objective and select relevant data."
Cleaning & transformation
2. PreparationProduce datasets suitable for mining."
Pattern extraction
3. MiningGenerate candidate patterns/models from data."
Evaluate & translate to knowledge
4. InterpretationTurn patterns into potentially useful, understandable knowledge (output)."
FAQ: What exactly is KDD “output”?
How KDD outputs align with the answer options
Qualitative alignment of each option with the final deliverable of KDD.
KDD Output Quick Check
Knowledge Check
In Knowledge Discovery in Databases (KDD), which option best describes the output?