String beans100 g vs 100 gTwo cited FDC records

Green beans, canned, reduced sodium vs Green beans, fresh, cooked, no addedUSDA FDC 2709865 vs 2709852

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 2709865

Green beans, canned, reduced sodium, cooked, no added fat

Check this record in FoodData Central ↗

Record B · FDC 2709852

Green beans, fresh, cooked, no added fat

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 Green beans, canned, reduced sodium, cooked, no added fat and Green beans, fresh, cooked, no added fat
NutrientA · Green beans, canned, reduced sodium, cookedB · Green beans, fresh, cooked, no added fatDifference
CaloriesMaterial under the publication gate 22 kcal 42 kcal B +20 kcal
Protein 1.1 g 2.1 g B +0.9 g
Total fat 0.5 g 0.3 g A +0.2 g
Carbohydrate 4.3 g 7.7 g B +3.4 g
Dietary fiberMaterial under the publication gate 1.9 g 3.1 g B +1.2 g
Total sugars 0.8 g 2.4 g B +1.6 g
SodiumMaterial under the publication gate 2 mg 121 mg B +119 mg
Saturated fat 0.1 g 0.1 g A +0.1 g
PotassiumMaterial under the publication gate 96 mg 301 mg B +205 mg
Calcium 38 mg 42 mg B +4 mg
Iron 1.1 mg 0.7 mg A +0.4 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

20 kcal per 100 g

Green beans, fresh, cooked, no added fat reports 20 kcal more calories per 100 grams than Green beans, canned, reduced sodium, cooked, no added (42 versus 22 kcal).

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

Dietary fiber difference

1.2 g per 100 g

Green beans, fresh, cooked, no added fat reports 1.2 g more dietary fiber per 100 grams than Green beans, canned, reduced sodium, cooked, no added (3.1 versus 1.9 g).

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

Sodium difference

119 mg per 100 g

Green beans, fresh, cooked, no added fat reports 119 mg more sodium per 100 grams than Green beans, canned, reduced sodium, cooked, no added (121 versus 2 mg).

The absolute difference is 98% 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 “String beans,” but the topic label is broad. Record A is “Green beans, canned, reduced sodium, cooked, no added fat.” Record B is “Green beans, fresh, cooked, no added fat.” Feast paired them because their contrast-neutral food identities are an exact match, not merely because they share a generic category.

The controlled name parser found 2 interpretable distinctions. These labels organize wording already present in the names; they do not establish that a distinction caused a nutrient difference.

Controlled wording distinctions
Description dimensionRecord ARecord B
Source formcannedfresh
Sodium wordingreduced- or low-sodium wordingNo matching controlled term in the source name

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 70 g. Record B uses Typical reported amount at 70 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 cup140 g
  • 1 cut piece2 g
  • 1 bean6 g
  • Quantity not specified70 g
Scale record A →

Record B measures

  • 1 cup140 g
  • 1 cut piece2 g
  • 1 bean6 g
  • Quantity not specified70 g
Scale record B →

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 Beans, snap, green, canned, no salt added, drained solids. Record B’s include Beans, snap, green, raw, Salt, table. Ingredient-code overlap is 0%, and normalized listed-input-weight variation is 100%.

Record A · 1 input rows

Green beans, canned, reduced sodium, cooked, no added fat

  1. Beans, snap, green, canned, no salt added, drained solidsIngredient code 11729
    100% of listed input weight

Record B · 2 input rows

Green beans, fresh, cooked, no added fat

  1. Beans, snap, green, rawIngredient code 11052
    99.7% of listed input weight
  2. Salt, tableIngredient code 2047
    0.3% of listed input weight

0 shared coded inputs

The two listed formulations do not share an ingredient code in this source extract. Shared codes can still carry different listed weights.

1 A-only and 2 B-only coded inputs

A-only entries include Beans, snap, green, canned, no salt added, drained solids. B-only entries include Beans, snap, green, raw, Salt, table.

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.