Functionality learning through specification instructions

Pedro Henrique Luz de Araujo, Benjamin Roth
11/14/2023
cs.CL

No confident code implementation found for this paper.

Abstract

Test suites assess natural language processing models' performance on specific functionalities: cases of interest involving model robustness, fairness, or particular linguistic capabilities. This paper introduces specification instructions: text descriptions specifying fine-grained task-specific behaviors. For each functionality in a suite, we generate an instruction that describes it. We combine the specification instructions to create specification-augmented prompts, which we feed to language models pre-trained on natural instruction data. We conduct experiments to measure how optimizing for some functionalities may negatively impact functionalities that are not covered by the specification set. Our analyses across four tasks and models of diverse sizes and families show that smaller models struggle to follow specification instructions. However, larger models (>~3B params.) can benefit from specifications and -- surprisingly -- even generalize certain desirable behaviors across functionalities.

View on arXivView PDF

Code Implementations

No confident code match yet

We couldn't find an author-owned or strongly-evidenced community implementation for this paper. Any repos shown below are weak matches — verify before relying on them.

No code implementations found yet.

Know of an implementation? Let us know in the comments below!

Similar Papers

Cite this paper

@article{araujo2023functionality,
  title  = {Functionality learning through specification instructions},
  author = {Pedro Henrique Luz de Araujo and Benjamin Roth},
  year   = {2023},
  eprint = {2311.08481},
  archivePrefix = {arXiv},
  url    = {http://arxiv.org/abs/2311.08481v2}
}

Add a badge to your README

Shows whether official code is linked for this paper.

Code of Paper badge
[![Code of Paper](https://codeofpaper.com/badge/2311.08481.svg)](https://codeofpaper.com/paper/2311.08481)

Discussion