Add head annotation to slot, there should be only one slot in a frame can be annotated as head. Of course, we can add this to frame level, where builder can select on slot.
Enable two version of alias. normalize and etc.
Motivation
From the language point of view, we have nouns (think of entity), and then we have noun phrases (think of frame). In theory, both are used to capture concepts, but there exist a head in the noun phrase that is entity:
Cat
Yellow cat
Brown eyed yellow cat
Each one of the noun phrases are essentially just referring cat.
In particular, on Framely, if we have a entity type Cat, and we have a frame CatWithColor with
CatWithColor {
Cat: Cat // head
Color: Color // modifier
}
In such frame, there will be one and only one head, and many modifiers.
If a frame has a head annotation, then it is noun frame.
When a frame has a head annotation, the it label/alias should have two implementations: associate to type, or associate to instance. The frame F with head of entity type E, is considered to be is-A of type E. What we convert the instance of E to depends on the dialog context we are in, in particular the type compatible slots. If there are more than one, and we can not separate, we will do clarification.
Describe alternatives you've considered
Another choice is not providing generalization capabilities.
Is there an existing issue for this?
Summary
Motivation
From the language point of view, we have nouns (think of entity), and then we have noun phrases (think of frame). In theory, both are used to capture concepts, but there exist a head in the noun phrase that is entity: Cat Yellow cat Brown eyed yellow cat Each one of the noun phrases are essentially just referring cat.
In particular, on Framely, if we have a entity type Cat, and we have a frame CatWithColor with CatWithColor { Cat: Cat // head Color: Color // modifier }
In such frame, there will be one and only one head, and many modifiers.
If a frame has a head annotation, then it is noun frame. When a frame has a head annotation, the it label/alias should have two implementations: associate to type, or associate to instance. The frame F with head of entity type E, is considered to be is-A of type E. What we convert the instance of E to depends on the dialog context we are in, in particular the type compatible slots. If there are more than one, and we can not separate, we will do clarification.
Describe alternatives you've considered
Another choice is not providing generalization capabilities.
Additional context
No response