Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I'm having success with simple YAML schema. One thing that's very helpful for the prompt is to include "description" and "example":

      -
         column name: salary_max
         format: number
         example: 150,000
         description: Salary Maximum
      -
         column name: keywords
         format: string
         example: engineer, python, docker, remote
         description: Relevant Keywords (Comma separated keywords used for filtering and matching jobs to candidates)


Nice! Another reason to prefer YAML is token count — YAML is 3x cheaper than JSON: https://twitter.com/v1aaad/status/1643889605538635782


Good suggestion mmaia - I'm opening a new issue to keep track of the different output schemas that are being suggested. One thing that originally worried me a bit with yaml was its relative reliance on space-based formatting to drive meaning. GPT generally tokenizes newlines/spaces but a lot of preprepared datasets strip these out, so I preferred the explicitness of a json that's idempotent to spaces. Have you tried using this approach for non-tabular or nested data like lists or dictionaries?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: