Interesting, Chris, though copy and paste would need to be automated somehow. Here's a hopefully more readable format for some of the JSON data.
"Name": "Little-4639",
"FirstName": "William",
"MiddleName": "",
"LastNameAtBirth": "Little",
"LastNameCurrent": "Little",
"Nicknames": "",
"LastNameOther": "Litle",
"RealName": "William",
"Prefix": "",
"Suffix": "",
"BirthLocation": "Cumberland, England",
"DeathLocation": "Dormansteads, Stapleton, Cumberland, England.",
"Gender": "Male",
"BirthDate": "1676-07-09",
"DeathDate": "1763-03-27",
ChatGPT gives a passable result in this case, except it has assumed William lived in the same place where he died, which may not be justified.
However, "artificial intelligence" is not needed for this. It's not hard to write algorithmic code which produces a biography from the same data. (Ian Beacall's Auto Bio uses such an approach, and I have my own private code to do this.) As distinct from a language model like ChatGPT, an algorithm will give a predictable result, without risk of inventing things.
Because much information, e.g. from censuses, is not in WikiTree data fields, it can't be made available in this way. It can be extracted from another database (I do that) or an existing biography (I think Ian does that in some cases), but the latter makes the process circular. ChatGPT could use events templates, but so can algorithms, and anyhow those have not been authorised.
I think "AI" would be massive overkill for something that can be done algorithmically.