What JSON Lines is
JSON Lines is one complete JSON object per line, with no enclosing array and no commas between records. The file is not valid JSON as a whole, and that is the point.
Log pipelines, machine learning datasets and anything that appends records or reads them in a stream.
What RDF is
RDF in Turtle syntax: subject, predicate, object triples describing each row.
Linked data and semantic web projects.
What changes when you convert JSON Lines to RDF
Each line is parsed on its own, so a corrupt record does not take the file with it. Keys are unioned across lines in first-seen order, so a record missing a field leaves that cell empty rather than shifting the columns.
Each row becomes a subject with one predicate per column, under an example.org namespace you will want to change.
What carries over from JSON Lines to RDF
JSON Lines records 2 things about a table that RDF has no way to hold.
JSON Lines distinguishes a number from the text of a number; RDF does not, so every value arrives as text and has to be re-parsed by whatever reads it next.
An empty cell and a missing one are the same thing in RDF, so a null and an empty string in the JSON Lines both come out blank and can no longer be told apart.
The identifier 007 comes out of the RDF as 007. Reading it as a number would have made it 7, and an id that changes value is worse than one that stays text.
The role "Analyst, data" survives with its comma, in one cell rather than split across two. That is the first thing to check in any converted table, and the usual place a RDF file goes wrong.
The quotes around Jonah "Jo" Pryce are escaped with a backslash in the RDF.