Below is an abstract from a computer science research paper. Given this abstract, your task is to extract all unique relationships between entities of the following types:

- "USED-FOR": For instance, "Our method models user proficiency" -> ["method", "user proficiency", "USED-FOR"].
- "EVALUATE-FOR": For instance, "We evaluate our method using F1-measure" -> ["F1-measure", "method", "EVALUATE-FOR"].
- "FEATURE-OF": For instance, "prior knowledge of the model" -> ["prior knowledge", "model", "FEATURE-OF"].
- "HYPONYM-OF": For instance, "TUIT is a software library" -> ["TUIT", "software library", "HYPONYM-OF"].
- "PART-OF": For instance, "We incorporate NLU module into the system." -> ["NLU module", "system", "PART-OF"].
- "COMPARE": For instance, "Unlike the quantitative prior, the qualitative prior is often ignored" -> ["quantitative prior", "qualitative prior", "COMPARE"].
- "CONJUNCTION": For instance: "obtained from human expert or knowledge base" -> ["human expert", "knowledge base", "CONJUNCTION"].

Format your output as a json array. Each entry in the array should express a single relation, formatted as ["<Entity_A>", "<Entity_B>", "<RELATION_A_B>"]. An example output might look like:

[["neural networks", "classification", "USED-FOR"], ["neuron", "neural network", "PART-OF"]].

If no relations are found, please return an empty array [].

Abstract:

An entity-oriented approach to restricted-domain parsing is proposed. In this approach, the definitions of the structure and surface representation of domain entities are grouped together. Like semantic grammar, this allows easy exploitation of limited domain semantics. In addition, it facilitates fragmentary recognition and the use of multiple parsing strategies, and so is particularly useful for robust recognition of extra-grammatical input. Several advantages from the point of view of language definition are also noted. Representative samples from an entity-oriented language definition are presented, along with a control structure for an entity-oriented parser, some parsing strategies that use the control structure, and worked examples of parses. A parser incorporating the control structure and the parsing strategies is currently under implementation.
[["entity-oriented approach", "restricted-domain parsing", "USED-FOR"], ["control structure", "entity-oriented parser", "USED-FOR"], ["control structure", "parsing strategies", "USED-FOR"], ["this", "multiple parsing strategies", "USED-FOR"], ["multiple parsing strategies", "recognition of extra-grammatical input", "USED-FOR"], ["this", "limited domain semantics", "USED-FOR"], ["this", "fragmentary recognition", "USED-FOR"], ["control structure", "parser", "PART-OF"]]