Skip to main content
Two run ids, because preference annotation asks which of A and B is better. The walkthrough is collecting preference annotations.

Worked examples

pull takes the Argilla dataset name as its argument; --into names the platform dataset the preferences land in, as a new version. Without --into it only prints the statistics. Start with tp annotate status. Everything else fails confusingly on a deployment with no Argilla instance wired up.

tp annotate

Manage preference annotation

tp annotate pull

Pull annotations back as a dataset

tp annotate push

Send answers out for annotation

tp annotate status

Check the Argilla integration
No options beyond --help.