There are several ways that can be used and in this case virtually any solution is feasible. You did not give more details or requirements. It is not easy to answer this primarily without incurring opinions that do not help at all.

SQLite

So trying to be objective I say that I would use SQLite yes. Not because it is the best solution, I do not know if it would be in this case. But because it works well today and will probably work well in the future and because there is probably no counterindicator to avoid SQLite.

Of course, if your requirement is to have something very small, you need to save each , I would avoid the database. But it consumes very little memory, it is rarely important to have that savings.

Raw file

Maybe you do not need it, maybe a more basic file will suffice. Manipulating a raw file may seem very simple but it can also bring unexpected complications especially if you want to evolve the application in the future. Creating a format can be tricky, and incredible how it looks even if the format is as simple as having lines (simpler than CSV format) if you're familiar with the database and not with file manipulation, the easiest is to that you already know. One of the reasons SQLite was created is for people not to have to deal with raw files.

Internal data list in the application

And if the application is never updated perhaps it would be the case even to put the phrases in a list in the application. But I would not think of it even if the idea is this because you can change your mind in the future.

Conclusion

First choose the easiest, most powerful and flexible then you think if you need to optimize. SQLite seems to be a cannon to kill bird. But I do not see any real disadvantage in using this cannon.

Aside from these important observations, only you can say whether it is true or not.