Compare products using known specifications

Author: AILesson7 min setupTested with:ChatGPTReviewed: 2026-08-28

Quick answer

Normalize supplied specifications, preserve missing data, and compare only against explicit needs. Provide: Requirements and comparison rules, Product facts and source labels, Use and decision context. Expected result: An evidence-linked product comparison with eligibility, trade-offs, unknowns, and verification steps.

Add your context

Your text stays in this browser. AILesson Prompts does not send it to a model or server.

Requirements and comparison rulesProduct facts and source labelsUse and decision context

Your prompt

Unfilled fields remain visible as placeholders, so you can still copy and edit the prompt

Compare the supplied products using only the stated requirements and provided evidence.

Hard requirements, preferences, units, scoring anchors, tie-breaks, and unknown-data treatment:
[criteria]

Candidate prices, specifications, terms, test results, source labels, and retrieval dates:
[products]

Location, cost treatment, compatibility, timing, decision owner, and consequential uncertainties:
[context]

Normalize units and terminology while retaining original values and source labels. Distinguish confirmed, claimed, inferred, conflicting, and missing data. Apply hard gates before scoring; do not treat missing evidence as a pass, convert currencies or calculate total cost without supplied rates, or fill absent specifications from memory. Avoid false precision when scoring anchors are incomplete. Return: normalized comparison table; gate result with evidence for each candidate; weighted comparison where supported; material trade-offs; conflicts and unknowns; sensitivity to close scores; verification checklist; and a conditional recommendation that states what new fact could change it.

Private by defaultPrompt assembly happens locally in your browser. Avoid placing confidential information into any AI service unless your organization allows it.

From input to outcome

A worked example

See how concrete context turns this recipe into a usable result

Actual input

Requirements and comparison rules: Portable monitor for travel. Gates: USB-C single-cable video with a supplied laptop; weight ≤ 900 g; price before tax ≤ USD 260; warranty ≥ 1 year. Preferences: brightness 30, weight 25, stand flexibility 20, warranty 15, price 10. Brightness anchors: 300 nits=1, 400=3, 500=5. Missing gate data = unverified, not pass. Tie-break lower weight.
Product facts and source labels: Aster View 14: USD 229; 1.65 lb; 400 nits claimed; USB-C DP Alt Mode; folding cover stand; 18-month warranty. Source A: manufacturer sheet, retrieved 2026-08-27. Brim Go 15: USD 249; 0.95 kg; 500 nits claimed; USB-C video, exact protocol not stated; kickstand; 2-year warranty. Source B: retailer page, 2026-08-27. Coda Air 14: USD 269; 780 g; 350 nits; USB-C DP Alt Mode; adjustable kickstand; warranty not listed. Source C: manufacturer page, 2026-08-27. Laptop supports USB-C DP Alt Mode but available port power output is not provided.
Use and decision context: Purchase in Oregon this week. Compare pre-tax listed price only; shipping unknown. One traveler decides. Single-cable compatibility must be verified with the laptop model because power may be insufficient.

Example output

Normalized gates: Aster weighs about 748 g (1.65 lb × 453.592), price USD 229, protocol stated, warranty 18 months—provisionally passes product-side gates, while laptop power remains unverified. Brim weighs 950 g and fails the 900 g gate; its USB-C protocol is also unverified. Coda weighs 780 g but fails the USD 260 price gate and has unverified warranty.

Only Aster remains eligible for conditional consideration. Its preference evidence is incomplete: brightness is a manufacturer claim, stand flexibility is described but not scored by a defined test, and shipping is unknown. A weighted total would create false precision because stand anchors and laptop compatibility evidence are missing. Material trade-off: Brim offers a claimed 500 nits and longer warranty but is ineligible on weight; Coda has the adjustable stand and low weight but is ineligible on price and unknown warranty.

Conditional recommendation: verify Aster with the exact laptop model for video plus adequate power over one cable, confirm delivered price, and test the cover stand at required angles. If it needs a second cable, it fails the primary gate and no supplied candidate qualifies. Also verify whether brightness figures use the same measurement method before relying on them.

Why this works

1
Source-labeled normalization enables like-for-like comparison without erasing where facts came from.
2
Gate-first evaluation stops attractive preferences from compensating for a failed requirement.

Check the result

Are original values, normalized values, status, and source retained for every material specification?
Were failed and unverified gates excluded from unconditional recommendations?
Does the recommendation identify close calls and facts that could reverse it?

Use it with confidence

Frequently asked questions

Practical answers about when to use this recipe, what to provide, and where human review still matters

What should I prepare before using “Compare products using known specifications”?

For “Compare products using known specifications,” prepare Requirements and comparison rules, Product facts and source labels, and Use and decision context. Replace placeholders only with information you can verify. If a detail is unknown, preserve that uncertainty explicitly instead of asking the model to infer it.

When is the “Compare products using known specifications” result not ready to use?

The result is not ready if it does not yet deliver the stated outcome—An evidence-linked product comparison with eligibility, trade-offs, unknowns, and verification steps—from the supplied evidence, or if it relies on unresolved assumptions, missing approvals, or invented details. Use the checks as release gates: revise the source inputs or assign a named, authorized reviewer instead of polishing an unsupported output.

Which AI tools have recorded tests for “Compare products using known specifications”?

The published test record for “Compare products using known specifications” lists ChatGPT as of 2026-08-28. This confirms recorded runs, not guaranteed compatibility or identical results in later product versions. For another tool or version, keep every constraint visible and repeat the result checks before use.

More ways to explore