-
Notifications
You must be signed in to change notification settings - Fork 8
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
Citation numbers should be after the full stop instead of before #645
Comments
requires prompt engineering, as this is returned by the LLM |
@melissasamworth who's in charge of prompt engineering? |
@bryceerobertson afaik there is not a single person, but Matthew (@matthew1970 on Discord) has been poking around with prompt engineering. AFAIK he is not on Github |
I've submitted a PR (#148) that fixes this issue by updating the example in settings.py's QUESTION_PROMPT to show the period before the citation brackets. This should help ensure consistent citation formatting throughout responses. |
I'm not sure it's possible to cross-link between projects, but here's a try |
Update: @LeMurphant will give this a go using the following recommendation from Matthew: Most frustratingly, I can't run the code on my local machine (outdated MacOS won't support all the necessary packages), so I can't test it. As I wrote in the github pull request notes: "This was simply a matter of changing one line in stampy-chat/api/src/stampy_chat/settings.py QUESTION_PROMPT = ( QUESTION_PROMPT = ( I am unable to run this codebase on my local machine (due to dependencies issues caused by an outdated MacOS, I think), but I'm 98% confident this will work, since the reason for the unwanted behaviour was so explicit." For example: "AGI is concerning. [1, 3, 8]" (note the period placement)\n\n" to For example: "AGI is concerning. [1, 3, 8]" (note that the period is placed before the citation numbers)\n\n" or even For example: "AGI is concerning. [1, 3, 8]" (it is very important that the period is placed before the citation numbers)\n\n" I used the most terse wording I could to save on token expenditure, but I'm confident that a more explicit instruction would do the job. |
See e.g. Wikipedia.
The text was updated successfully, but these errors were encountered: