vania-janet/multiturn-rag-retrieval-data huggingface dataset:
From the Skills menu, click Dialog.<-- </section "id="section-dialog-runtime-disambig-edit" "> --><-- <section "id="section-dialog-runtime-disambig-choose-nodes" "> --> Choosing nodes to not show as disambiguation options All nodes are eligible to be included in the disambiguation list. - Nodes at any level of the tree hierarchy are included.
- Nodes that condition on intents, entities, special conditions, context variables, or any combination of these values are included.
Consider hiding some nodes from the disambiguation list.<-- <ul> --> * Hide root nodes with welcome and anything_else conditions
Unless you added extra functionality to these nodes, they typically are not useful options to include in a disambiguation list.
* Hide jumped-to utility nodes
The text that is displayed in the disambiguation list is populated from the node name (or external node name) of the last node that is processed in the branch where the node condition is matched.

You do not want the name of a utility node, such as one that thanks the user, or says goodbye, or asks for feedback on answer quality to be shown in the disambiguation list instead of a phrase that describes the purpose of the matched root node.

For example, maybe a root node with the matching intent condition of store-location jumps to a node that asks users if they are satisfied with the response. If the check_satisfaction node has a node name and has disambiguation enabled, then the name for that jumped-to node is displayed in the disambiguation list. As a result, Check satisfaction is displayed in the disambiguation list to represent the store-location branch instead of the Get store location name from the root node.
* Hide root nodes that condition on an entity or context variable only
Only a node with a matched intent can trigger disambiguation. However, once it's triggered, any node with a condition that matches is included in the disambiguation list.
Passages returned might be up to twice the requested length, if necessary, to get them to begin and end at sentence boundaries.<-- </section "id="section-passages_characters" "> --><-- </section "id="section-passages" "> --><-- <section "id="section-highlight" "> --> highlight A boolean that specifies whether the returned output includes a highlight object in which the keys are field names and the values are arrays that contain segments of query-matching text highlighted by the HTML * tag.The output lists the highlight object after the enriched_text object, as shown in the following example. curl -u "apikey":"{apikey_value}" "{url}/v1/environments/{environment_id}/collections/{collection_id}/query?version=2019-04-30&natural_language_query=Hybrid%20cloud%20companies&highlight=true"
Replace {apikey} and {url} with your API key and URL.The returned JSON is in the following format: {
"highlight": {
"extracted_metadata.title":
"IBM to Acquire Sanovi Technologies to Expand Disaster Recovery Services for <em>Hybrid</em> <em>Cloud</em>"
],
"enriched_text.concepts.text":
"Privately held <em>company</em>",
"<em>Cloud</em> computing"
],
"text":
" Sanovi Technologies, a privately held <em>company</em> that provides <em>hybrid</em> <em>cloud</em> recovery, <em>cloud</em> migration",
"IBM to Acquire Sanovi Technologies to Expand Disaster Recovery Services for <em>Hybrid</em> <em>Cloud</em>nnPublished",
" undergoing digital and <em>hybrid</em> <em>cloud</em> transformation.nnURL: http://www.ibm.com/press/us/en/pressrelease/50837.wss",
[Save tags when complete](https://cloud.ibm.com/docs-content/v1/content/63322f2f3a72050206eb05ba7f590fdcb741105c/cloud-object-storage/images/object-save-tags.jpg)

Your requests must be authenticated in order to tag your data. Also, you will have to programmatically keep any old tags while updating your objects with new information. The example shown repeats the tags from the previous examples while adding a new tag.

Remember that performing "PUT" operations involving tags will overwrite any current tags.

curl -X "PUT" 'https://<endpoint>/<bucketname>/<objectname>?tagging' -H 'Authorization: bearer <token>' -H "content-type: text/plain" --data "<Tagging><TagSet><Tag><Key>source</Key><Value>text</Value></Tag><Tag><Key>source1</Key><Value>text1</Value></Tag></TagSet></Tagging>"





 Removing tags 

After you have added tags to your objects, it may become necessary to remove them.

In order to delete the tags using the graphic interface, you will have to log into the console and access your objects as previously described. Again, click on the "Manage tags" option, and in the panel that appears, choose either to "delete all" or delete one tag at a time by clicking on the "trash can" icon in the same row as the tag.

Remember to press "Save" when complete.

![Delete one or all tags](https://cloud.ibm.com/docs-content/v1/content/63322f2f3a72050206eb05ba7f590fdcb741105c/cloud-object-storage/images/object-edit-tags.jpg)

You will have to authenticate in order to delete tags from your data.
Name the regular expression. For example, MyAgeRegex.

The name cannot be longer than 64 characters.
3. Associate the expression with a class. For example, AGE_REGEX.
4. Click Add Entry.
5. Add the expression.

For example, to capture a number that represents an age (up to age 99), you can specify [0-9]{1,2}. To capture expressions of time, like 12:30 AM, you might specify this regular expression:

(1[0-2]|0?[1-9]):([0-5])(s+[AaPp])?

You can optionally change the minimum and maximum number of word tokens. In English, tokens are often equated to words as delimited by white spaces in a sentence. However, they do not always match one-to-one with words. Other textual elements are considered tokens in some situations. For example, the hyphens in the term 50-year-old each count as a token, which means the total number of tokens used in this term is 5. And the text 12:30 PM contains 4 tokens. (12 | : | 30 | PM)

Click Add.
6. Repeat the previous two steps if you want to add more expressions.
7. Click Save.



The regex editor closes, and the document is displayed. You should see the class that you defined for the regular expression applied to the text that you intended it to match against. If you do not see the annotation, check your expression. It might need to be revised so it matches the text that you intended for it to find.

![The rule editor showing the "Regex" tab selected, a regular expression called "Age" that's associated with the class "AGE_REGEX", and a document that shows the text "50" highlighted in yellow. The highlighted text matches the regular expression that was created.]
For each value you specify a bunch of synonyms (aqua, navy). You can also pick synonyms to add from recommendations made to you by Watson.

At run time, your assistant recognizes terms in the user input that exactly match the values or synonyms that you defined for the entity as mentions of that entity.
* Pattern entity: You define a category of terms as an entity (contact_info), and then one or more values in that category (email). For each value, you specify a regular expression that defines the textual pattern of mentions of that value type. For an email entity value, you might want to specify a regular expression that defines a text@text.com pattern.

At run time, your assistant looks for patterns matching your regular expression in the user input, and identifies any matches as mentions of that entity.
* System entity: Synonym entities that are prebuilt for you by IBM. They cover commonly used categories, such as numbers, dates, and times. You simply enable a system entity to start using it.







 Annotation-based method 

When you define an annotation-based entity, which is also referred to as a contextual entity, a model is trained on both the annotated term and the context in which the term is used in the sentence you annotate. This new contextual entity model enables your assistant to calculate a confidence score that identifies how likely a word or phrase is to be an instance of an entity, based on how it is used in the user input.



* Contextual entity: First, you define a category of terms as an entity (product). Next, you go to the Intents page and mine your existing intent user examples to find any mentions of the entity, and label them as such. For example, you might go to the buy_something intent, and find a user example that says, I want to buy a Coach bag. You can label Coach bag as a mention of the @product entity.

For training purposes, the term you annotated, Coach bag, is added as a value of the @product entity.

At run time, your assistant evaluates terms based on the context in which they are used in the sentence only.
Specify one label per --tag option; for example, --tag tagA --tag tagB. This value is optional.

--tag-rm, --trm
: Remove a label assigned to your project. Specify one label per --tag-rm option; for example, --tag-rm tagA --tag-rm tagB. This value is optional.





 Example 

ibmcloud ce project tag --name myproject --tag tag1 --tag tag2





 Example output 

Getting project 'myproject'...
OK







 ibmcloud ce project update 

Update the selected project.

ibmcloud ce project update (--binding-service-id SERVICE_ID_ID | --binding-resource-group RESOURCE_GROUP_NAME | --binding-resource-group-id RESOURCE_GROUP_ID) [--quiet]



 Command Options 

--binding-resource-group, --brg
: The name of a resource group to use for authentication for the service bindings of this project. A service ID is created with Operator and Manager roles for all services in this resource group. Use "" to specify all resource groups in this account. This value is optional.

--binding-resource-group-id, --brgid
: The ID of a resource group to use for authentication for the service bindings of this project. A service ID is created with Operator and Manager roles for all services in this resource group. This value is optional.

--binding-service-id, --bsid
: The ID of a service ID to use for authentication for the service bindings of this project. This service ID must have the Operator role and an appropriate service role for one or more service instances, service types, or resource groups. This value is optional.

--quiet, -q
: Specify this option to reduce the output of the command. This value is optional. The default value is false.





 Example 

ibmcloud ce project update --binding-service-id ServiceId-1234abcd-abcd-abcd-1111-1a2b3c4d5e6f
* If the input span starts or ends with white space (for example, it starts between two tokens or ends between two tokens), the function ignores the beginning and trailing white space.
* If the input span starts in the middle of a token or ends in the middle of a token, then the output consists of the following content, in this order, and separated by a white space:



* The surface form of the first partial token if it exists.
* The sequence of lemmas that correspond to the first to last complete tokens. If the lemma for any of the complete tokens consists of white spaces, escape the white spaces by using the backslash character (\).
* The surface form of the last partial token if it exists.





This function returns an error if the tokenizer that is being used is not capable of producing lemmas.

You can use the GetLemma() function to create dictionaries of lemmatized forms. Call GetLemma() on an input that contains the terms whose lemmatized form you want to include in the dictionary.





 GetLength 

The GetLength function takes a single span argument and returns the length of the input span. If the argument is null, the function returns null.

For example,

GetLength([5, 12])

returns a value of 7.





 GetLengthTok 

The GetLengthTok function takes a single span argument and returns the length of the input span in tokens. If the input argument is null, the function returns null.





 GetString 

The GetString function takes a single AQL object as its argument and returns a Text object that is formed from the string representation of the object.

For span and text arguments, the values that are returned are different from those returned by GetText(). For Text objects, the returned value includes single quotation marks surrounding the text string. For span objects, the returned value includes in addition offsets in brackets.

For scalar lists, this function returns the GetString() values of the elements of the list, concatenated with semicolons. For Integer, Float, Boolean, and String arguments, this function returns the value of the argument as a string.
* location: The location of the contract term as defined by its begin and end indexes.



* contract_currencies: An array that identifiea the document's contract currency or currencies.



* confidence_level: The confidence level of the identification of the contract currency. Possible values include High, Medium, and Low.
* text: A contract currency, which is listed as a string.
* text_normalized: The normalized text, if applicable. It is listed as a string in [ISO-4217](https://www.iso.org/iso-4217-currency-codes.html) format
* provenance_ids: An array that contains zero or more keys. Each key is a hashed value that you can send to IBM to provide feedback or receive support.
* location: The location of the contract currency as defined by its begin and end indexes.



* tables*: An array that defines the tables identified in the input document.



* location: The location of the current table as defined by its begin and end indexes in the input document.
* text: The textual contents of the current table from the input document without associated markup content.
* section_title: If identified, the location of a section title contained in the current table. Empty if no section title is identified.



* text: The text of the identified section title.
* location: The location of the section title in the input document as defined by its begin and end indexes.



* title: If identified, the title or caption of the current table of the form Table x.: .... Empty when no title is identified. When exposed, the title is also excluded from the contexts array of the same table.



* location: The location of the title in the input document as defined by its begin and end indexes.
* text: The text of the identified table title or caption.



* table_headers: An array of table-level cells applicable as headers to all the other cells of the current table. Each table header is defined as a collection of the following elements:



* cell_id: The unique ID of the cell in the current table.
* eventId: Displays the unique ID of the event.
* partInfo: Displays whether the message is split into parts. The format is [1-X]. For example, [1-1] indicates 1 message only.
* createdTime: Displays the time when the event is generated.
* eventType: Displays the event type.
* severity: Displays whether the event is informational, a warning message, or an error.
* user: Displays the name of the initiator of the request.
* target: Displays the object the event refers to.
* chainId: Displays information about the parent ID or the group ID.
* desc: Displays the description of the event.



Events that are split into multiple syslog messages have the following format:

<syslog-prefix> : Event [eventId] [1-X] [payload-part-1]
<syslog-prefix> : Event [eventId] [2-X] [payload-part-2]
...
<syslog-prefix> : Event [eventId] [X-X] [payload-part-X]

Where X represents the total number of the event message parts.

For example:

<14>1 2023-02-07T20:20:15.600724+00:00 vcsobserv-vc vpxd 6757 - - Event [125101] [1-1] [2023-02-07T20:20:15.599975Z] [vim.event.EventEx] [info] [com.vmware.vim.eam] [] [125101] [Successful login by com.vmware.nsx.management.nsxt into vSphere ESX Agent Manager]
For more information, see [Working with tags](https://cloud.ibm.com/docs/account?topic=account-tag).
* What access is required to create access management tags?

You must be the account owner or have the following roles:



* Administrator on all account management services
* Administrator on the tagging service



For more information, see [Granting users access to tag resources](https://cloud.ibm.com/docs/account?topic=account-access).
* What access is required to attach or detach tags?



* To manage user tags on a resource, you must have at least the editor role for IAM-enabled resources.
* To manage user tags on a service ID, you must have at least the editor role on the IAM Identity service.
* To manage access management tags, you must have the administrator role on the targeted resource.
* To manage access management tags on service IDs, you must have the administrator role on the IAM Identity service.



For more information, see [Granting users access to tag resources](https://cloud.ibm.com/docs/account?topic=account-access).
* Can users in my account view my tags?

Yes, tags are visible throughout your account. If your account users have permission to view a resource, they can also view all tags that are attached to those resources. For more information, see [Granting users access to tag resources](https://cloud.ibm.com/docs/account?topic=account-access).
* Can I delete my tags?

Before you can delete a tag, you must detach it from all resources. The tag might be attached to a resource that you don't have permission to view. The same tag can be attached to several resources by different users in the same billing account. Users don't have the same visibility on all resources on the account. Contact the account owner who can resolve the problem by detaching the tag from the blocking resource.

If you still can't delete it, the tag might be attached to a reclaimed resource. You can use the IBM Cloud CLI to manage the reclamation process of specific resources.
on <name>.<column containing spans>
as <output name>





 Description 



* with count [between<min> and] <max>

Specifies how many spans can make up a block. The <min> and <max> values specify the minimum and maximum number of spans that can make up a block.
* [between 0 and] <max>

Specifies the separation distance that is allowed between spans before they are no longer considered to be contiguous.
* (tokens| characters)

Specifies whether the separation distance of the span represents the number of tokens or the number of characters.
* <name>.<column containing spans>

The view name and column name on which the block operator is to be applied.
* <output name>

Specifies a name for the output from the block operator.







 Usage notes 



* If the input scans contain multiple overlapping blocks in the input spans, a block extraction statement returns all possible blocks. Use consolidation to filter out redundant blocks.
* An extract statement with block extraction specification yields blocks that each consist of an aggregation of values of a certain field from across multiple input tuples. Therefore, its select list cannot include fields from its input view.







 Examples 

Example 1: Extract blocks of words within a character range

In the following code, the view TwoToThreeCapitalizedWords identifies blocks of two to three capitalized words within 100 characters of each other.

create view CapitalizedWords as
extract
regex /[A-Z]/
with flags 'CANON_EQ'
on 1 token in D.text
as word
from Document D;

create view TwoToThreeCapitalizedWords as
extract blocks
with count between 2 and 3
and separation between 0 and 100 characters
on CW.word as capswords
from CapitalizedWords CW;

Example 2: Extract blocks of words within a token range

The following code identifies blocks of exactly two capitalized words within five tokens of each other.

create view TwoCapitalizedWords as
extract blocks
with count 2
and separation between 0 and 5 tokens
on CW.word as capswords
from CapitalizedWords CW;







 Part of speech
The --tag option filters the collection of backup policies with the exact user tag value.

ibmcloud is backup-policies --tag

The following example produces a list of backup policies that have the dev:test tag.

cloudshell:$ ibmcloud is backup-policies --tag dev:test
Listing backup policies in all resource groups and region eu-de under account Test Account as user test.user@ibm.com...
ID Name Status Resource group
r138-0521986d-963c-4c18-992d-d6a7a99d115f backup-policy-v1 stable defaults
r138-8c494618-9e4f-4b67-9a08-ee3491404f3b my-backup-policy-v1 stable defaults
r138-5c719085-cf26-456e-9216-984866659e29 my-backup-policy-v2 stable defaults

For more information about available command options, see [ibmcloud is backup-policies](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-referencebackup-policies).





 Viewing backup policy details from the CLI 

Run the backup-policy command and specify either the backup policy ID or the policy name.

ibmcloud is backup-policy POLICY [--output JSON] [-q, --quiet]

The following example uses the policy ID and the option to receive the response in JSON format.

cloudshell:$ ibmcloud is backup-policy r138-0521986d-963c-4c18-992d-d6a7a99d115f --output JSON
{
"created_at": "2023-02-21T22:42:10.000Z",
If the split points are all the instances of the word fish in the phrase fish are swimming in the fish pond, then the various versions of the retain clause have the following effects:



* retain clause omitted

are swimming in the " and " pond
* retain right split point

are swimming in the fish" and " pond
* retain left split point

fish are swimming in the " and "fish pond
* retain both split points

fish are swimming in the fish" and "fish pond



Example 2: Split extraction

This example splits the document into sentences. It first uses a regular expression to identify sentence boundaries, then uses the split extraction specification to split the document text on the sentence boundaries.

create dictionary AbbreviationsDict as
(
'Cmdr.',
'Col.',
'DR.',
'Mr.',
'Miss.');

create view Sentences as
extract
split using B.boundary
retain right split point
on B.text
as sentence
from (
extract
D.text as text,
regex /(([!.?]+s)|(nsn))/
on D.text as boundary
from Document D
-- Filter the candidate boundaries.
having Not(ContainsDict('AbbreviationsDict',
CombineSpans(LeftContextTok(boundary, 1), boundary)))
) B;
Show more







 Blocks 

Use the blocks extraction specification to identify blocks of contiguous spans across input text.



 Syntax 

blocks
with count [between <min> and] <max>
and separation [between 0 and] <max> (tokens| characters)
on <name>.<column containing spans>
as <output name>





 Description 



* with count [between<min> and] <max>

Specifies how many spans can make up a block. The <min> and <max> values specify the minimum and maximum number of spans that can make up a block.
* [between 0 and] <max>

Specifies the separation distance that is allowed between spans before they are no longer considered to be contiguous.