```xml <result> <column_name>output_tokens</column_name> <family>additive</family> <subtype>ordinal_additive</subtype> <confidence>0.85</confidence> <requires_user_confirmation>false</requires_user_confirmation> <sum_meaningful>true</sum_meaningful> <signed>false</signed> <reducers> <primary_reducer>sum</primary_reducer> <valid_reducers>sum, mean, min, max, median, count, distribution</valid_reducers> <excluded_reducers>product (not a ratio), geomean (not a ratio)</excluded_reducers> <average_semantics>arithmetic_mean</average_semantics> </reducers> <inner_outer_measure> <inner_measure_reducer>sum</inner_measure_reducer> <outer_measure_reducer>sum</outer_measure_reducer> </inner_outer_measure> <multiplicative_partner_derivable>true</multiplicative_partner_derivable> <reasoning> Gate prior: PATH table with sequence axis allows both multiplicative and ordinal_additive. Column name "output_tokens" is a count/quantity token (real_additive signal), but on a PATH table instantaneous counts are ordinal_additive. Center of mass (mean=422, median=268, max=7159) shows large unbounded magnitude far from 1.0, ruling out multiplicative. Contains 22.7% zeros, against multiplicative. The column represents an instantaneous rate/count at each sequence step (tokens output per event), not a cumulative total - summing across entities at a fixed timestamp is meaningful, but summing along the sequence would be inappropriate without normalization. Classification: ordinal_additive with cross-entity sum as primary reducer. </reasoning> <table_type_conflict>false</table_type_conflict> </result> ```