A context engineer operates a finance Q&A agent on Databricks. The agent invokes a Genie space backed by tables in the finance.silver schema, and Genie selects which table to query for each user question by reading Unity Catalog table and column metadata. Two tables exist in the schema: revenue and revenue_gross. MLflow evaluation runs show the Correctness scorer flagging frequent failures where Genie queries revenue_gross when the user asks about net revenue, and queries revenue when the user asks about gross figures. Both tables are in active production use and must remain available to the Genie space, and the same disambiguation should be usable by other Genie spaces and BI consumers building against the same schema. Which intervention resolves the failure?