1. Automating Discovery from Biomedical Texts Marti Hearst & Barbara Rosario UC Berkeley Agyinc Visit August 16, 2000

2. The LINDI Project Linking Information for New Discoveries UIs for building and reusing hypothesis seeking strategies. Statistical language analysis techniques for extracting propositions Two Main Thrusts:

3. Scenario: Explore Functions of a Gene l Objective –Determine the functions of a newly sequenced Gene X. l Known facts –Gene X co-expresses (activated in the same cell) with Gene A, B, C –The relationship of Gene A, B, C with certain types of diseases (from medical literature) l Question –What types of diseases are Gene X related to?

4. Gene Co-expression: Role in the genetic pathway g? PSA Kall. PAP h? PSA Kall. PAP g? Other possibilities as well

5. Make use of the literature l Look up what is known about the other genes. l Different articles in different collections l Look for commonalities –Similar topics indicated by Subject Descriptors –Similar words in titles and abstracts adenocarcinoma, neoplasm, prostate, prostatic neoplasms, tumor markers, antibodies...

6. Developing Strategies l Different strategies seem needed for different situations –First: see what is known about Kallikrein. –7341 documents. Too many –AND the result with “disease” category »If result is non-empty, this might be an interesting gene –Now get 803 documents

7. Medical Literature Explore Functions of New Gene X Gene-A Keywords Slide adapted from K. Patel Projection Mapping Query

8. Developing Strategies l Different strategies seem needed for different situations –First: see what is known about Kallikrein. –7341 documents. Too many –AND the result with “disease” category »If result is non-empty, this might be an interesting gene –Now get 803 documents –AND the result with PSA »Get 11 documents. Better!

9. Medical Literature Explore Functions of New Gene X Gene-A Keywords Gene-B Gene-C Keywords Projection Keywords Intersection Query

10. Developing Strategies l Look for commalities among these documents –Manual scan through ~100 category labels –Would have been better if »Automatically organized »Intersections of “important” categories scanned for first

11. Medical Literature Explore Functions of New Gene X Gene-A Keywords Gene-B Keywords Slide adapted from K. Patel Slicing Gene-C Keywords Projection Keywords Intersection Mapping Query

12. Try a new tack l Researcher uses knowledge of field to realize these are related to prostate cancer and diagnostic tests l New tack: intersect search on all three known genes –Hope they all talk about diagnostics and prostate cancer –Fortunately, 7 documents returned –Bingo! A relation to regulation of this cancer

13. Medical Literature Explore Functions of New Gene X Possible Function For Gene-X Gene-A Keywords Gene-B Keywords Slide adapted from K. Patel Slicing Gene-C Keywords Projection Keywords Intersection Mapping Query

14. Formulate a Hypothesis l Hypothesis: mystery gene has to do with regulation of expression of genes leading to prostate cancer l New tack: do some lab tests –See if mystery gene is similar in molecular structure to the others –If so, it might do some of the same things they do

15. Strategies again l In hindsight, combining all three genes was a good strategy. –Store this for later l Might not have worked –Need a suite of strategies –Build them up via experience and a good UI

16. The System l Doing the same query with slightly different values each time is time- consuming and tedious l Same goes for cutting and pasting results –IR systems don’t support varying queries like this very well. –Each situation is a bit different l Some automatic processing is needed in the background to eliminate/suggest hypotheses

17. The User Interface l A general search interface should support –History –Context –Comparison –Operators: Intersection, Union, Slicing –Operator Reuse –Visualization (where appropriate) l We have an initial implementation l It needs lots of work

18. Architecture of LINDI UI l Data Layer l Annotation Layer l User Interface Layer

19. Data Layer l Purpose –Hide different formats of text collections l Components –Data: Abstractions representing records of a text collection –Operations: performed on the data l Data –A set of records –Each record is a set of tuples with types l Operations –union, intersection, projection, mapping

20. Annotation Layer l Purpose –Associate data set with operations that produced them (history) –History is a first class object l Advantage –Streamline a sequence of operations –Reuse operations –Parameterize operations

21. User Interface l Direct manipulation of information objects and access operations –Query –Intersection –Union –Mapping –Slicing l Record and reuse of past operations l Parameterization of operations l Streamlining of operations

22. Initial Palette

23. Query Structure Determined by Collection Type

24. Query Operation Results

25. Projection Operation and Subsequent Results

26. Parameterized Query: Repeat operations with different values GC GB GA

27. Intersection over Projected Attribute

29. Example Interaction with UI Prototype 1 Query on Gene names 2 Project out only mesh headings 3 Intersect the results 4 Map to create a ranking 5 Slice out the top-ranked.

30. Future Work on UI l As currently designed –Better labeling –Better layout »Intuitive »Scalable –Connection to real backend –User Testing »Does direct manipulation work? »What operator sequences help? »How to improve parameterization? l More advanced –Support for strategies –Incorporation of NLP

31. Language Analysis Component Goals: –Extract Propositions from Text –Make Inferences

32. Language Analysis Component Why Extract Propositions from Text? –Text is how knowledge at the propositional level is communicated –Text is continually being created and updated by the outside world

33. Example: Statistical Semantic Grammar To detect causal relationships between medical concepts –Title: Magnesium deficiency implicated in increased stress levels. –Interpretation: related-to –Inference: »Increase(stress, decrease(mg))

34. Statistical Semantic Grammars l Empirical NLP has made great strides –But mainly applied to syntactic structure l Semantic grammars are powerful, but –Brittle –Time-consuming to construct l Idea: –Use what we now know about statistical NLP to build up a probabilistic grammar

35. LINDI: Target Components 1. Special UI for retrieving appropriate docs 2. Language analysis on docs to detect causal relationships between concepts 3. Probabilistic representation of concepts and relationships 4. UI + User: Hypothesis creation