```xml <result> <column_name>salary_usd</column_name> <family>additive</family> <subtype>intensive_additive</subtype> <confidence>0.92</confidence> <requires_user_confirmation>false</requires_user_confirmation> <sum_meaningful>false</sum_meaningful> <signed>false</signed> <reducers> <primary_reducer>mean</primary_reducer> <valid_reducers>mean, min, max, median, distribution</valid_reducers> <excluded_reducers>sum (summing salaries across entities is meaningless for a dimension table), product (not a ratio)</excluded_reducers> <average_semantics>arithmetic_mean</average_semantics> </reducers> <inner_outer_measure> <inner_measure_reducer>min</inner_measure_reducer> <outer_measure_reducer>max</outer_measure_reducer> </inner_outer_measure> <multiplicative_partner_derivable>false</multiplicative_partner_derivable> <reasoning> Table-type gate: DIMENSION with no sequence axis makes multiplicative highly implausible. Column name "salary_usd" indicates an absolute currency amount (additive family). The range [32K-399K] with high distinctness and center far from both 0 and 1 confirms additive. Subtype is intensive_additive because this is a DIMENSION table representing a level/attribute per entity (one row per entity); summing salaries across different entities in a dimension table is meaningless—only averaging, min, max make sense for rollup. On a transactional PATH table, salary payments would be real_additive (summable), but here it's a static attribute level. </reasoning> <table_type_conflict>false</table_type_conflict> </result> ```