Upload README.md with huggingface_hub

README.md

@@ -74,7 +74,7 @@ The examples have the following structure per configuration:
 {
     "anchor": "a Validator is such an example.\n\nRelated concepts:the Artifact Store is a type of Stack Component that needs to be registered as part of your ZenML Stack.\n\nthe objects circulated through your pipelines are serialized and stored in the Artifact Store using Materializers. Materializers implement the logic required to serialize and deserialize the artifact contents and to store them and retrieve their contents to/from the Artifact Store.\n\nWhen to use it\n\nThe Artifact Store is a mandatory component in the ZenML stack. It is used to store all artifacts produced by pipeline runs, and you are required to configure it in all of your stacks.\n\nArtifact Store Flavors\n\nOut of the box, ZenML comes with a local artifact store already part of the default stack that stores artifacts on your local filesystem. Additional Artifact Stores are provided by integrations:\n\nArtifact Store Flavor Integration URI Schema(s) Notes Local local built-in None This is the default Artifact Store. It stores artifacts on your local filesystem. Should be used only for running ZenML locally. Amazon S3 s3 s3 s3:// Uses AWS S3 as an object store backend Google Cloud Storage gcp gcp gs:// Uses Google Cloud Storage as an object store backend Azure azure azure abfs:// , az:// Uses Azure Blob Storage as an object store backend Custom Implementation custom custom Extend the Artifact Store abstraction and provide your own implementation\n\nIf you would like to see the available flavors of Artifact Stores, you can use the command:\n\nzenml artifact-store flavor list\n\nEvery Artifact Store has a path attribute that must be configured when it is registered with ZenML. This is a URI pointing to the root path where all objects are stored in the Artifact Store. It must use a URI schema that is supported by the Artifact Store flavor. For example, the S3 Artifact Store will need a URI that contains the s3:// schema:\n\nzenml artifact-store register s3_store -f s3 --path s3://my_bucket\n\nHow to use it",
     "distilabel_metadata": {
-        "raw_output_generate_sentence_pair_0": "## Positive\n\nWhat is an example of a Validator in the context of ZenML?\n\n## Negative\n\nHow do I bake a cake using a conventional oven?"
+        "raw_output_generate_sentence_pair_0": "## Positive\n\nWhat is an example of a Validator in the ZenML documentation?\n\n## Negative\n\nHow can I implement a custom Artifact Store in AWS?"
     },
     "embedding": [
         -0.019603008404374123,
@@ -465,9 +465,9 @@ The examples have the following structure per configuration:
     "filename": "https://docs.zenml.io/stack-components/artifact-stores",
     "generated_questions": null,
     "model_name": "gpt-4o",
-    "negative": "How do I bake a cake using a conventional oven?",
+    "negative": "How can I implement a custom Artifact Store in AWS?",
     "parent_section": "stack-components",
-    "positive": "What is an example of a Validator in the context of ZenML?",
+    "positive": "What is an example of a Validator in the ZenML documentation?",
     "token_count": 393,
     "url": "https://docs.zenml.io/stack-components/artifact-stores"
 }