Make metadata available in NLU pipeline

[cajoek]

Note: I know that I'm using Rasa in an unusual way.

Description of Problem:

I have a website with some tools and I'm trying to educate and guide my users on how to use those tools. For that I have many interactive tutorials which in turn have many steps. During the tutorial users can ask questions to the AI tutor about what they see, where they are supposed to click, how things work, in which order to do things, why they should do that thing, and many other kinds of questions. This chat functionality is powered by Rasa. This setup means that there are very many similar but different intents and each intent may only be valid on a few pages or during a few steps. I would therefor like to pass a key in the metadata that indicates where in the tutorial the user currently is and use this key in my custom NLU component to filter out the relevant intents/responses for that part of the tutorial before predicting the correct one.

In a sense I want the contextual assistants context to also include what the user sees in the current tutorial.

Relevant topics: https://forum.rasa.com/t/pass-along-users-current-location-on-website-as-a-paramter-to-rasa/25908 https://forum.rasa.com/t/metadata-in-message-in-nlu-pipeline-component/26767

Overview of the Solution:

Metadata for each message in the conversation needs to be available in the NLU pipeline. Currently metadata is only avaiable in rasa.core.channels.UserMessage not in rasa.nlu.training_data.Message

In this post https://forum.rasa.com/t/new-training-data-format-ideas/29687 it is mentioned that "support for optional custom metadata in training examples" may come in a new update. Will this also allow for providing metadata to the NLU during inference?

Definition of Done:

• [ ] Chat metadata for all messages is available to NLU components.

[sara-tagger]

Thanks for submitting this feature request 🚀 @wochinge will get back to you about it soon! ✨

[cristianmtr]

My team is also in need of this.

Quoting my colleague, @nbeuchat :

One thing we want to do is passing some geographic context to the bot so that location entities can be properly disambiguated. For example, if a user is looking for a place in NYC, we want to be able to differentiate between “Downtown” between NY or other cities so that we get the proper ID for this location. Up until now, we’ve done this mapping in actions so it was easy to use slots for the context. The problem is that we want to extend our location parsing using a custom pipeline component which uses Spacy’s pattern matcher. But we first need our disambiguation before applying the patterns.

[wochinge]

Sorry, I was convinced to have already answered 😬

Thanks for brining up all these different use cases. Especially the one with geographic context is very valid. I think we should probably not just metadata but the whole conversation tracker (previous messages, bot actions / utterances, into the NLU pipeline).

What do you think @Ghostvv ?

[cristianmtr]

Yes, having access to the tracker and sender_id would also be very nice! We have added a mechanism for logging by sender_id to our logging system, and seeing which sender has triggered a specific error in a pipeline component would be very useful :)

[Ghostvv]

NLU pipeline should be context agnostic, it is used to classify text into abstract notions. Disambiguation should happen through rasa core. E.g. disambiguating entities can be done inside custom action or a form. Same for the problem of website, I'd recommend to merge similar intents into one, but use dialogue story that would receive different predefined external intents when user switch pages. Then different actions can be predicted even though nlu intent is the same

[cajoek]

Does the NLU pipeline have to be context agnostic? Why? The ResponseSelector is not so abstract.

[Ghostvv]

this is the separation of nlu and core. Core is responsible for context. Response selector is still context agnostic. I think if we keep it agnostic, we maintain clarity of what happening when, which makes it more scalable.

We fully integrate nlu inside core in the further update. So you could easily access nlu components inside core, and therefore condition their output on the context.

[nbeuchat]

Disambiguation should happen through rasa core. E.g. disambiguating entities can be done inside custom action or a form.

Correct me if I'm wrong but custom actions and forms are not really part of Rasa core, are they? Rasa core just predicts the next action/form/utterance to use and that's it. For the disambiguation case, that means that you need to either:

• Have a specific action doing this disambiguation and put it before any action that needs the entity to be correctly disambiguated (or linked). Then, you rely on Rasa core to predict your disambiguation action before any other action that actually needs your entity
• Do the disambiguation in every single action that wants to use this (this is what we chose to do). That also forces you to use actions instead of utterances in some cases and you cannot simply use the automatic slot filling from entities

To me, it forces us to do some simple entities processing way later in the NLU > Core > Action pipeline which makes it very unclear of what is happening when.

I think if we keep it agnostic, we maintain clarity of what happening when, which makes it more scalable.

