-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #44 from WSE-research/threeshot_input_generative
Added three-shot (input) and zero-shot (output) generative support
- Loading branch information
Showing
6 changed files
with
53 additions
and
5 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,33 @@ | ||
Given the following context: Here, we consider the data of a Question Answering system. The data describes a SPARQL query. As a user I'd like to understand what the query means and does. For this purpose a (text-based) explanation has to be computed. | ||
Here's an example explanation: | ||
The query: | ||
``` | ||
"${ZEROSHOT_QUERY}" | ||
``` | ||
The example explanation: | ||
"${ZEROSHOT_EXPLANATION}" | ||
|
||
Another example is the following: | ||
The query: | ||
``` | ||
${ONESHOT_QUERY} | ||
``` | ||
The 2nd example explanation: | ||
"${ONESHOT_EXPLANATION}" | ||
|
||
And lastly an 3rd example: | ||
The query | ||
``` | ||
"${TWOSHOT_QUERY}" | ||
``` | ||
The 3rd explanation: | ||
``` | ||
"${TWOSHOT_EXPLANATION}" | ||
``` | ||
|
||
Now explain the following query, used by the component "${COMPONENT}": | ||
``` | ||
${QUERY} | ||
``` | ||
|
||
Don't use more than 3 sentences. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
Given the following context: | ||
Here, we consider the data of a Question Answering system. | ||
The data describes the outcome of this system. | ||
As a user I'd like to understand what happened inside that particular component. | ||
For this purpose a (text-based) explanation has to be computed. | ||
|
||
Given is the following data: | ||
<TASK_RDF_DATA_TEST> | ||
|
||
Now, create an explanation for this data. | ||
|
||
Don't introduce your answer and only return the result. |