Closed pingpingy1 closed 10 months ago
Required computational tasks:
Parsing, localization, replacement searching would be done with Prolog, while choosing a single replacement and interfacing with user would probably be done with Python.
Miro link Here's a basic data flow diagram of the project. Given one, grammatically incorrect reading of the joke, its syntax tree is passed through the modules explained above to determine whether the sentence has a humorous homophone reading. The English, phonetic, and contextual KBs are designed to be separated from this process, so as to be as modular as possible.
Is your feature request related to a problem? Please describe. I should decide on the following things:
Describe the solution you'd like The resulting architecture must be modular, concise, and generalizable. For example, transitions from hard-coded phonetic similarity to IPA to vector DB should be smooth. Each module should have a well-defined, simple task that have little overlap. By looking at the architecture, the prototype should seem within reach. This should also lead to some loose (preferably tight) definition of the scope of functionalities.
Describe alternatives you've considered A totally-Python or totally-Prolog is impractical since a friendly interface as well as logical inferences are required. It may be beneficial to use some diagram-drawing software for this task. eg) Miro
Additional context