Great use case. I have successfully used it in a similar way with SRT files (recording transcripts in SubRip Subtitle format) as well as CSV data from surveys that often has many columns with long text labels (the survey questions) and free text answers.
Ex. a prompt I had used for a developer skills survey .csv was:
> The CSV data below is the results of a skills survey sent to a group of software engineers. The first row is a header row. Please summarize this data in the areas that the People are Strong, Weak, Most Similar, and Unique:
Then, because of things I saw in the response, I asked a few follow-up questions:
> How much Azure experience is there in the group?
> Can you provide more explanation around your assessment that "Engineers generally have little to no experience with Dockers and Kubernetes."
> What other skills and experience do you see in the results that you haven't already mentioned?
To address my risk tolerance vis-a-vis the ChatGPT warnings (and previous UI leak of responses), I replaced the email addresses in the .csv file with "PersonA", "PersonB", ...
Ex. a prompt I had used for a developer skills survey .csv was:
> The CSV data below is the results of a skills survey sent to a group of software engineers. The first row is a header row. Please summarize this data in the areas that the People are Strong, Weak, Most Similar, and Unique:
Then, because of things I saw in the response, I asked a few follow-up questions:
> How much Azure experience is there in the group?
> Can you provide more explanation around your assessment that "Engineers generally have little to no experience with Dockers and Kubernetes."
> What other skills and experience do you see in the results that you haven't already mentioned?
To address my risk tolerance vis-a-vis the ChatGPT warnings (and previous UI leak of responses), I replaced the email addresses in the .csv file with "PersonA", "PersonB", ...