You could just make your original topic post a wiki, but I think it might make more sense for you to start a new topic and organize it with some structure and bring all of these papers together more concisely.
I’d also include them as simple links rather than as “onebox” links.
I’d then also add a second post to the wiki outlining the “rules” for editing the wiki in terms of structure and how you want people to add additional papers for inclusion or consideration (maybe have an “Uncategorized” category for people to just drop links to papers, etc.
One thing I think would be nice is a format like this for each paper:
Paper Title (as link to source)
Published date
List of authors as links to their pages
Summary
Summary written by ChatGPT
Code
Links to any online repos which have implemented aspects of the paper
This topic was originally created as a spinoff from conversations between @qrdl, @bruce.dambrosio
and myself, and because the “sharing papers” pm between me and @bruce.dambrosio was reaching +100 posts.
I think it’s a good idea to turn this into a wiki section after a bit of “off-topic” cleanup.
I’ve recently been reading about toxic language detection & moderation using AI, and I found these papers particularly interesting due to their different approaches to the generation of training datasets.
In this study they introduce a modified BERT model specifically designed for detecting abusive language in English using data from banned Reddit communities. Not only does HateBERT surpass general BERT models in identifying hate speech, but the research also delves into how training data influences the adaptability of such models across various datasets.
The next paper tries to address the issue of toxic language detection systems inaccurately flagging mentions of minority groups.
This study introduces “ToxiGen”, a large dataset produced with GPT-3, that generates both subtle toxic and benign statements; initial tests showed that refining toxicity classifiers with ToxiGen significantly enhances their accuracy on human-written content.
Probably not ‘Foundational’, but the idea of using multiple embeddings of a prompt, then sending the retrieval results from each as part of a separate gpt query, then ensembling the gpt query results, is certainly an idea I hadn’t thought of.
Only relevant for multiple-choice type queries, or maybe feed all results back again to llm for final compilation?
Some stuff I run across isn’t necessarily ‘foundational’ and the depth isn’t always that extensive (at least math wise), but it talks about an idea that I’m interested in which perhaps doesn’t lend itself to formal exploration - when few other papers will. Probably because it’s hard to measure precisely and conclude concretely.
This is one example:
It’s particularly relevant I think because of GPT-4s visual capabilities, where you can generate code from UML modeling.
The biggest takeway I got from this was how it used object constraint language / OCL to enhance GPT4’s code generation capability. When I go to experiment with it, I’ll need to read that more carefully to see what skimming missed.
They used plantuml (text based uml), so some of that isn’t useful given image support but it is interesting. Maybe converting uml diagrams to plantuml first might work better than straight to code, especially if the diagrams are extensive and disparate.