Interactive Acquisition of Justifications: Learning "Why" by Being Told "What."
From Tetherless World Wiki
Citation: Thomas R. Gruber. (1991) Interactive Acquisition of Justifications: Learning "Why" by Being Told "What.". In KSL-91-17, August,1991.
| Publication techreport ( Edit ) | |
| type | Technical Report |
| bibtype | techreport |
| Bibtex basics | |
| author | Thomas R. Gruber |
| title | Interactive Acquisition of Justifications: Learning "Why" by Being Told "What." |
| number | KSL-91-17 |
| institution | Knowledge Systems, AI Laboratory |
| year | 1991 |
| month | August |
| Bibtex more | |
| Access Paper | |
| abstract | In this paper I describe an approach to automated knowledge acquisition in which users specify desired system behavior by constructing justifications of examples. Justifications are explanations of why example behaviors are appropriate in given situations. I analyze the problem of acquiring justifications, showing how current knowledge acquisition techniques are best suited for asking what-questions, while justifications are naturally viewed as answers to why-questions. I sketch a new approach for acquiring justifications that transforms why-questions into what-questions, borrowing the sources of power of existing techniques. In this approach, users construct justifications by selecting facts that specify what is relevant in a situation from a space of facts provided by the elicitation tool.Justifications are then used to create operational mappings from situations to intended outcomes. I show how the approach is applied to two different knowledge acquisition problems: the acquisition of diagnostic strategy and the acquisition of design rationale. I conclude by identifying common characteristics of the two applications and discuss how their design distributes the cognitive load between human and machines. |
| KSL Technical Report ID: KSL-91-17 |
Facts about Interactive Acquisition of Justifications: Learning "Why" by Being Told "What."RDF feed
| Abstract | In this paper I describe an approach to au … In this paper I describe an approach to automated knowledge acquisition in which users specify desired system behavior by constructing justifications of examples. Justifications are explanations of why example behaviors are appropriate in given situations. I analyze the problem of acquiring justifications, showing how current knowledge acquisition techniques are best suited for asking what-questions, while justifications are naturally viewed as answers to why-questions. I sketch a new approach for acquiring justifications that transforms why-questions into what-questions, borrowing the sources of power of existing techniques. In this approach, users construct justifications by selecting facts that specify what is relevant in a situation from a space of facts provided by the elicitation tool.Justifications are then used to create operational mappings from situations to intended outcomes. I show how the approach is applied to two different knowledge acquisition problems: the acquisition of diagnostic strategy and the acquisition of design rationale. I conclude by identifying common characteristics of the two applications and discuss how their design distributes the cognitive load between human and machines. cognitive load between human and machines. |
| Author | Thomas R. Gruber + |
| Bibtype | techreport + |
| Has author | Thomas R. Gruber + |
| Has identifier | KSL-91-17 + |
| Has publishing details | August,1991 + |
| Has title | Interactive Acquisition of Justifications: Learning "Why" by Being Told "What." + |
| Has where published | KSL-91-17 + |
| Has year | 1991 + |
| Institution | Knowledge Systems, AI Laboratory + |
| Ksl tr id | KSL-91-17 + |
| Month | August + |
| Number | KSL-91-17 + |
| Process note | YES + |
| Title | Interactive Acquisition of Justifications: Learning "Why" by Being Told "What." + |
| Year | 1991 + |
Resource > Thing > Entity > Document > Scientific Document > Publication
Resource > Thing > Entity > Document > Scientific Document > Publication > Technical Report
Resource > Thing > Entity > Document > Scientific Document > Publication > Technical Report > KSL Technical Report
