Lettuce and lettuce salads100 g vs 100 gTwo cited FDC records

Lettuce, salad with egg, cheese vs Lettuce, salad with egg, tomatoUSDA FDC 2709827 vs 2709826

A controlled equal-weight comparison of two exact USDA survey-food records, with source descriptions, representative amounts, listed formulation inputs, and interpretation limits kept visible.

Record A · FDC 2709827

Lettuce, salad with egg, cheese, tomato, and/or carrots, with or without other vegetables, no dressing

Check this record in FoodData Central ↗

Record B · FDC 2709826

Lettuce, salad with egg, tomato, and/or carrots, with or without other vegetables, no dressing

Check this record in FoodData Central ↗

Equal-weight evidence

Nutrition per 100 grams

Both columns use the same mass, which compares nutrient concentration without allowing the two representative source amounts to change the denominator. “A +” or “B +” reports the arithmetic difference between the cited values; it is not a quality score.

Per-100-gram nutrient comparison for Lettuce, salad with egg, cheese, tomato, and/or carrots, with or without other vegetables, no dressing and Lettuce, salad with egg, tomato, and/or carrots, with or without other vegetables, no dressing
NutrientA · Lettuce, salad with egg, cheese, tomatoB · Lettuce, salad with egg, tomato, or carrotsDifference
CaloriesMaterial under the publication gate 71 kcal 50 kcal A +21 kcal
Protein 4.2 g 3.4 g A +0.8 g
Total fatMaterial under the publication gate 4.4 g 2.3 g A +2.1 g
Carbohydrate 3.7 g 3.9 g B +0.2 g
Dietary fiber 1.2 g 1.2 g Same reported value
Total sugars 1.6 g 1.7 g B +0.1 g
Sodium 106 mg 56 mg A +50 mg
Saturated fatMaterial under the publication gate 2.1 g 0.7 g A +1.4 g
Potassium 239 mg 242 mg B +3 mg
Calcium 93 mg 35 mg A +58 mg
Iron 0.4 mg 0.5 mg B +0.1 mg

Values come from the two cited USDA FoodData Central Survey Foods records. Feast does not average records, impute missing values, or infer a nutrient from the food name.

Calories difference

21 kcal per 100 g

Lettuce, salad with egg, cheese, tomato, or carrots reports 21 kcal more calories per 100 grams than Lettuce, salad with egg, tomato, or carrots, with (71 versus 50 kcal).

The absolute difference is 30% of the larger reported value. That percentage describes these two records only; it is not an estimate of biological effect or expected variation.

Total fat difference

2.1 g per 100 g

Lettuce, salad with egg, cheese, tomato, or carrots reports 2.1 g more total fat per 100 grams than Lettuce, salad with egg, tomato, or carrots, with (4.4 versus 2.3 g).

The absolute difference is 47% of the larger reported value. That percentage describes these two records only; it is not an estimate of biological effect or expected variation.

What differs in the source descriptions

The exact names carry information the numbers cannot.

USDA assigns both records to “Lettuce and lettuce salads,” but the topic label is broad. Record A is “Lettuce, salad with egg, cheese, tomato, and/or carrots, with or without other vegetables, no dressing.” Record B is “Lettuce, salad with egg, tomato, and/or carrots, with or without other vegetables, no dressing.” Feast paired them because their contrast-neutral food identities are closely related (90% token overlap after controlled modifiers are set aside), not merely because they share a generic category.

No controlled preparation phrase is needed to explain this pairing. The close source names instead differ in narrow food or ingredient terms. Record A has the distinctive neutral terms cheese; Record B has the corresponding terms shown in its exact name. Read the full descriptions before selecting either profile.

Even a clean name contrast can carry hidden companions. A fried record may also include coating; a restaurant record can use a different recipe; a reduced-sodium description can differ in more than salt; and a source amount can reflect a different reporting convention. That is why this page reports the complete pair rather than treating one word as an intervention.

Portion context

A representative source amount is not a shared “serving.”

Record A uses Typical reported amount at 79 g. Record B uses Typical reported amount at 88 g. Those labels and gram weights come from their respective records. They are useful for scaling the chosen profile, but they are not recommendations and need not describe equal amounts.

The representative amounts do not cross Feast’s material portion-difference threshold of both 15 grams and 20%. They are still separate source measures, so the 100-gram table remains the appropriate place for an equal-weight comparison.

A cup, piece, slice, sandwich, fillet, or fluid ounce can have different gram weights across records. A matching label is not enough: check the listed grams. If accuracy matters more than convenience, weighing the food or using a current package label can be more specific than a generic survey-food measure.

Record A measures

  • 1 garden salad236 g
  • 1 side salad168 g
  • 1 cup79 g
  • Quantity not specified79 g
Scale record A →

USDA source formulation evidence

The listed inputs provide another way to audit the match.

FNDDS includes input-food rows behind each standardized survey-food record. Record A’s leading listed inputs include Mixed salad greens, raw, Tomatoes, red, ripe, raw, year round average, Egg, whole, cooked, hard-boiled, Celery, raw. Record B’s include Mixed salad greens, raw, Egg, whole, cooked, hard-boiled, Tomatoes, red, ripe, raw, year round average, Carrots, mature, raw. Ingredient-code overlap is 67%, and normalized listed-input-weight variation is 23%.

