Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Launch HN: Parsewise (YC P25) – Reason Across Documents with an API

news.ycombinator.com

Post reply on HN
Print view View original

31–40 of 59 posts

Re: Launch HN: Parsewise (YC P25) – Reason Across Documents with an API

#31

Post by gergelycsegzi »

vinaigrette wrote: post #27
gergelycsegzi wrote: post #24

Earlier quoted context omitted.

Fully agree, that's why we quite like the Databricks OfficeQA benchmark.. it made us experts on historical US treasuries haha Some screenshots in here: https://www.parsewise.ai/officeqa-sota

I'm surprised at the low rate every model manages considering the (apparent) ease of the benchmarked document. Can your pipeline produce ground truth as a byproduct ? How do you think open-weight ocr models compare to the one showcased ? I've had good results with glm-ocr on complex documents (complex by their handwriting, pretty easy layouts). What I like about your solution is the traceability of the information. A…

We were also surprised at first. The reason the models don't do so well is that they need to find information across 90k pages. When they are pointed to the right location they tend to do much better. And with these treasury documents grepping / keyword searching is almost impossible because everything appears thousands of times.

And thank you, we also love the traceability, it's one of the aspects that we have prioritized. Models will never be perfect so rather than building the best model harness we went for the best human harness haha.

Tbh it's been a while since I've looked at notebooklm so I expect it would have gotten better over time. One thing where I found it lacking in the past was the structure we could get out (which gives the traceability) - for example a deep dive on one the underlying data for this corpus: https://demo.parsewise.ai/projects/39bee9d8-d722-4b23-8894-e...

And yes, we're really excited whenever new open weights models come out that push quality, price, latency. We're finding that throughput is a big obstacle so I'm looking forward to more of this running locally, but it will be a while..

Re: Launch HN: Parsewise (YC P25) – Reason Across Documents with an API

#32

Post by gergelycsegzi »

capevace wrote: post #29

I built a similar tool some time ago called Struktur ( https://struktur.sh ). It’s much more limited in scope but fully open source and highly customisable. In fact it’s made for people to build their own pipelines on top of, providing the scaffolding needed to do so in a reliable way. During development I’ve found it to be hard to truly generalise agent/llm-based data extraction, especially around the unlimited numb…

I'll need to check it out!

We had the same observation in that the possible space is almost endless, and for example even for the same file type there may be different kind of processing required (e.g. an excel can be database style, vs small narrative heavy, or both).

We have baked in some ground processing rules for different kinds of documents, and we do allow custom instructions on how to deal with specific cases (e.g. translations, particular format layouts). The best write-up I have at the moment is https://www.parsewise.ai/doc-processing-pipelines but we're working on something that goes into more detail:)

Re: Launch HN: Parsewise (YC P25) – Reason Across Documents with an API

#33

Post by gergelycsegzi »

whinvik wrote: post #30

Document parsing is top of my mind lately because in some of the areas we work on the bottleneck is starting to become being able to query documents the same way one queries an api. I keep thinking the most obvious analogue is we need some way to represent documents the same way we can represent structured data in parquet. Parquet allows easy range bases queries and there is so much tooling built around Arrow. But fo…

100% the really hard challenge is that the intermediate representation (ie the parquet equivalent) will be dependent on the given use case. So what we do with the platform is have the users configure the intermediate layer that serves most of their queries, and if they need to extend it we will suggest it for them. For example for the demo on the grounded reasoning benchmark I referred to, here is what the intermediate layer looks like on top of which the agents can more efficiently query: https://demo.parsewise.ai/projects/39bee9d8-d722-4b23-8894-e...

Re: Launch HN: Parsewise (YC P25) – Reason Across Documents with an API

#36

Post by gnerd00 »

dang wrote: post #19
gnerd00 wrote: post #4

[flagged]

A launch post is not a place to attack other users personally. Neither is any other HN thread for that matter, so please don't do it here. https://news.ycombinator.com/newsguidelines.html

I do respect your moderation, however I addressed the statement, the choice of words, not the person.

Re: Launch HN: Parsewise (YC P25) – Reason Across Documents with an API

#37

Post by gergelycsegzi »

vmandrade wrote: post #35

Interesting product! Do you think it would work for e-discovery? I have around 120GB of emails, contracts, and the like, and I need to search for data and where certain expressions are referenced.

Potentially, but at that scale cost and latency may actually become an issue, so probably better to consider some sort of indexing or keyword searching.

Re: Launch HN: Parsewise (YC P25) – Reason Across Documents with an API

#39

Post by gergelycsegzi »

rogerthis wrote: post #38

I am seeing my client using things like this heavily (not exactly this). Also, what I would call "business awareness" is declining.

I can see why, it's tempting to go for full automation. The reason we go for fine grained sourcing is so that people can build their awareness quickly. Plus many of our customers work in regulated industries where full automation is prohibited.
Post reply on HN