Ah yes, that's the expected output of review: it will show you all available versions and then one editable example at the top. The different version are shown separately and greyed out, so you can compare them. What exactly were you looking for in terms of visualisation? It can sometimes be difficult to visualise conflicting annotations in the same example, because they may obverlap.
If you want to see both annotations together in one example with potential overlaps, one alternative approach could be to use the new spans_manual UI introduced in the upcoming version (currently available as a nightly prerelease): ✨ Prodigy nightly: spaCy v3 support, UI for overlapping spans & more
In that case, you could create a single example with different labels for each input source (model, data), e.g. ORG_MODEL and ORG_DATA etc. Those spans would then all be highlighted in the same UI, and you could use different colours for them in your theme so you can tell them apart. And you could then use regular labels like ORG to add your own annotations, if they differ. At the end, you'd just need a postprocess that normalises all the final labels so they're all ORG, e.g. via a before_db callback. This could potentially be a nice built-in workflow as well – I'll try this out!