```xml <result> <column_name>elapsed_ms</column_name> <family>additive</family> <subtype>ordinal_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, last, distribution</valid_reducers> <excluded_reducers>sum (summing elapsed times across sequence steps 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> Gate prior: PATH table with sequence axis allows both multiplicative and ordinal_additive. Column name "elapsed_ms" indicates a duration measurement (milliseconds), which is an absolute physical quantity. The large magnitude (mean ~47K, max ~289K), strictly positive values, and center far from 1.0 rule out multiplicative. This is a duration/time measurement at each sequence step - summing elapsed times across timestamps is meaningless (you don't add "how long step 1 took" to "how long step 2 took"), but averaging across entities at a fixed step is valid. Classified as ordinal_additive rather than intensive_additive because elapsed time is extensive within an entity's step, just not summable along the sequence axis. </reasoning> <table_type_conflict>false</table_type_conflict> </result> ```