Applied Language Understanding (@AppliedLanguage) header
Applied Language Understanding (@AppliedLanguage) profile picture

Making AI work for your Confluence knowledge base

New York, USA
Joined January 2013
Photo by Applied Language Understanding (@AppliedLanguage)Photo by Applied Language Understanding (@AppliedLanguage)Photo by Applied Language Understanding (@AppliedLanguage)Photo by Applied Language Understanding (@AppliedLanguage)Photo by Applied Language Understanding (@AppliedLanguage)Photo by Applied Language Understanding (@AppliedLanguage)
Replying to @thsottiaux
Human in the loop (prefer bursts, frustrated by 5h limits when in the zone) vs autonomous agents (and token resellers perhaps).
91
I should have used the word consistency instead of reproducibility. E,g, different models may require adjustments to prompts/skills to perform their best. Better overall may be worse in particular scenarios. Losing the model one has invested in may require painful adaptation.
12
Replying to @antirez
This makes difficult using DS in scenarios where reproducibility is important: agents doing e.g. automated checks. Since you decide what better is, users will need to periodically retest their workflows or be left behind. Not bad, just limits use cases which is a fair UX choice.
1
31
More precisely, it implements an efficient LLM token selector driven by a JSON schema, with application examples on MLX. This is better that GNBF in that mapping to GNBF can produce unwieldy rule sets for things like min and max number of items in an array . @awnihannun @simonw
1
42
✅ Against GPT-3.5-Turbo, we saw a 17% reduction in hallucination and similarly improved recall, at a 10x cost and 2x latency. blog.alu.ai/evaluating-gpt-4…
61
We evaluated GPT-4-Turbo in our pipeline and found it a very useful addition to the palette of LLMs available, although not a complete game-changer. ✅ Against GPT-4, we saw 66% reduction in latency and cost with an estimated 5% decrease in quality (F1 score). (1/2)
1
163
From prompt whack-a-mole to fine tuning. We've learned a couple of lessons fine-tuning GPT-3.5.
1
1
136
Of course, to write the story for the submission, we enlisted AI help. blog.alu.ai/participating-in…
27
For Atlassian’s codegeist hackathon, we sprinted on querying Confluence tables:
1
95
What’s the point of AI if you can’t rely on its output? We are building a trustworthy assistant for Confluence that tells you exactly how it got its answers. Not just sources, but every reasoning step. Read more in our blog: blog.alu.ai/introducing-x-ra…
45
Atlassian has just released the public beta of Atlassian Intelligence. We had a first look and found it still has some way to go before being trustworthy. Link to our report below.
1
67
Connie AI can now answer sophisticated questions about tabular data. We translate natural language queries to a pseudo-SQL language and execute it over your Confluence tables. Support for the new Confluence Databases coming soon.
1
172
Replying to @typesfast
Connie AI (connie.alu.ai). We’re ex-Atlassians building an AI assistant for Confluence. It’s miles ahead of Confluence search already.
32