I would agree with this statement for the conversation part (ie: it shouldn't really matter where you are in the conversation from an NLU perspective). However, I feel that entity disambiguation/linkage should be done within the NLU pipeline and some limited context can be needed (geography for entity disambiguation, user locale for date parsing, user country for phone number parsing, etc.)

[Ghostvv]

custom actions and forms are not really part of Rasa core

what do you mean? they are part of rasa core, but you need to write them using sdk

Have a specific action doing this disambiguation and put it before any action that needs the entity to be correctly disambiguated (or linked).

why can't you do it inside the action that needs to use it?

geography for entity disambiguation, user locale for date parsing, user country for phone number parsing

is it always the same inside conversation but change from conversation to conversation? Sorry, then misunderstood what do you mean by context. if it is changing inside one conversation, for example entity number can mean different things in different parts of the conversation, then I think it is better to have it in core, otherwise how do you create training data. If it is set in the beginning of the conversation and don't change throughout the conversation, then I agree predict custom action every time is a tedious process. I can envision some default action similar to action_listen, that is not predicted, but always called after the utterance and execute the custom action from sdk that is basically responsible for auto slot filling but with additional customizable logic. Would this solve your issue?

[wochinge]

@nbeuchat What do you think of the proposed solution?

[nbeuchat]

@nbeuchat What do you think of the proposed solution?

I love it! Very much waiting to have it in Rasa 2.0. I just implemented last week something that would have greatly benefited from the custom auto slot filling. It's also great combined with the new entities groups (for example, to pick or ignore a group for auto-filling a slot).

[wochinge]

Very much waiting to have it in Rasa 2.0.

Ehm, about this 🙄 🙈 It's probably rather gonna be a minor after 2.0 . We are currently focusing upon releasing a production ready Rasa Open Source 2.0 version with the features which we committed to and want to avoid further delays due to newly added features. Getting 2.0 ready, documented and smooth to use is currently our number one priority. We will return to our regular release cycle (every 4 weeks) once 2.0 is released so it shouldn't take too long 🤞 I'm sorry to keep you waiting longer.

[nbeuchat]

No worries at all 😄 In any case, we'll have some work to do to migrate to 2.0 in the first place so I wasn't expecting to have that new feature up and running directly :-) Thanks for the update!

[TyDunn]

@wochinge Can we close this after 2.0?

[wochinge]

Yes, fixed by https://github.com/RasaHQ/rasa/pull/6275

[dingusagar]

the default interpreter in Agent is RasaNLUInterpreter. But RasaNLUInterpreter does't have this feature of passing on the metadata in its parse method.

[goxiaoy]

Why this issue is closed?

The current meta is not passed from core to nlu

https://github.com/RasaHQ/rasa/blob/2039cef57780f034da22efcf8c1534d12f3d0ac3/rasa/core/interpreter.py#L131-L147

The current interpreter of nlu can not accept metadata

https://github.com/RasaHQ/rasa/blob/2039cef57780f034da22efcf8c1534d12f3d0ac3/rasa/nlu/model.py#L444-L449

Ref active question from forum

https://forum.rasa.com/t/passing-metadata-to-custom-components-nlu/45198 https://forum.rasa.com/t/metadata-in-message-in-nlu-pipeline-component/26767/9

[indam23]

The changes in the linked PR don't send metadata all the way down to the method in which it is needed for NLU components to access it. Here in processer.parse_message metadata is available: https://github.com/RasaHQ/rasa/blob/7c8aa9fc44475b8716e4b8cd444a1d7d1ca7506d/rasa/core/processor.py#L572-L574 But here in RasaNLUInterpreter.parse which it calls, only the text of the message actually gets passed on: https://github.com/RasaHQ/rasa/blob/7c8aa9fc44475b8716e4b8cd444a1d7d1ca7506d/rasa/core/interpreter.py#L145 (also true of RasaNLUHttpInterpreter.parse)

Eventually this will call rasa.nlu.model.Interpreter.parse, which does not accept metadata at all: https://github.com/RasaHQ/rasa/blob/7c8aa9fc44475b8716e4b8cd444a1d7d1ca7506d/rasa/nlu/model.py#L444-L449

This means the UserMessage object available to NLU components is not the same object that the processor has access to. https://github.com/RasaHQ/rasa/blob/7c8aa9fc44475b8716e4b8cd444a1d7d1ca7506d/rasa/nlu/model.py#L467-L470

[indam23]

The original issue description seems to be referring to training data metadata, which is quite different from incoming message metadata. However the linked PR seems to be making incoming message metadata available to the interpreter (although not quite, as above)

[indam23]

Apologies, the above is true for Rasa 2.8.x, this is resolved entirely in Rasa 3.0. Metadata is available in each component's process method in message.data["metadata"]

[mattyd2]

@melindaloubser1 can you provide a link in the docs or code to where message.data["metadata"] is implemented in 3.0?

[indam23]

See here - The UserMessage object, which includes metadata, is now passed down through to processor._handle_message_with_tracker. That allows parsing to access the whole message object also.