@Jonas @thiemowmde I've added example properties to the task description (two for each entity type). After doing that I realized that both this ticket and T165579 have actually been already mentioning an example (respectively "Antonym" and "Rhymes with").

@Jonas, can you please link the tickets and restore the text you deleted and that is not in any of the sub-tasks? Never mind, I restored it.

I take it the translation from/to item datatype (Q11 ⇔ L5-F11) mentioned in the task breakdown was just for the prototype, and now no longer applies? Or am I misunderstanding something?

good catch @Lucas_Werkmeister_WMDE. Whatever would be said about the task description, this part is clearly not relevant. Editing.

Uses labels from items by turning L5-F11 into Q11.
[…] except that it does return a value where the item ID is translated to a form/sense ID (Q11 becomes L5-F11).

These two sentences have been written for an absolute baseline prototype with a suggester for forms and senses that is almost entirely fake. This fake suggester does not search for forms or senses (these are not even indexed in the database), but it searches for items. All it does is displaying an ID that looks like a form or sense ID. Thats why the fake translates Q11 into L5-F11, and the other way around.

I'm not sure the task breakdown does make sense any more if all you did is removing these sentences. You might as well remove it entirely, or create the necessary subtasks for indexing forms and senses in the wb_terms table, the CirrusSearch index, and possibly other secondary tables that are also required to make the described datatype work as expected.