```xml <result> <column_name>duration_ms</column_name> <family>additive</family> <subtype>intensive_additive</subtype> <confidence>0.85</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 durations across entities is meaningless), 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 "duration_ms" indicates an absolute time measurement (milliseconds), which is an intensive physical quantity. The center (mean=37.6, median=15.0) is far from both 0.0 and 1.0, and the presence of zeros (19.3%) argues against multiplicative. On a DIMENSION table, duration represents a property/attribute of each entity (e.g., song length, call duration), not an accumulating quantity - summing durations across different entities is meaningless, but averaging them is sensible. This is a classic intensive_additive measure: a level/intensity where mean is the natural rollup. </reasoning> <table_type_conflict>false</table_type_conflict> </result> ```