Dependency parse tree visualization

#1

Post by altro » Thu, Aug 20, 2015, 7:58 AM UTC

Dependency parse tree visualization
spacy.io

Re: Dependency parse tree visualization

#2

Post by bshimmin » Thu, Aug 20, 2015, 9:07 AM UTC

Interesting and quite neat! I tried this with the famous openings of two famous novels, "Pride and Prejudice" and "Ulysses"; it did well with the former but struggled a bit with the latter. I guess that's probably par for the course for most humans with those two texts, though.

Re: Dependency parse tree visualization

#3

Post by [deleted] » Thu, Aug 20, 2015, 10:25 AM UTC

[deleted]

Re: Dependency parse tree visualization

#4

Post by nxb » Thu, Aug 20, 2015, 10:48 AM UTC

Nice, and has a built-in parser and annotation system too. Very nice.

Any others like this?

Re: Dependency parse tree visualization

#5

Post by syllogism » Thu, Aug 20, 2015, 10:52 AM UTC

Please report any performance problems. I have this running on a pretty modest server, but it should be no trouble to throw up an EC2 instance if the traffic gets too much.

I did some simple stress testing that said it should handle a couple of hundred concurrent users, but I didn't put the time in to get a very realistic simulation. I worry it was too optimistic.

Re: Dependency parse tree visualization

#6

Post by maze-le » Thu, Aug 20, 2015, 10:57 AM UTC

bshimmin wrote: post #2

Interesting and quite neat! I tried this with the famous openings of two famous novels, "Pride and Prejudice" and "Ulysses"; it did well with the former but struggled a bit with the latter. I guess that's probably par for the course for most humans with those two texts, though.

I think it depends on the level of complexity, and common structure of the sentences. If a writer uses a bit more prosaic language it will fail.

I tried the famous opening from the "Commentarii de Bello Gallico".

"All Gaul is divided into three parts, one of which the Belgae inhabit, the Aquitani another, those who in their own language are called Celts, the third."

It failed to parse the tree in a correct way. On the other hand, it did quite well with simple sentences (randomly picked from wikipedia).

PS: I had also a hard time to understand Ulysses.

Re: Dependency parse tree visualization

#7

Post by LoSboccacc » Thu, Aug 20, 2015, 11:04 AM UTC

Super interesting!

I'm feeding it Shakespeare, just for fun, however I'm having trouble understanding the meaning of having two CCMP in the context of the verb make in this

"Our doubts are traitors, and make us lose the good we oft might win, by fearing to attempt"[1]

[1] http://spacy.io/displacy/?full=Our%20doubts%20are%20traitors...

Re: Dependency parse tree visualization

#8

Post by LoSboccacc » Thu, Aug 20, 2015, 11:07 AM UTC

maze-le wrote: post #6

bshimmin wrote: post #2

Interesting and quite neat! I tried this with the famous openings of two famous novels, "Pride and Prejudice" and "Ulysses"; it did well with the former but struggled a bit with the latter. I guess that's probably par for the course for most humans with those two texts, though.

I think it depends on the level of complexity, and common structure of the sentences. If a writer uses a bit more prosaic language it will fail. I tried the famous opening from the "Commentarii de Bello Gallico". "All Gaul is divided into three parts, one of which the Belgae inhabit, the Aquitani another, those who in their own language are called Celts, the third." It failed to parse the tree in a correct way. On th…

Imagine if we could have a visualization of subject/verb/object and their relationships clearly outlined on hover on each forum of the internet!

It is not as curing cancer but as close as solving war as it gets

Re: Dependency parse tree visualization

#9

Post by grandpa » Thu, Aug 20, 2015, 11:12 AM UTC

It parses "fruit flies like a banana" the same way as "Time flies like an arrow".

https://en.wikipedia.org/wiki/Time_flies_like_an_arrow;_frui...

Re: Dependency parse tree visualization

#10

Post by syllogism » Thu, Aug 20, 2015, 11:23 AM UTC

maze-le wrote: post #6

bshimmin wrote: post #2

Interesting and quite neat! I tried this with the famous openings of two famous novels, "Pride and Prejudice" and "Ulysses"; it did well with the former but struggled a bit with the latter. I guess that's probably par for the course for most humans with those two texts, though.

I think it depends on the level of complexity, and common structure of the sentences. If a writer uses a bit more prosaic language it will fail. I tried the famous opening from the "Commentarii de Bello Gallico". "All Gaul is divided into three parts, one of which the Belgae inhabit, the Aquitani another, those who in their own language are called Celts, the third." It failed to parse the tree in a correct way. On th…

Interesting example. The Latin is much easier to parse than the English "translation" for this sentence. Actually I often tell people that a classics class is probably a better introduction for parsing than most linguistics 101 classes I've seen, which are usually a little bit airy.

Theory is definitely good, but it can't replace stepping through a lot of examples. Classics is probably the best place to get that.

Anyway. The Latin is probably easier to parse than the English "translation", since the translation here is hardly natural. I'd suggest that Classics translation have a particular tradition of being faithful to the syntax of the original.

Compare the parses for the original:

http://spacy.io/displacy/?full=All%20Gaul%20is%20divided%20i...

And what I would say is a more English-like version:

http://spacy.io/displacy/?full=Gaul%20is%20divided%20into%20...

The English-like version is still wrong, and I'm interested to dig through what's gone wrong with it. But it's a much better parse than the tool was capable of producing for the Latinglish original.