-
Notifications
You must be signed in to change notification settings - Fork 57
Raw input column #390
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Raw input column #390
Conversation
| - QA: `Q: <question>\nA:` | ||
| - Multiple choice: `Q: <question>\nA. <choice0>\nB. <choice1>\n...\nA:` | ||
| - Translation: `Original:\n<source>\nTranslation:` | ||
| - Summarization: `Original:\n<source>\nSummary:` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we keep this structure? It seems that all methods using stripped_input expect raw input, without prefixes like Original:, Q:, etc
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure if it's best to mark parts of the task (input/output) for the NLI task. I guess for summarization it makes sense to mark output as a summary, since otherwise it could just be thought of as another sentence from the text. I'll check how it works with and without these markers and report back
| x.append(prompt.format(text=q) if len(prompt) else q) | ||
| y.append("") | ||
| return x, y | ||
| s.append(qa_stripped(q)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I’m not sure QA is the best format for this dataset
stripped_inputcolumn to most of the datasets