Record A · 8 input rows

Lettuce, salad with egg, cheese, tomato, or carrots

  1. Mixed salad greens, rawIngredient code 75114000
    34.9% of listed input weight
  2. Tomatoes, red, ripe, raw, year round averageIngredient code 11529
    14.3% of listed input weight
  3. Egg, whole, cooked, hard-boiledIngredient code 1129
    10.8% of listed input weight
  4. Celery, rawIngredient code 11143
    9.5% of listed input weight
  5. Cheese, cheddarIngredient code 1009
    9% of listed input weight
  6. Carrots, mature, rawIngredient code 11124
    8.7% of listed input weight
  7. Cucumber, with peel, rawIngredient code 11205
    8.2% of listed input weight
  8. Radishes, rawIngredient code 11429
    4.6% of listed input weight

Record B · 7 input rows

Lettuce, salad with egg, tomato, or carrots, with

  1. Mixed salad greens, rawIngredient code 75114000
    41.6% of listed input weight
  2. Egg, whole, cooked, hard-boiledIngredient code 1129
    20.2% of listed input weight
  3. Tomatoes, red, ripe, raw, year round averageIngredient code 11529
    10.7% of listed input weight
  4. Carrots, mature, rawIngredient code 11124
    7.3% of listed input weight
  5. Celery, rawIngredient code 11143
    7.1% of listed input weight
  6. Onions, rawIngredient code 11282
    6.8% of listed input weight
  7. Cucumber, with peel, rawIngredient code 11205
    6.2% of listed input weight

6 shared coded inputs

The largest shared entries include Mixed salad greens, raw, Egg, whole, cooked, hard-boiled, Tomatoes, red, ripe, raw, year round average, Celery, raw, Carrots, mature, raw. Shared codes can still carry different listed weights.

2 A-only and 1 B-only coded inputs

A-only entries include Cheese, cheddar, Radishes, raw. B-only entries include Onions, raw.

Important: these weights belong to USDA’s source formulation. Their percentages are shares of the listed input weight, not a reconstructed plate, final cooked yield, visitor serving, ingredient declaration, or estimate of what is visible in a photo.

Choosing the closer record

Match context first; scale second.

  1. 01

    Read both names literally

    Compare cooking method, coating, edible skin or peel, sauce, additions, venue, source form, and food subtype. For this pair, the full A and B descriptions above are the evidence—not shortened search labels.

  2. 02

    Use listed inputs as a check

    If the name still leaves ambiguity, compare the leading and unique source inputs. They can reveal that two near names refer to meaningfully different standardized formulations, but they do not reconstruct your dish.

  3. 03

    Choose an amount for that record

    After choosing A or B, use its own named measure and gram weight. Do not transfer a cup, slice, or “typical amount” from the other record as if the measures were interchangeable.

  4. 04

    Account for missing details

    Brand, current restaurant recipe, cooking oil, drained weight, toppings, substitutions, and unfinished portions may not be captured. A label or weighed recipe can supersede a generic reference when it better matches the actual food.

Limits and responsible interpretation

This is a comparison of records, not a causal study.

The two records come from 2021–2023 FoodData Central Survey Foods data. The nutrient table faithfully compares their published values on the same weight basis. It does not measure two plates prepared at the same time, isolate one ingredient, or estimate the uncertainty around either value.

Several details can change together. Moisture affects concentration per 100 grams. Coating or sauce can add carbohydrate and sodium. Edible skin or fat changes the portion represented. Restaurant, school, frozen, canned, fresh, home-recipe, and ready-to-heat records may use distinct standardized formulations. The source descriptions and input lists help show those differences, but they cannot assign cause.

A higher or lower number is not an overall verdict. Protein, fiber, sodium, energy, fat, micronutrients, preferences, allergies, budget, portion, and an individual’s goals answer different questions. Feast therefore reports directions and magnitudes without applying a universal “healthier” label.

This page is educational and does not diagnose a condition, prescribe a target, or replace advice from a qualified professional. For an allergy, medically directed diet, or strict ingredient limit, use verified ingredient information and guidance appropriate to that situation.

How this page qualified

A page is published only when the pair clears materiality and diversity gates.

Both records must occupy the same USDA survey-food topic and share a close food identity after a controlled vocabulary separates preparation, edible-part, source, claim, crust, and sauce wording. Exact contrast-neutral identities receive priority. Close ingredient or form substitutions can qualify when name overlap remains high and the numerical evidence is material.

For primary nutrients, Feast requires both an absolute and relative difference: at least 20 kcal and 12% for energy; 2 g and 18% for protein or fat; 5 g and 15% for carbohydrate; 1 g and 20% for fiber; 4 g and 20% for sugars; or 100 mg and 20% for sodium. A focused one-nutrient pair also needs a material representative-amount or formulation distinction. Rounding-only pairs are not published.

Unordered FDC IDs define a canonical pair, so reversing A and B cannot create another page. Each source record can appear twice at most, each USDA topic contributes no more than 40 pages, and closely repeated identity families are capped. Those rules produced a selective comparison library rather than every mathematical combination in the corpus.

Read the complete nutrition-page methodology for import, nutrient mapping, portion scaling, Daily Value, and uncertainty rules.