You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 14, 2020. It is now read-only.
TUPA often predicts a node with A (participant) children but no P/S (process/state). There are several ways to tackle this problem:
Add constraints on Reduce to force creating this relation. Might make the parser get to dead ends with no possible action, though, or resort to taking unreasonable decisions. Beam search might remedy this (Implement beam search #10).
Attach the missing relations in post-processing.
The text was updated successfully, but these errors were encountered:
As simpler captions show, sometimes it is actually necessary to have a relation-less scene ("A man on a beach"), unless we want to obligatorily have P/S. The latter is a valid strategy, IMO, but it will entail creating implicit P/S nodes, which are not used at the moment.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
TUPA often predicts a node with
A
(participant) children but noP
/S
(process/state). There are several ways to tackle this problem:Reduce
to force creating this relation. Might make the parser get to dead ends with no possible action, though, or resort to taking unreasonable decisions. Beam search might remedy this (Implement beam search #10).The text was updated successfully, but these errors were encountered: