vania-janet/multiturn-rag-retrieval-data huggingface dataset:
A relation links two different entities in the same sentence.





 relation type 

A binary, unidirectional relationship between two entities. For example, Mary employedBy IBM is a valid relationship; IBM employedBy Mary is not.





 Representational State Transfer (REST) 

A software architectural style that guides the design and development of the architecture for the web. REST defines a set of constraints for the architecture of Internet-scale distributed hypermedia systems, such as the web.





 resource 

A physical or logical component that can be provisioned or reserved for an application or service instance. Examples of resources can include storage, processors, memory, clusters, and VMs.





 resource group 

The environment, and constraints, in which contained resource instances adhere to. A user can be associated with a resource group to enable collaboration.





 REST 

See [Representational State Transfer](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx3220976).





 role 



* An attribute that provides a context-sensitive meaning of a mention. For example, in the phrase "I went to IBM today", IBM is the mention, Organization is the entity type, and Facility is the role of the entity type.
* A set of permissions or access rights.







 root key 

A symmetric wrapping key that is used for encrypting and decrypting other keys that are stored in a data service.





 route 

The URL that is used to direct requests to an application. A route is made up of an optional host (or subdomain) and a domain that are specified when an application is pushed. For example, in the route myapp.example.com, myapp is the host and example.com is the domain. A route can be associated with one or more applications. Unless a custom domain is specified, IBM Cloud uses a default shared domain in the route to an application.
[solution tutorial icon](https://cloud.ibm.com/media/docs/images/homepage/solution-tutorial.svg) [SQL Database for Cloud data](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-sql-database)SQL Database for Cloud data Solution tutorial

This tutorial shows how to provision a SQL (relational) database service. As administrator, you create a table and load a large data set (city information) into the database. Then, you deploy a web app "worldcities" to Code Engine. The app allows regular users to look up records from the cloud database. The app is written in Python using the Flask framework.

![solution tutorial icon](https://cloud.ibm.com/media/docs/images/homepage/solution-tutorial.svg) [Team based privacy using IAM, VPC, Transit Gateway and DNS](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-tg-dns-iam)Team based privacy using IAM, VPC, Transit Gateway and DNS Solution tutorial

Microservices are popular because they allow an enterprise to organize their development teams around the services they deliver. This tutorial walks you through the steps of creating infrastructure for a IBM Cloud® Virtual Private Cloud (VPC) based microservice architecture. In this architecture, VPCs are connected to each other using the IBM Cloud® Transit Gateway. A set of shared microservices is accessed through host names registered in the IBM Cloud® DNS Services. Each VPC is managed by a separate team isolated by IBM Cloud® Identity and Access Management. Optionally a IBM Cloud® Load Balancer can be used to scale out the shared microservice.

!
Cascade Lake CPU support
: You can choose from the following Intel® Xeon® Cascade Lake CPUs when you provision a bare metal server. For more information, see the Intel Cascade Lake CPU support section of [Bare metal server options](https://cloud.ibm.com/docs/bare-metal?topic=bare-metal-about-bmbm-cascade-lake-support).







 March 2019 



 25 March 2019 

Contract term pricing
: IBM Cloud® Bare Metal Servers gives you the option to lock-in a lesser price by signing a contract term. You choose between either a 1-year or a 3-year contract. A contact term bare metal server is a great option if you know that you need hardware for the long term and makes sure that your resources are available throughout your term. When your term is over, you keep your contracted price on a month-to-month basis. For more information, see [Contract term pricing for bare metal servers](https://cloud.ibm.com/docs/bare-metal?topic=bare-metal-about-reserved-bare-metal-servers).







 April 2018 



 05 April 2018 

Spare pools
: The Spare Pool screen in the IBM Cloud® allows users to manage the spare pool of devices associated with the account. Each device in the spare pool can be used as a backup device if more devices are needed. For more information, see [Spare pools](https://cloud.ibm.com/docs/bare-metal?topic=bare-metal-bm-about-spare-pools).







 March 2018 



 26 March 2018 

Intel Software Guard Extension
: Intel® Software Guard Extension (SGX) is an architecture extension that is designed to increase security by using protected areas in memory that runs your sensitive code and data. For more information, see [Intel Software Guard Extension](https://cloud.ibm.com/docs/bare-metal?topic=bare-metal-bm-intel-sgx).





 16 March 2018 

Block and file storage add-on
: If you need extra storage, IBM makes it easy! You can now order block and file storage (20 - 12,000 GB) when you provision a bare metal server.
Fast Path of IBM Cloud Intel Virtual Servers 

This page is a collection of shortcuts to the documentation sections for each offering, excluding general information that applies to all offerings, such as SAP Sizing.

Use the links in this section to quickly access relevant documents that you are already familiar with.



 Learn 

An Infrastructure-as-a-Service (IaaS) environment consists primarily of compute, storage, and network components from a specified region (such as the US) and a designated site location (also referred to as zone, which is a data center site). For more information:



* [IBM Cloud VPC Infrastructure environment introduction](https://cloud.ibm.com/ddocs/sap?topic=sap-vpc-env-introduction)



Certified Infrastructure-as-a-Service for SAP HANA database server is available in many variations, each with different capabilities and sizes to fit many different SAP workload scenarios. For more information:



* [Infrastructure certified for SAP - IBM Intel Virtual Server](https://cloud.ibm.com/docs/sap?topic=sap-iaas-offeringsiaas-intel-vs)



The following is an overview of the SAP-certified profiles with IBM Power Virtual Servers for SAP HANA and SAP NetWeaver. For more information:



* [IBM Cloud Intel Virtual Server certified profiles for SAP HANA](https://cloud.ibm.com/docs/sap?topic=sap-hana-iaas-offerings-profiles-intel-vs-vpc)
* [IBM Cloud Intel Virtual Server certified profiles for SAP NetWeaver](https://cloud.ibm.com/docs/sap?topic=sap-nw-iaas-offerings-profiles-intel-vs-vpc)
* [Compute Profiles of SAP-certified IBM Cloud Intel Virtual Server](https://cloud.ibm.com/docs/sap?topic=sap-compute-os-design-considerationscompute-vs-vpc)



Your business and functional requirements determine the SAP solutions powered by the SAP HANA Database Server or SAP NetWeaver Application Server, and therefore determine how your applications are run in the available infrastructure. For more information:
Use the slider to select the number of blocks of provisioned throughput capacity based on the maximum limit of either reads per second, writes per second, or global queries per second as required for your application. For example, if your application requires 1,000 reads per second, use the slider to select the capacity that offers 1,000 reads per second, 500 writes per second, and 50 global queries per second. Select this capacity even if you don't need the corresponding number of writes or global queries.





 Data usage pricing 

What about pricing for data overage? How does that work?



Table 1. Pricing for data overage

 Plan Storage included Overage limit 

 Lite 1 GB Your account is blocked from writing new data until you delete enough data to be under the 1-GB limit, or upgrade to a higher plan. 
 Standard 20 GB Extra storage costs charged per GB per hour, for each GB over the included 20 GB. 







 IBM Cloud Usage Dashboard 

How does data populate the IBM Cloud Usage Dashboard?

Current and historical usage bills can be seen in the IBM Cloud Dashboard, under Manage > Billing and usage > Usage. This view shows the totals for usage that are accrued during a particular month at the service, plan, or instance level. The Estimated Total reflects the bill so far for the month or for past complete months. It shows only the hourly costs that are accrued up to that point for the current month.
Available data centers 

Each IBM Cloud® data center is connected to the IBM global private network — making data transfers faster and more efficient everywhere. The available FSA data centers and their locations are listed here.



Table 1: Available data centers

 Data Center   Location           

 AMS03, Pod 1  Amsterdam          
 DAL09, Pod 1  Dallas             
 DAL09, Pod 6  Dallas             
 DAL10, Pod 1  Dallas             
 DAL10, Pod 2  Dallas             
 DAL12, Pod 1  Dallas             
 DAL12, Pod 2  Dallas             
 DAL13, Pod 1  Dallas             
 DAL13, Pod 2  Dallas             
 DAL13, Pod 3  Dallas             
 FRA02, Pod 2  Frankfurt          
 FRA04, Pod 1  Frankfurt          
 FRA05, Pod 1  Frankfurt          
 LON02, Pod 2  London             
 LON04, Pod 1  London             
 LON05, Pod 1  London             
 LON06, Pod 1  London             
 MON01, Pod 1  Montreal           
 PAR01, Pod 1  Paris              
 SAO01, Pod 1  São Paulo          
 SAO04, Pod 1  São Paulo          
 SAO05, Pod 1  São Paulo          
 SJC03, Pod 1  San Jose           
 SJC03, Pod 2  San Jose           
 SJC04, Pod 1  San Jose           
 SNG01, Pod 2  Singapore          
 SYD01, Pod 1  Sydney             
 SYD04, Pod 1  Sydney             
 TOK02, Pod 1  Tokyo              
 TOK04, Pod 1  Tokyo              
 TOR01, Pod 2  Toronto            
 WDC04, Pod 1  Washington, D.C.   
 WDC04, Pod 2  Washington, D.C.   
 WDC04, Pod 3  Washington, D.C.   
 WDC04, Pod 4  Washington, D.C.   
 WDC04, Pod 5  Washington, D.C.   
 WDC06, Pod 1  Washington, D.C.   
 WDC07, Pod 1  Washington, D.C.   



If you want to see additional locations supported, use this [survey](http://ibm.biz/firewalllocations) to submit feedback.

See [Global locations for your global business](https://www.ibm.com/cloud/data-centers/), for more information on IBM data centers.
`s3.us-south.cloud-object-storage.appdomain.cloud us-south` 





Table 3. Single data center endpoints

 Single data center endpoint name Alias 

 s3.ams03.cloud-object-storage.appdomain.cloud ams03 
 s3.mon01.cloud-object-storage.appdomain.cloud mon01 
 s3.sng01.cloud-object-storage.appdomain.cloud sng01 







 Availability zones 



Table 4. Regions

 Regions Availability zones 

 Dallas 3 
 Frankfurt 3 



For Availability Service Level Agreements, see the [Cloud Services terms](https://cloud.ibm.com/docs/overview?topic=overview-slas).
-t, --storage-type
: Filter by type of storage volume, options are: performance,endurance.

-o, --order
: Filter by ID of the order that purchased the block storage.

--sortby
: Column to sort by, default:id, options are: id,username,datacenter,storage_type,capacity_gb,bytes_used,ip_addr,lunId,active_transactions,created_by.

--column
: Column to display. Options are: id,username,datacenter,storage_type,capacity_gb,bytes_used,ip_addr,lunId,created_by,active_transactions,notes. This option can be specified multiple times.

Examples:

ibmcloud sl block volume-list -d dal09 -t endurance --sortby capacity_gb

This command lists all endurance volumes on current account that are located at dal09, and sorts them by capacity.





 ibmcloud sl block volume-modify 

Modify an existing block storage volume:

ibmcloud sl block volume-modify VOLUME_ID [OPTIONS]

Command options:

-c, --new-size
: New Size of block volume in GB. If no size is given, the original size of volume is used. Potential Sizes: [20, 40, 80, 100, 250, 500, 1000, 2000, 4000, 8000, 12000] Minimum: [the original size of the volume]

-i, --new-iops
: Performance Storage IOPS. Range between [100 and 6000], and in multiples of 100 [only for performance volumes] If no IOPS value is specified, the original IOPS value of the volume is used. Requirements: [If original IOPS/GB for the volume is less than 0.3, new IOPS/GB must also be less than 0.3. If original IOPS/GB for the volume is greater than or equal to 0.3, new IOPS/GB for the volume must also be greater than or equal to 0.3.]

-t, --new-tier
For more information about the components of this hybrid solution, see the following iformation:



* [NetApp AltaVault website ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://mysupport.netapp.com/site/products/all/details/altavault/docsandkb-tab)
* [Veeam Backup & Replication website ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://www.veeam.com/vm-backup-recovery-replication-software.html)
* [IBM Cloud Object Storage website ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://www.ibm.com/cloud/storage)



Utility server refers to a server that contains the VMware vSphere Client that is used to access a private environment and through which the AltaVault appliance that is used for data recovery operations are deployed.
* [NetApp ONTAP-NAS 20.07](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-class-refnetapp-nas-ref)
* [NetApp ONTAP-SAN 21.04](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-class-refnetapp-san-ref-2104)
* [NetApp ONTAP-SAN 20.07](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-class-refnetapp-san-ref)
* [OpenShift Data Foundation for local volumes](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-class-refocs-local-ref)
* [OpenShift Data Foundation for remote volumes](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-class-refocs-remote-ref)
* [IBM Spectrum Scale](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-class-refspec-scale-sc-ref)
* [IBM Systems object storage](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-class-refsat-storage-ibm-object-sc-ref)
* [IBM VPC block storage](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-class-refsat-storage-ibm-vpc-csi-sc-ref)
* [VMware Storage CSI Driver](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-class-refsat-storage-vmware-csi-sc-ref)









 Setting up Satellite as a Secure Gateway for on-prem solutions 

[Setting up Satellite as a Secure Gateway for on-prem solutions](https://cloud.ibm.com/docs/satellite?topic=satellite-sg-usecasesg-usecase)
"name": "Gross_margin",
"description": "Gross margin",
"label": "Gross margin",
"usage": "fact",
"regularAggregate": "minimum"
}
]
},
"label": "Module Name",
"identifier": "moduleId"
}
Show more









 Table section of the data source specification 

The final portion of the data source module specification, is the table field. In this section, the columns of the data source are described, along with their type information:

![tablesectionofdatasource](https://cloud.ibm.com/docs-content/v1/content/2781097afe16f2d329d7a606ddd260fb1a3e355c/services/cognos-dashboard-embedded/tablesectionofdatasource.jpg)



* name: An identifier for the column. The rules following for identifiers should be followed.
* label: The label that will appear in the metadata tree when the data source is added to a dashboard.
* description: The description of the column.
* nullable: Indicates whether values in this column can be null. Values: (true|false).
* usage: Values: (attribute|fact|identifier|automatic)
* datatype: Type of the data items in this column. Values: (INTEGER|NVARCHAR(n)|...). See the xsd for the full list of data types.
* regularAggregate: Specifies the aggregation type to be used for this column. Values: (total|average|maximum|...). See the xsd for the full list.
* taxonomyFamily: With the optional taxonomyFamily information, you can use specific type information to identify the nature of the field; such as geographical or timing information.
"f46eba57-f08e-4e38-a76c-f3370d457bd2"
]
}
]
}
Show more

--name
: The DNS hostname to associate with your load balancer.

--fallback-pool
: The pool ID to use when all other pools are detected as unhealthy.

--default-pools
: A list of pool IDs ordered by their failover priority.

--description
: The descriptive text of the load balancer.

--ttl
: Time to live (TTL) of the DNS entry for the IP address returned by this load balancer.

--az-pools
: A mapping of region and country codes to a list of pool IDs (ordered by their failover priority) for the region.

--enabled
: Whether the load balancer pool is enabled. Valid values: true, false.

-i, --instance
: Instance name or ID. If not set, the context instance specified by dns instance-target INSTANCE is used.

--output
: Specify output format. Currently, json is the only supported format.





 Examples 

Create a global load balancer in zone demo.com:31984fea73a15b45779fa0df4ef62f9b.

ibmcloud dns glb-create demo.com:31984fea73a15b45779fa0df4ef62f9b --json @glb.json -i "dns-demo"







 ibmcloud dns glb-update 

Update a global load balancer in a zone.

ibmcloud dns glb-update DNS_ZONE_ID GLB_ID (-j, --json @JSON_FILE | JSON_STRING) [-i, --instance INSTANCE] [--output FORMAT]
Creating schema 

You can create schema from the Data manager page by using the web console.



1.  Log in to IBM® watsonx.data console.
2.  Select Data manager from the navigation menu.
3.  Select the engine from the Engine menu. The catalogs that are associated with the selected engine are displayed.
4.  Click the Create drop-down and select Create schema.



1.  In the Create schema form, select the catalog and enter schema name.
2.  Click Create. The schema is created under the selected catalog.
Creating table from a file 

Files can also be ingested or imported to IBM® watsonx.data through the overflow menu of schema in the Data explorer page to create tables.



1.  Log in to the watsonx.data console.
2.  From the navigation menu, select Data manager.
3.  Select the engine from the Engine drop-down. Catalogs that are associated with the selected engine are listed.
4.  Select a schema under a catalog where you want to import a file to create table.
5.  Click the overflow menu of the selected schema and select Create table from a file. The Create table from a file page opens.
6.  Follow the steps in the [Creating tables](https://cloud.ibm.com/docs/watsonxdata?topic=watsonxdata-create_table) topic to complete importing the file.
Schemas 



  Creating schemas 



1.  Go to Databases.
2.  Select the database in which you want to create a schema.
3.  Click Create schema.
4.  Type a name for the schema.
If the name contains special characters, enclose it in double quotation marks. The dot character (".") is not supported.
5.  Specify the retention time interval (in days) for the schema.
6.  Click Create.







  Updating retention time interval (time travel) for schemas 



1.  Go to Databases.
2.  Select the database in which the schema that you want to alter is.
3.  From the overflow menu, click Update interval.
4.  Type a retention time interval.
You can select between 1 day and up to 99 days, or zero to alter a temporal schema to nontemporal.
For more information on retention time interval and time travel, see [Netezza Performance Server time travel](https://cloud.ibm.com/docs/netezza?topic=netezza-enablingdisabling_tt).
5.  Click Save.
create external table create table 

 <br><br> * Defines a placeholder for a table whose content is supplied at initialization time.<br><br><br> <br><br> * Requires that the content of the table is available at compile time.<br> * Serialized in the compiled representation (.tam) of a module.<br><br><br> 







 Examples 

Example 1: Creating an external table that is populated at load time

The external table, PersonNegativeClues, expects to be populated at load-time because of the flag, allow_empty false.

module PersonModuleFrench;

create external table PersonNegativeClues (name Text)
allow_empty false;

export table PersonNegativeClues;

Example 2: Creating a dictionary with an external table

Dictionaries can also be created from external tables, similar to being created from inline tables that are declared with the create table statement.

create external table Product (nickName Text, formalName Text)
allow_empty false;

/
* Dictionary of product nicknames, from the nickName field
* of the customizable external table Product.
/
create dictionary ProductDict
from table Product
with entries from nickName;





 Documenting the create external table statement with AQL Doc 

The AQL Doc comment for a create external table statement contains the following information:



* General description about the table.
* @field for every column name in the schema of this table.



/ Create a table that maps company names to locations of corporate headquarters.
* @field name name of the company
* @field location location of corporate headquarters
/
create external table Company2Location
(name Text, location Text)
allow_empty false;







 The create external view statement 

The create external view statement in AQL allows specification of more metadata about a document as a new view, in addition to the predefined Document view that holds the textual and label content.



 Syntax 

create external view <view_name> (
<colname> <type> [, <colname> <type>]
)
external_name '<view_external_name>';
Creating table 

You can generate, configure, and run DDL from the Data manager page by using the web console.



1.  Log in to IBM® watsonx.data console.
2.  From the navigation menu, select Data manager.
3.  Select the engine from the Engine menu. Catalogs that are associated with the selected engine are listed.
4.  Click Create and select Create table.
5.  In the Create table form, drag a file to the box or click to upload.

.CSV, .Parquet, .json, .txt are the supported data file formats. For .json file, you must enclose the content in [].
6.  Click the data type and choose the required data types for each column. Click Next.
7.  In the Target form, select the Engine, Catalog, and Schema in which the table is created.
8.  Enter a name for the table in the Table name field and click Next.
9.  Verify the details in the Summary page and scroll down to view the DDL preview.
10. Click Create.
11. Verify that the table creation status in the Result set is successful, indicated as true.
12. Go to the Data manager page and select the schema under which you created the table and click the refresh icon. The newly created table is listed.