Fixing Tool-Call Accuracy in vLLM

(ubicloud.com)

44 points | by coffeemug 1 hour ago

6 comments

  • jesdo 1 hour ago
    I'm one of the authors of this blog post. Figuring out how to integrate the LLM, the inference and serving engine, and the constrained decoding implementation such that you get the intended output and overall quality definitely requires careful engineering and testing. Please feel free to AMA. :)
    • ivanjermakov 33 minutes ago
      Do you know where <||> syntax is coming from? I find it very odd that existing markup wasn't used and there is very little info online about it.
      • jesdo 20 minutes ago
        To the LLM, the <|...|> tags are single, special tokens. They are rendered as <|...|> tags for readability, but to the model the tags are single tokens.

        I do not know why these tokens are visualized as <|...|>, but I speculate that this way they are easily recognizable as special-purpose tokens, and difficult to confuse with other types of existing markup.

      • t_mahmood 26 minutes ago
        Correct me if I wrong, I saw this when llama.cpp or ollama initializes, it is used as token separator of some sort.
        • cowlevel 22 minutes ago
          GPT-2 used <|endoftext|>
  • sroussey 10 minutes ago
    Constrained decoding came to JS land transformers last month for in browser structured output as well, also used for tool calling.

    https://github.com/huggingface/transformers.js/blob/main/pac...

  • sarmedshafi 27 minutes ago
    [flagged]
  • arbor-group 33 minutes ago
    [flagged]
  • michaelpo 29 minutes ago
    [dead]
  • fr2029r 11 minutes ago
    [dead]