vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Examples may include, but are not limited to, statements regarding limitations of liability, third-party claims, and repairs, replacements, or reimbursements as required of the party at fault. 
 Payment Terms & Billing Elements that detail how and when a party is to pay or get paid, and the items or fees the parties will be paying or billed for. Includes references to modes of payment or payment mechanisms. 
 Pricing & Taxes Elements that refer to specific amounts or figures that are associated with individual deliverables that are exchanged (for example, how much something costs) as part of satisfying the terms of the contract. Includes references to specific figures or methods for calculating prices or tax amounts. 
 Privacy Elements that are particularly concerned with the treatment of sensitive personal information, usually regarding its protection (for example, to satisfy regulations such as GDPR). 
 Responsibilities Elements that discuss tasks ancillary to the contract that are in only one party's control and are focused on discussion of employee oversight. 
 Safety and Security Elements referring to physical safety or cybersecurity protection for people, data, or systems. Examples include discussions of background checks, safety precautions, workplace security, secure access protocols, and product defects that might pose a danger. 
 Scope of Work Elements that define what is in the contract versus is not in the contract; consequently, what is promised to be done. Examples include statements that define an order, or describe the goals or aims outlined in the contract. 
 Subcontracts Elements referring to the hiring of third parties to perform certain duties under the contract, and the permissions, rights, restrictions, and consequences thereto and arising therefrom. 
 Term & Termination Elements referring to duration of the contract, the schedule and terms of contract termination, and any consequences of termination, including any obligations that apply at or after termination. 
 Warranties Elements that refer to ongoing promises and obligations that are made in the contract that are currently true and will continue to be true in the future. Also, elements that discuss the consequences of such promises or obligations that are broken, and the rights to remedy the situation (for example, but not limited to, seeking damages). This category does not apply to elements that are concerned with representation statements (statements of fact about the past or the present), or to elements that lay out assumptions about things that occurred in the past. 







 Attributes
* location: The location of the cell in the input document as defined by its begin and end indexes.
* text: The textual contents of the cell from the input document without associated markup content.
* text_normalized: Normalized column header text.
* row_index_begin: The begin index of the cell's row location in the current table.
* row_index_end: The end index of the cell's row location in the current table.
* column_index_begin: The begin index of the cell's column location in the current table.
* column_index_end: The end index of the cell's column location in the current table.



* row_headers: An array of row-level cells, each applicable as a header to other cells in the same row as itself, of the current table. Each row header is defined as a collection of the following items:



* cell_id: The unique ID of the cell in the current table.
* location: The location of the cell in the input document as defined by its begin and end indexes.
* text: The textual contents of the cell from the input document without associated markup content.
* text_normalized: Normalized row header text.
* row_index_begin: The begin index of the cell's row location in the current table.
* row_index_end: The end index of the cell's row location in the current table.
* column_index_begin: The begin index of the cell's column location in the current table.
* column_index_end: The end index of the cell's column location in the current table.



* body_cells: An array of cells that are not table header or column header or row header cells, of the current table with corresponding row and column header associations. Each body cell is defined as a collection of the following items:



* cell_id: The unique ID of the cell in the current table.
* location: The location of the cell in the input document as defined by its begin and end indexes.
* text: The textual contents of the cell from the input document without associated markup content.
"Watson Discovery is an award-winning AI search technology."





 Response 

In the JSON output:



* text = The keyword text
* mentions = The entity mentions and locations



{
"keywords": [
{
"mentions":
{
"location": {
"end": 157,
"begin": 141
},
"text": "Watson Discovery"
}
],
"text": "Watson Discovery",
"relevance": 0.503613
},
{
"mentions":
{
"location": {
"end": 177,
"begin": 164
},
"text": "award-winning"
}
],
"text": "award-winning",
"relevance": 0.728722
},
{
"mentions":
{
"location": {
"end": 198,
"begin": 181
},
"text": "search technology"
}
],
"text": "search technology",
"relevance": 0.779356
}
]
}
Show more







 Keywords limits 

The Keywords enrichment can identify up to 50 keywords, each with one or many mentions, per document.







 Part of speech 

Recognizes and tags parts of speech, including nouns, verbs, adjectives, adverbs, conjunctions, interjections, and numerals.
* ibmcloud is backup-policies --tag dev:test







 Command options 



* --tag: Filters the collection to resources with the exact tag value.
* --resource-group-id: ID of the resource group. This ID is mutually exclusive with --resource-group-name.
* --resource-group-name: Name of the resource group. This name is mutually exclusive with --resource-group-id.
* --all-resource-groups: Query all resource groups.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



--------------------







 ibmcloud is backup-policy-create 

Create a backup policy.

