<result> <column_name>vA%</column_name> <family>multiplicative</family> <subtype>ratio_multiplicative</subtype> <confidence>0.5</confidence> <requires_user_confirmation>true</requires_user_confirmation> <sum_meaningful>false</sum_meaningful> <signed>false</signed> <reducers> <primary_reducer>product</primary_reducer> <valid_reducers>product, geomean, min, max</valid_reducers> <excluded_reducers>sum (meaningless for ratios), arithmetic_mean (wrong average for ratios)</excluded_reducers> <average_semantics>geometric_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> The table is PATH with a Date sequence axis, so a multiplicative measure is plausible. The '%' in the column name and the '%' suffix on every sample value (0.0%, 0.4%, 0.5%) are the only evidence, and they point to a rate or percent-change measure. The column is VARCHAR with a '-' placeholder, so all numeric statistics are null. That rules out center-of-mass, log-symmetry and reconstruction checks, and nothing in the data confirms or contradicts the naming signal. The small values near 0% could be a percent change (compounding as 1+x) or a share or level, so confidence is low. The column must be parsed to numeric, with '-' treated as null, and a human should confirm before it is used. </reasoning> <table_type_conflict>false</table_type_conflict> </result>