```xml <result> <column_name>query_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 query 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 "query_ms" indicates a duration measurement (milliseconds), which is an intensive physical quantity - a level/intensity at a point, not an accumulating extensive quantity. Values are strictly positive, centered away from both 0 and 1 (mean=3.52, median=1.19), with no zeros. Summing query times across different entities is meaningless (you cannot add "3ms for entity A" to "9ms for entity B" to get a meaningful 12ms); averaging is the natural aggregation. This is a classic intensive_additive measure. </reasoning> <table_type_conflict>false</table_type_conflict> </result> ```