Corrections
You will disagree with some answers. Typing over one is expected, and the table is built so that doing it does not cost you the record of what was originally extracted.
Type over the cell
Any cell can be overridden by typing a new value into it. From that point on the table shows yours: the grid displays it, and an export carries it rather than the model’s answer.
What does not happen is a delete. The extracted value stays underneath, with its citations, and the change is recorded — so a table can always answer three questions at once: what the model said, what a person changed it to, and when. That is the difference between a corrected table and an edited one, and it is the property that makes a table worth handing to someone else.
An override is a decision, and it sticks
Overrides survive the things that unsettle extracted answers:
- Staleness does not touch them. Editing a column’s prompt marks its extracted answers stale, but a cell you typed stays as you left it — you made that call about this document, and a change to the question does not unmake it.
- They drop out of triage. An overridden cell is no longer counted as low confidence, because it has been checked by a person by definition.
- They come across when you duplicate a table. Copying rows copies their values, citations and overrides.
If you want the model’s answer back, you do not have to rerun anything. Select the cells and press delete on the selection toolbar: while anything in the selection is still overridden, that first press removes the override only, and the extracted answer comes back with its citations intact. It costs nothing, because the answer was never deleted — it has been underneath yours the whole time.
Press it again, with nothing left overridden, and it clears the cells for real: the value, its citations and its confidence go together. That is the honest behaviour for a cell you no longer believe — a cleared cell has no answer rather than a stale one pretending to be current — and it is the point at which rerunning becomes the way to get an answer back.
Right-clicking a cell offers Clear, which is the full version in one press: it takes the value, the citations and any correction together, and the confirmation says so. Use the toolbar when what you want is your correction gone; use the menu when what you want is the cell empty.
One exception: image cells
An image column answers with a picture, and what you type over it is text. So overriding an image cell replaces the picture with your words, and the cell reads as text from then on — there is no way to pick a different region by hand.
That makes an override a heavier decision on an image column than on a text one, and usually the wrong tool. If the column keeps finding the wrong picture, the prompt is what to change. If one document is simply the exception, clearing the cell leaves an honest blank; typing “see p.14” over it loses the thing the column was for. As everywhere else, the extracted answer and its citation are kept underneath, so nothing is destroyed either way.
When to override, and when to fix the column
Override when the document is unusual — the one lease that words its break clause backwards, the contract with a handwritten amendment. That is a per-document judgement and nothing about the column would improve it.
Do not override your way out of a bad column. If you are correcting the same kind of error across many rows, the prompt is asking the wrong question or the output type is wrong, and fixing that is cheaper than typing forty cells — and it holds for the documents you have not uploaded yet. See columns.
A rough rule: two or three overrides in a column is review; ten is a column problem.