Conversation

A demo of something I've been hacking on 👀 OSINT investigators have to parse large volume documents in their flow, looking for hidden clues and useful context. Definitely think we need more ML tools to help extract + visualize key information:

0:14

43.3K views

106

811

Karina Nguyen

@karinanguyen_

right now it's extracting key characters and their actions in the document & context, but thinking about creating timelines, relationships btw people, and possibly maps/locations.

9:21 PM · Aug 9, 2022Twitter Web App

Replying to

This was much inspired from my personal investigative projects (both legal & journalistic) — supply chain analysis, military chain of command, illegal fishing. The tool shouldn’t drive investigations, rather the story should drive the tool’s flexibility.

Karina Nguyen

@karinanguyen_

Aug 10

Balancing journalist’s explorative control of the document is a key challenge here and one way to tackle this is to make AI decisions interpretable for humans to guide the direction of their investigations. I’m skeptical of making QA / prompt-based interfaces for this reason!

Replying to

👀

Thanks, the states goals remind me a lot of the academic version of Codex!

Replying to

this is really interesting, but I believe it could be important to establish how well it works and how it fails as a priority - this will allow the investigator to apply the tool without creating blindspots. Have you done a calibration step?