This decision will dictate your UI going forward, so to some extent the answer to this question depends on the other data you'll need to represent.
For the sake of consistency, make sure to think about whether you can apply the option you choose here to any other multi-choice questions in your form.
However, just within the context of your question, and considering that you've already stated your preference against vanilla radio buttons in a comment above, here are my opinions:
This is a tab-style interface, and it benefits from familiarity and extensibility. In the future, if you have a series of options with more than two values, you can easily reuse this element, lending your UX some plus-points through consistency. This would be my choice from the options given.
This element is a switch, and it evokes an "on-off" impression. Traditionally, switches are not meant to function as radio buttons. I would recommend against this option simply because it goes against the interface language of many other apps out there, and doesn't offer any obvious benefits over the 1st option. You cannot extend this element to include non-boolean values, and you won't be able to use vanilla "on-off" switches in the future without causing dissonance.
This is the least recognisable element of the three, and it could use some tweaking, but it benefits from clear intent through the use of the arrow head.
If you planned to install this element frequently throughout your system (particularly for datasets with more than two values, or a directional element like "north-east-south-west") I'd say give it a go. Not my first choice, but sure.
However it really could use some more clarity. For example, am I supposed to tap on the text, or the arrow? If I'm supposed to tap on the text, what separates it visually from your body text? Should it be underlined, or perhaps outlined as a button?
In short, this dataset doesn't really justify anything complicated, so if radio buttons are off the cards I personally recommend option 1.