SQL query generator from a plain-English request
Converts a natural-language data requirement plus a table schema into a syntactically correct SQL query for a named database, with its assumptions stated up front.
Label supplied comments consistently while preserving mixed opinions, unclear cases and the exact words supporting each label.
No public result for version 1 yet
Version 1 · 2 variables · 2 required
Fill in the values below — the customized prompt updates as you type. marks a required value.
Comments with stable IDs and any necessary context. Default: Illustrative comments: C1: Reports load quickly now. C2: The charts are useful, but exporting still fails. C3: Well, that was something. C4: Where is the download button?
Target subject, allowed labels and operational definitions. Default: Target: reporting product experience. Labels: positive, negative, mixed, neutral, unclear. Questions without an expressed evaluation are neutral unless context says otherwise.
Classify sentiment in these comments.
Text records with IDs: Illustrative comments: C1: Reports load quickly now. C2: The charts are useful, but exporting still fails. C3: Well, that was something. C4: Where is the download button?
Subject and labeling rules: Target: reporting product experience. Labels: positive, negative, mixed, neutral, unclear. Questions without an expressed evaluation are neutral unless context says otherwise.
Assign each record one permitted label based only on its expressed opinion about the target subject. Give a short evidence excerpt and concise rationale. Preserve mixed sentiment and use an unclear label where context, sarcasm or an unstated target prevents a defensible assignment.
Do not infer a person's hidden emotional state, diagnosis, demographics or intent. Keep topic/aspect separate from sentiment, and flag comments that discuss more than one aspect.
Summarize label counts with the supplied-record denominator and list ambiguous records for human review. Do not treat this sample as population opinion, manufacture confidence probabilities or claim a validated classifier.No public examples yet for version 1
Curated prompt only. No example output or model test is attached; model compatibility has not been verified. Default inputs are illustrative practice material; replace them with your own facts and context.
Reports go to moderators and are never shown publicly.
Converts a natural-language data requirement plus a table schema into a syntactically correct SQL query for a named database, with its assumptions stated up front.
No public results yet
Check join cardinality and aggregation grain to explain duplicate rows or double-counted measures before changing a reporting query.
No public results yet
Specify temporal evaluation, leakage checks, baselines and business-relevant metrics before judging a forecasting model.
No public results yet
Review a chart's scales, labels, aggregation and claims, separating visual issues from data questions that need verification.
No public results yet
Produce a deterministic transformation from repeated measure columns to tidy rows with explicit keys, types and missing-value rules.
No public results yet
Specify cohort membership, return behavior and observation maturity so retention percentages remain comparable.
Oldest first · one level of replies
Sign in to join the discussion. Share what you learned or made with this prompt.
No comments yet
Be the first to share how this prompt worked for you.