ibmcloud is backup-policy-create --match-tags MATCH_TAGS [--name NAME] [--plans PLANS_JSON | @PLANS_JSON_FILE] | --plan-cron-spec PLAN_CRON_SPEC --plan-name PLAN_NAME] --plan-active --plan-attach-tags PLAN_ATTACH_TAGS] --plan-copy-tags true | false] --plan-delete-after PLAN_DELETE_AFTER] --plan-delete-over-count PLAN_DELETE_OVER_COUNT]] --plan-clone-policy-zones ZONE1,ZONE2,...] --plan-clone-policy-max-snapshots PLAN_CLONE_POLICY_MAX_SNAPSHOTS]]] [--resource-group-id RESOURCE_GROUP_ID | --resource-group-name RESOURCE_GROUP_NAME] [--output JSON] [-q, --quiet]



 Command examples 



* ibmcloud is backup-policy-create --match-tags dev:test --name demo-bkp-policy-1 --plan-name demo-bkp-plan-1 --plan-cron-spec '45 09 * * '
...
],
"body_cells" :
{
"cell_id" : string,
"location" : {
"begin" : int,
"end" : int
},
"text" : string,
"row_index_begin" : int,
"row_index_end" : int,
"column_index_begin" : int,
"column_index_end" : int,
"row_header_ids": string ],
"row_header_texts": string ],
"row_header_texts_normalized": string ],
"column_header_ids": string ],
"column_header_texts": string ],
"column_header_texts_normalized": string ],
"attributes" :
{
"type" : string,
"text" : string,
"location" : {
"begin" : int,
"end" : int
}
},
...
]
},
...
],
"contexts":
{
"text": string,
"location" : {
"begin" : int,
"end" : int
}
}
...
],
"key_value_pairs":
{
"key": {
"cell_id": string,
"location": {
"begin": int,
"end": int
},
"text": string
},
"value": {
"cell_id": string,
"location": {
"begin": int,
"end": int
},
"text": string
},
...
]
},
...
]
},
...
],
"document_structure": {
"section_titles": [
{
"text": string,
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. Simply use the "DELETE" HTTP method with the ?tagging query parameter to delete all tags. If you wish to delete one or more tags while simultaneously keeping one or more tags, use the "edit" instructions to make your changes.

curl -X "DELETE" 'https://<endpoint>/<bucketname>/<objectname>?tagging' -H 'Authorization: bearer <token>' -H "content-type: text/plain"







 Next Steps 

Find more details about the operations related to objects in the [S3 API documentation](https://cloud.ibm.com/apidocs/cos/cos-compatibility) and more configuration options in the [configuration API](https://cloud.ibm.com/apidocs/cos/cos-configuration).
globalTaggingService.deleteTagAll(params)
.then(res => {
console.log(JSON.stringify(res.result, null, 2));
})
.catch(err => {
console.warn(err)
});







 Deleting tags by using Terraform 

Before you can delete tags by using Terraform, make sure that you have completed the following:



* Install the Terraform CLI and configure the IBM Cloud Provider plug-in for Terraform. For more information, see the tutorial for [Getting started with Terraform on IBM Cloud®](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-getting-started). The plug-in abstracts the IBM Cloud APIs that are used to complete this task.
* Create a Terraform configuration file that is named main.tf. In this file, you define resources by using HashiCorp Configuration Language. For more information, see the [Terraform documentation](https://www.terraform.io/docs/language/index.html).



Use the following steps to delete tags from your account:



1. Create an argument in your main.tf file. The following example deletes the ibm_tag from the resource ibm, which is attached to resource ID ibm_satellite_location.location.crn.

resource "ibm_resource" "ibm" {
resource_id = ibm_satellite_location.location.crn
tags = [ "ibm_tag" ]
}
2. After you finish building your configuration file, initialize the Terraform CLI. For more information, see [Initializing Working Directories](https://www.terraform.io/cli/init).

terraform init
3. Provision the resources from the main.tf file. For more information, see [Provisioning Infrastructure with Terraform](https://www.terraform.io/cli/run).



1.
* text: The text that is associated with the attribute.
* location: The location of the attribute as defined by its begin and end indexes.





* effective_dates: An array that identifies the date or dates on which the document becomes effective.



* confidence_level: The confidence level of the identification of the effective date. Possible values include High, Medium, and Low.
* text: An effective date, which is listed as a string.
* text_normalized: The normalized form of the effective date, which is listed as a string. This element is optional; it is returned only if normalized text exists.
* location: The location of the date as defined by its begin and end indexes.
* 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.



* contract_amounts: An array that monetary amounts that identify the total amount of the contract that needs to be paid from one party to another.



* confidence_level: The confidence level of the identification of the contract amount. Possible values include High, Medium, and Low.
* text: A contract amount, which is listed as a string.
* text_normalized: The normalized text, if applicable.
* interpretation: The details of the normalized text, if applicable.



* value: A string listing the value that was found in the normalized text.
* numeric_value: An integer or float expressing the numeric value of the value key.
* unit**: A string listing the unit of the value that was found in the normalized text.



* location: The location of the amount or amounts as defined by its begin and end indexes.
* 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.



* termination_dates: An array that identifies the date or dates on which the document is to be terminated.



* confidence_level: The confidence level of the identification of the termination date. Possible values include High, Medium, and Low.
* text: A termination date, which is listed as a string.
By default, AQL uses Perl syntax for regular expressions, which means that regular expression literals are enclosed in two forward slash (//) characters. Regular expression escape sequences take precedence over other escape characters. AQL allows regular expressions in SQL string syntax, so a regular expression for United States phone numbers can be expressed as either of the examples:

/d{3}-d{5}/

'\d{3}-\d{5}'
* [and /<regex2>/ and ... and /<regex n>/ ]

Lists more regular expressions to be used in the extraction.
* [with flags '<flags string>']

Specifies a combination of flags to control regular expression matching. This parameter is optional. These flags correspond to a subset of the flags that are defined in the Java™ implementation. If the flags string is not provided, AQL uses only the DOTALL flag by default.

To specify multiple flags, separate them with the | character. For example, to specify multiline matching, matching that is not case-sensitive, and Unicode case folding, use the flags string 'MULTILINE|CASE_INSENSITIVE|UNICODE'.
* [<token spec>]

Indicates whether to match the regular expression only on token boundaries.

... [between <number> and] <number> tokens] in] ...

Token constraints are an optional part of the specification. If token constraints are omitted, AQL returns the longest non-overlapping match at each character position in the input text. If token constraints are present, the extract statement returns the longest match at every token boundary that is within the specified range of tokens in length. Each returned match must start at the beginning of a token and end at the end of a token. If multiple overlapping matches exist, the extract statement returns all of them.

The locations of token boundaries depend on what tokenizer the runtime component is using to tokenize the document. If the engine is using the Standard tokenizer, then a token is defined as a sequence of word characters or a single punctuation character.

For example, consider the string:

"The fish are pretty," said the boy.
"passage_text":"Disaster Recovery Services for Hybrid Cloud</title></head>n<body>nnn<p>Published: Thu, 27 Oct 2016 07:01:21 GMT</p>n"
"passage_score":10.153470191601558,
"document_id":"fbb5dcb4d8a6a29f572ebdeb6fbed20e",
"start_offset":70
"end_offset":120
"field":"html"
},
...
Show more
<-- <section "id="section-passages_fields" "> --> passages.fields A comma-separated list of fields in the index that passages are drawn from. If this parameter not specified then all top level field are included.<-- </section "id="section-passages_fields" "> --><-- <section "id="section-passages_count" "> --> passages.count The maximum number of passages to return. The search returns fewer passages if that is the total number found. The default is 10. The maximum is 100.<-- </section "id="section-passages_count" "> --><-- <section "id="section-passages_characters" "> --> passages.characters The approximate number of characters that any one passage must have. The default is 400. The minimum is 50. The maximum is 2000. 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.
No supported roles.





 GhoST Tagging Service 

Review the available platform and service roles and the actions mapped to each to help you assign access. If you're using the CLI or API to assign access, use ghost-tags for the service name.

Platform roles

Actions



Table 62. Platform roles - GhoST Tagging Service
Use the tab buttons to change the context of the table. This table has row and column headers. The row headers provide the platform role name and the column headers identify the specific information available about each role.

 Role Description 

 Administrator As an administrator, you can perform all platform actions based on the resource this role is being assigned, including assigning access policies to other users. 







 Global Catalog 

Review the available platform and service roles and the actions mapped to each to help you assign access. If you're using the CLI or API to assign access, use globalcatalog for the service name.

Platform roles

Actions



Table 63. Platform roles - Global Catalog
Use the tab buttons to change the context of the table. This table has row and column headers. The row headers provide the platform role name and the column headers identify the specific information available about each role.

 Role Description 

 Administrator Administrators can change object metadata or visibility for private services added to the account and can restrict the visibility of a public service. 
 Editor Editors can change object metadata, but can’t change visibility for private services added to the account. 
 Operator Operators can view private services added to the account. 
 Viewer Viewers can view private services added to the account. 







 Personal Catalog 

Review the available platform and service roles and the actions mapped to each to help you assign access. If you're using the CLI or API to assign access, use globalcatalog-collection for the service name.

Platform roles

Service roles

Actions



Table 64. Platform roles - Personal Catalog
Use the tab buttons to change the context of the table. This table has row and column headers. The row headers provide the platform role name and the column headers identify the specific information available about each role.

 Role Description
* Flag: --bucket BUCKET_NAME



* Optional: A DELIMITER is a character that you use to group keys.



* Flag: --delimiter DELIMITER



* Optional: Requests to encode the object keys in the response and specifies the encoding METHOD to use.



* Flag: --encoding-type METHOD



* Optional: Limits the response to keys that begin with the specified PREFIX.



* Flag: --prefix PREFIX



* Optional: A TOKEN to specify where to start paginating. This is the NextToken from a previously truncated response.



* Flag: --starting-token TOKEN



* Optional: The SIZE of each page to get in the service call. This does not affect the number of items returned in the command's output. Setting a smaller page size results in more calls to the service, retrieving fewer items in each call. This can help prevent the service calls from timing out. (default: 1000)



* Flag: --page-size SIZE



* Optional: The total NUMBER of items to return in the command's output. If the total number of items available is more than the value specified, a NextToken is provided in the command's output. To resume pagination, provide the NextToken value in the starting-token argument of a subsequent command. (default: 0)



* Flag: --max-items NUMBER



* Optional: The REGION where the bucket is present. If this flag is not provided, the program uses the default option that is specified in config.



* Flag: --region REGION



* Optional: Output FORMAT can be only json or text.



* Flag: --output FORMAT











 List parts 



* Action: Print out information about an in progress multipart upload instance.
* Usage:ibmcloud cos parts --bucket BUCKET_NAME --key KEY --upload-id ID --part-number-marker VALUE [--page-size SIZE] [--max-items NUMBER] [--region REGION] [--output FORMAT]
* Parameters to provide:



* The name of the bucket.



* Flag: --bucket BUCKET_NAME
create view Conjunction as
extract
dictionary 'ConjunctionDict'
on D.text
as name
from Document D;







 Splits 

Use the split extraction specification to split a large span into several smaller spans.



 Syntax 

split using <name>.<split point column>
[retain right|left|both] split points]]
on <name>.<column to split>
as <output name>





 Description 

The split extraction specification takes two arguments:



* A column that contains longer target spans of text.
* A column that contains split points.



The splitting algorithm works in two passes over the input view. The first pass groups all of the input tuples by the target column. The second pass goes through the tuples in each group, splitting the target column with each value of the splitting column.



* <name>.<split point column>

Specifies the split points for the extraction.
* [retain right|left|both] split points]]

Specifies how to treat the left and right end points of each result. This argument is optional.



* If retain left split point is specified, then each output span also contains the split point to its left, if such a split point exists.
* If retain right split point is specified, then the system makes each output span contain the split point to its right.
* The split extraction also accepts null values as split points. For each such value, the extraction returns a tuple that contains the entire input span.



* <name>.<column to split>

Specifies the target column for the extraction.
* <output name>

Defines the name of the output of the extraction.







 Examples 

Example 1: Split points and the retain clause

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
They are not supported.





 The <paragraph> and <sentence> elements 

The <paragraph> (or <p>) and <sentence> (or 
) elements are optional elements that can be used to give hints about textual structure. If the text that is enclosed in a <paragraph> or <sentence> element does not end with an end-of-sentence punctuation character (like a period), the service adds a longer than normal pause to the synthesized audio.

The only valid attribute for either element is xml:lang, which allows for language switching. The attribute is not supported.

<paragraph>
<sentence>Text within a sentence element.</sentence>

More text in another sentence.

</paragraph>





 The <phoneme> element 

The <phoneme> element provides a phonetic pronunciation for the enclosed text. The phonetic spelling represents the sounds of a word, how the sounds are divided into syllables, and which syllables receive stress. The element has two attributes:



* alphabet is an optional attribute that specifies the phonology to be used. The supported alphabets are



* The standard International Phonetic Alphabet (IPA):alphabet="ipa".
* The IBM Symbolic Phonetic Representation (SPR):alphabet="ibm".



If no alphabet is specified, the service uses IBM SPR by default. For more information, see [Understanding phonetic symbols](https://cloud.ibm.com/docs/text-to-speech?topic=text-to-speech-symbols).
* ph is a required attribute that provides the pronunciation in the indicated alphabet. The following examples show the pronunciation for the word tomato in both formats:



* IPA format:

<phoneme alphabet="ipa" ph="təˈmeɪ.ɾoʊ">tomato</phoneme>
* IPA format with Unicode symbols:

<phoneme alphabet="ipa" ph="təˈmeɪ.ɾoʊ">tomato</phoneme>
* IBM SPR format:

<phoneme alphabet="ibm" ph=".0tx.1me.0Fo">tomato</phoneme>