From 2ae6df32aa6b4094043bd5f48f78fadce00f506f Mon Sep 17 00:00:00 2001 From: Dennis Hume Date: Thu, 23 Jan 2025 05:08:00 -0600 Subject: [PATCH] Additional PR edits --- .../category-two/prompt-engineering/custom-resource.md | 2 +- .../docs/tutorials/category-two/prompt-engineering/index.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/docs-beta/docs/tutorials/category-two/prompt-engineering/custom-resource.md b/docs/docs-beta/docs/tutorials/category-two/prompt-engineering/custom-resource.md index 840030248f848..be3920236cf83 100644 --- a/docs/docs-beta/docs/tutorials/category-two/prompt-engineering/custom-resource.md +++ b/docs/docs-beta/docs/tutorials/category-two/prompt-engineering/custom-resource.md @@ -6,7 +6,7 @@ last_update: sidebar_position: 40 --- -With an output in our desired schema, we can use the NREL API to lookup nearby alternative fuel stations. The NREL API is a standard REST API. In Dagster, we will create a resource with a single method to retrieve fuel stations. This method (`alt_fuel_stations`) will take in the three parameters from our prompt engineering asset (latitude, longitude, and fuel type). +With an output in our desired schema, we can use the [NREL](https://www.nrel.gov/) API to lookup nearby alternative fuel stations. The NREL API is a standard REST API. In Dagster, we will create a resource with a single method to retrieve fuel stations. This method (`alt_fuel_stations`) will take in the three parameters from our prompt engineering asset (latitude, longitude, and fuel type). Now we can use our custom resource in another asset (`nearest_fuel_station`) and query the API. The [reponse of the API](https://developer.nrel.gov/docs/transportation/alt-fuel-stations-v1/nearest/#fuel-station-record-fields) gives some very rich data about these fuel stations. One field that would be particularly interesting for the user is `access_days_time` which shows when the fuel station is open. diff --git a/docs/docs-beta/docs/tutorials/category-two/prompt-engineering/index.md b/docs/docs-beta/docs/tutorials/category-two/prompt-engineering/index.md index 7f14f79cd1cea..2ddd225b0f44d 100644 --- a/docs/docs-beta/docs/tutorials/category-two/prompt-engineering/index.md +++ b/docs/docs-beta/docs/tutorials/category-two/prompt-engineering/index.md @@ -10,7 +10,7 @@ sidebar_position: 10 In this tutorial, you'll build a pipeline with Dagster that: - Takes an input question -- Generates prompts to use with Anthropic +- Generates prompts to use with [Anthropic](https://www.anthropic.com/) - Validates outputs of AI models and passes outputs across assets
@@ -27,7 +27,7 @@ To follow the steps in this guide, you'll need: First, set up a new Dagster project. -1. Within the Dagster repo, navigate to the project: +1. Clone the the [Dagster repo](https://github.com/dagster-io/dagster) and navigate to the project: ```bash cd examples/project_prompt_eng