Perplexity Decider v1.3: Training, eval, and use cases
71 points by gmays 4 hours ago | 13 comments
0o777 2 hours ago
This blog post acted as a rabbit hole into some interesting stuff:
replyhttps://www.perplexity.ai/hub/blog/pii-trace-detecting-perso...
https://www.perplexity.ai/hub/blog/a-local-first-agent-for-p...
jstummbillig 2 hours ago
Any ideas what decider models are actually good? There does not seem to be a strong competitive benchmark culture (as with LLMs) for whatever reason?
replywalls 2 hours ago
I've found this fairly accurate: https://huggingface.co/spaces/multimodalart/jev-decision-ind...
replystri8ted 2 hours ago
It performs well on my local benchmark, and is priced competitively. Good timing too, considering that inception Labs is discontinuing their Mercury models API, which I was previously using. It seems plausible that the bidirectional attention performs better for decision models.
replyredanddead 3 hours ago
Complete lack of creativity in the field of AI...
replyHere's new product, which is just our shitty version of this easily reproducible technology
What is this?
Same for Google and their decisions api
agentdev001 3 hours ago
You seem to be confusing market capture for novelty. This almost certainly is not intended to be taken as some greenfield thing from perplexity, same goes for google
replyjgalt212 3 hours ago
Perhaps, but if you're already inside GCP it's nice to have something easy to turn on.
replyhappyopossum 2 hours ago
> version of this easily reproducible technology
replyso you'd prefer indefinite first-mover monopolies?
k__ 3 hours ago
Does anyone really use such things for security?
replywaximabbax 2 hours ago
I highly doubt it. Even if a company does internally, its highly unlikely they will reveal it publically.
replyOne use case is live content moderation or streaming where reasoning models could be a lot slower and its hard to hardcode logic.
Here are some thoughts not facts:
On AA Decision Index.
Decider v1.3 and Decider v.1.2 seem to have same benchmarks. However, V1.3 flash beats V1.2 flash by 4 points.
I am not particulary excited about this pattern/trend of having flash versions for decision models. The whole point of Decision models was to deliver faster ouput for high volume requests at much cheaper cost than Reasoning models. Since most reasoning models can and probably do outperform decision models already in accuracy but they are a lot slower and are pricier. Reasoning Models can already return structured ouput.
So your flagship model must be fastest and most accurate.
Unless it can handle some different form of input other than just image and text, I don't see the point of having both flagship and flash version for the same model.