lesson 3 of 3 · every prediction gets a nameevery prediction gets a nameevery prediction gets a namelesson 3 of 3 · every prediction gets a nameevery prediction gets a nameevery prediction gets a namelesson 3 of 3 · every prediction gets a nameevery prediction gets a nameevery prediction gets a namelesson 3 of 3 · every prediction gets a nameevery prediction gets a nameevery prediction gets a namelesson 3 of 3 · every prediction gets a nameevery prediction gets a nameevery prediction gets a namelesson 3 of 3 · every prediction gets a nameevery prediction gets a nameevery prediction gets a namelesson 3 of 3 · every prediction gets a nameevery prediction gets a nameevery prediction gets a namelesson 3 of 3 · every prediction gets a nameevery prediction gets a nameevery prediction gets a namelesson 3 of 3 · every prediction gets a nameevery prediction gets a nameevery prediction gets a namelesson 3 of 3 · every prediction gets a nameevery prediction gets a nameevery prediction gets a namelesson 3 of 3 · every prediction gets a nameevery prediction gets a nameevery prediction gets a name
A support ticket arrives carrying a prediction ID. To answer it, you build an index of the log — one dict, keyed by the field that names each prediction — and look the complaint up in it.
Fill in the key the index should be built on (a quoted string).
Expected output:
churn-clf-v14 said will_stay