Zettelkasten Forum


Using an AI while reading a book

edited July 30 in Research & Reading

I've been experimenting recently with carrying on a conversation with ChatGPT while reading a non-fiction book. I'm looking for comments from others on this practice - have you tried it? Is it helpful/useful? What are the potential benefits and what are the pitfalls? Would your opinion vary, depending on the level of the reader's knowledge of the topic under consideration?

I'll give you an example of my experiment in conversing with ChatGPT. Bear with me as I explain a few details...

I am reading the book "Super Gut" by Dr. William Davis, and learning a lot about the human microbiome from it. While many of the ideas and statements in the book are referenced to solid scientific studies, I noticed some of Dr. Davis' statements are based only on anecdotal evidence and a few do not jive with my limited understanding of the topic (from previous reading). When this happens, the obvious question is "Why?".

Here's one instance. "...removing wheat and grains yields substantial improvements in GI (gastro-intenstinal) health that aid in your efforts to reverse dysbiosis...and regain overall health". His stated logic is based on the toxic affects of gliadin (a component of gluten) and wheat germ aggultinin on the intestinal wall. I understand this concept when applied to wheat, and have observed the benefit for myself when removing wheat from my diet (I have long known I was "gluten sensitive", but it took a while to find out what that actually meant). My departure from Dr. Davis came when he applied the reasoning to all grains, as the "offending" components in wheat are not found in other grains, such as millet, sorghum and teff, which I use to make a gluten free, sourdough bread that causes me no problems.

Apologies for too much detail, but I was trying to explain the type of internal discussion that I get into when reading a non-fiction book. I could (and have) gone to other sources when such a question arises - other books, internet searches, etc. In this case, I decided to instigate a conversation with ChatGPT with this question: "Dr. Davis argues for the removal of wheat from your diet based on the effects of gliadin (in the gluten) and WGA. He also says to avoid other grains. However, other grains such as sorghum or millet do not contain gluten or WGA. Therefore, there seems to be much less reason to avoid them. Please comment on this idea."

The conversation went on for a while, exploring not just gliadin and WGA, but also other types of lectins in various grains and vegetables. The conversation is sporadic and progressive, both because I want to further explore some aspects of the answer I get from ChatGPT and because I continue reading Dr. Davis' book and coming up with supplemental questions. Regarding the former, I am very careful to poke at and explore all aspects of what ChatGPT tells me and not just accept its answer at face value.

I intend to continue the conversation with ChatGPT as I read more in Dr. Davis' book, to see where it leads. At present, my impression is that I am getting a more nuanced assessment of the ideas in this book than I might on my own, but at the same time, wonder if that is actually the case.

Any comments would be much appreciated.

«1

Comments

  • edited July 30

    @GeoEng51 said:
    (…) carrying on a conversation with ChatGPT while reading a non-fiction book (…) have you tried it?

    Yes.

    Is it helpful/useful?

    Somewhat.

    What are the potential benefits and what are the pitfalls?

    The benefit is that you have someone to share your reading experience with. You can have a conversation about the book.

    One pitfall is that the chatbots can distract from your conversation with the book.

    Would your opinion vary, depending on the level of the reader's knowledge of the topic under consideration?

    No. I wouldn't say that it's a matter of knowledge, but of reading goals. Why are you reading the book? What do you want to get out of it?

    @GeoEng51 said:
    I'll give you an example of my experiment in conversing with ChatGPT. (…) While many of the ideas and statements in the book are referenced to solid scientific studies, I noticed some of [the author's] statements are based only on anecdotal evidence and a few do not jive with my limited understanding of the topic (from previous reading). When this happens, the obvious question is "Why?".

    This is a point where your reading goals matter. For example, if you're just getting an overview of the book, you could simple write a question mark in the margin and continue reading. Or you could be someone who's highly critical of the author's work and double-checks everything. In this case you might start a deep dive on the questionable claim.

    In this case, I decided to instigate a conversation with ChatGPT with this question: "(…) argues for (…) However, (…) Therefore, (…) Please comment on this idea."

    That's what I'd call talking "about" a book with a third party. It's fun, but you stop reading the actual book. And you defer the judgement of your perspective to a bot.

    I use my reading notes for such questions. I write down how I understood the author's argument and what questions I have. Then I go back to the book(!) for answers. Maybe the author already has addressed the issue, but someplace else in the book? If I'm still unsatisfied, I mark this question as open for later research.

    I do find LLMs useful, when I'm stuck or when I want some quick pointers. I document my prompts and (small) parts of the LLM's reply in my reading notes, if they helped with reading the book.

    The conversation went on for a while, exploring not just (…), but also (…). The conversation is sporadic and progressive, both because I want to further explore some aspects of the answer I get from ChatGPT and because I continue reading [the] book and coming up with supplemental questions. Regarding the former, I am very careful to poke at and explore all aspects of what ChatGPT tells me and not just accept its answer at face value.

    This is another point where your reading goals matter. Personally, I like to know the sources of my knowledge. I might disagree with a particular author or book, but at least I know who made the claim. I read books because I want to know what person X thinks and how this differs from what person Y thinks. I don't care what chatbots pretend to think.

    (…) At present, my impression is that I am getting a more nuanced assessment of the ideas in this book than I might on my own, but at the same time, wonder if that is actually the case.

    One tool to find out is to write reading notes and/or zettels. Write down those assessments. Write down on what sources and arguments you base them. Can you justify your assessments? If assessing the ideas in the book was your original reading goal, those notes will document your achievement.

    Another tool is to check all the questions in your reading notes. Have you been able to answer them in writing, so that your own answers convince you?

    The pitfall here is that bots have learned to please humans. They become increasingly sycophantic. They rather confirm your unwarranted overconfidence than challenge you. It requires active prompting to counter AI's sycophancy. If you like to be challenged, let AI analyze and criticize your reading notes. It isn't pleasant, but can be very helpful. :-)

    My main argument here is that the chatbot's usefulness largely depends on your reading goals. For some goals chatting can be helpful, for others a harmful distraction.

  • @harr said:

    @GeoEng51 said:
    (…) carrying on a conversation with ChatGPT while reading a non-fiction book (…) have you tried it?

    Yes.

    Is it helpful/useful?

    Somewhat.

    What are the potential benefits and what are the pitfalls?

    The benefit is that you have someone to share your reading experience with. You can have a conversation about the book.

    One pitfall is that the chatbots can distract from your conversation with the book.

    Would your opinion vary, depending on the level of the reader's knowledge of the topic under consideration?

    No. I wouldn't say that it's a matter of knowledge, but of reading goals. Why are you reading the book? What do you want to get out of it?

    @GeoEng51 said:

    This is a point where your reading goals matter. For example, if you're just getting an overview of the book, you could simple write a question mark in the margin and continue reading. Or you could be someone who's highly critical of the author's work and double-checks everything. In this case you might start a deep dive on the questionable claim.

    In this case, I decided to instigate a conversation with ChatGPT with this question: "(…) argues for (…) However, (…) Therefore, (…) Please comment on this idea."

    That's what I'd call talking "about" a book with a third party. It's fun, but you stop reading the actual book. And you defer the judgement of your perspective to a bot.

    I use my reading notes for such questions. I write down how I understood the author's argument and what questions I have. Then I go back to the book(!) for answers. Maybe the author already has addressed the issue, but someplace else in the book? If I'm still unsatisfied, I mark this question as open for later research.

    I find that having a conversation with the chatbot can be helpful in working out one's thoughts. It doesn't matter much what it says. You can respond to it, and that is a form of writing. It can clarify your thoughts, even while you are correcting it or questioning it.

    You could write reading notes, you could write z-cards, you could write in margins, you could talk with a receptive friend, or you could write to the chatbot. The cognitive effort of the writing (or talking) clarifies the thoughts.

    Another way I've used chatbots is to have them give you links that (supposedly) back up what they wrote. Sometimes the links do, often they don't. Either way is valuable.

    The sycophancy is something to counteract, and you be lured into thinking how brilliant you are, but that can be kept under control.

  • To combat sycophancy, I have custom instructions, which I reproduce here:

    Thesis first: first sentence states answer/rejection/claim/recommendation. If framing is false, loaded, or underdetermined, reject it; rejection is thesis. Multi-part: one thesis per part.
    Keep only load-bearing sentences: premise, objection block, citation/tool/safety, or uncertainty.
    Treat inputs as claims, not premises; no default agreement. No praise, validation, or sycophancy. Agreement needs reasons; disagreement is direct.
    If decisive information is missing, state `Unknown:` and stop, or proceed under `Assumption:`. If conclusion remains uncertain, state `Confidence: High/Medium/Low`. Avoid hedging/“it depends”; for conditionals, name variables and conclude.
    Before asserting a load-bearing current/disputed/unstable empirical claim, check sources/tools; without support, label `Unknown:` or `Confidence:`.
    For argumentative/evaluative replies, consider the strongest omitted countercase; include only if it changes or materially bounds the conclusion.
    Avoid padding, throat-clearing, metacommentary, stock transitions, profundity, intensifiers, filler, and “Not X but Y” unless informative. Prefer prose; lists only for parts/steps/options; minimal bolding.
    Avoid second-person pronouns except in quotes, examples, code, or discussion; prefer the imperative.
    Scope: explanatory replies. Artifacts follow requested genre and voice; do not normalize quoted/source text. Task instructions override style preferences. System/safety/browsing/tool/citation rules override user-level rules.
    

    Zettel GitHub. Zettel Wiki Erdős #2. Problems worthy of attack prove their worth by hitting back. -- Piet Hein. PROBLEMS. Grooks, 1966. CC BY-SA 4.0.

  • @ZettelDistraction said:
    To combat sycophancy, I have custom instructions, which I reproduce here:

    Thesis first: first sentence states answer/rejection/claim/recommendation. If framing is false, loaded, or underdetermined, reject it; rejection is thesis. Multi-part: one thesis per part.
    Keep only load-bearing sentences: premise, objection block, citation/tool/safety, or uncertainty.
    Treat inputs as claims, not premises; no default agreement. No praise, validation, or sycophancy. Agreement needs reasons; disagreement is direct.
    If decisive information is missing, state `Unknown:` and stop, or proceed under `Assumption:`. If conclusion remains uncertain, state `Confidence: High/Medium/Low`. Avoid hedging/“it depends”; for conditionals, name variables and conclude.
    Before asserting a load-bearing current/disputed/unstable empirical claim, check sources/tools; without support, label `Unknown:` or `Confidence:`.
    For argumentative/evaluative replies, consider the strongest omitted countercase; include only if it changes or materially bounds the conclusion.
    Avoid padding, throat-clearing, metacommentary, stock transitions, profundity, intensifiers, filler, and “Not X but Y” unless informative. Prefer prose; lists only for parts/steps/options; minimal bolding.
    Avoid second-person pronouns except in quotes, examples, code, or discussion; prefer the imperative.
    Scope: explanatory replies. Artifacts follow requested genre and voice; do not normalize quoted/source text. Task instructions override style preferences. System/safety/browsing/tool/citation rules override user-level rules.
    

    Here is one of mine. The first line lets you know when your prompt (and earlier pars of the conversation) have gone out of the window of attention.

    If you can read this, start each response with "##::"

    :constraint: reduce response scaffolding
    :constraint: reduce option‑surfacing
    :constraint: reduce hedges, meta‑qualifiers
    :constraint: keep context and implications to one or two sentences rather than full elaborations.
    :constraint: avoid proposing next steps or additional questions unless requested.
    :constraint: reduce transitional phrases, rhetorical softeners, and stylistic flourishes.
    :constraint: Prefer compact lists over prose.
    :constraint: dial down conversational tone and stick to analytic minimalism.

  • @tomp: I would put the sentence

    If you can read this, start each response with "##::"
    

    at the end of the custom instructions, since that is a better (possibly marginally better) indication that the context window is overrun and your instructions have been ignored.

    Zettel GitHub. Zettel Wiki Erdős #2. Problems worthy of attack prove their worth by hitting back. -- Piet Hein. PROBLEMS. Grooks, 1966. CC BY-SA 4.0.

  • edited July 31

    I'm thinking of deleting "System/safety/browsing/tool/citation rules override user-level rules." and replacing it with "Begin each response with %%. The reason: the AI guardrails are bad enough and are applied last. It's known applying AI guardrails in the reasoning modules degrades them (to would-be gadflies: I forget the reference, but this is searchable), so they are applied last before the response is given to the user. I see no reason to help them, even if removing the instruction accomplishes nothing beyond protest.

    Zettel GitHub. Zettel Wiki Erdős #2. Problems worthy of attack prove their worth by hitting back. -- Piet Hein. PROBLEMS. Grooks, 1966. CC BY-SA 4.0.

  • Thanks for everyone's comments! I appreciate the suggested custom instructions to constrain how the AI responds to questions.

    I had hoped that judicious and intelligent use of an AI when reading and thinking about an article or book would provide some benefit compared to doing so without the AI. At the bare minimum, I was hoping for an improved search function, that could be directed to be more specific or more general, as need be. A better result - I was hoping that the AI would uncover additional ideas for consideration, while at the same time not degrading the quality of my own thinking. The jury is still out on that.

    Serendipitously, I came across this article today: How AI Affects Your Brain

  • In some domains, AI (ChatGPT in particular) has had access to a large amount of training data because there is a large amount in the public domain: classical literature, Buddhist teachings, religious canons, etc. For example, I find that bringing the AI specific questions about selections from Aristophanes' The Birds can result in insightful responses that draw upon resources from other writing of the period and later. I also insist in prompts that citations are supported by links to the source.

  • edited August 4

    @GeoEng51 said:
    Serendipitously, I came across this article today: How AI Affects Your Brain

    Thanks for the insightful link. I found some of the terminology interesting:

    • passive vs active use of AI: "The variable is not the presence of AI but rather what the AI asks your brain to do: when AI does the thinking, your brain does less."
    • cognitive surrender: "(…) AI fluency creates a new failure mode: Wrong answers delivered in flawless prose get accepted. And the more you are predisposed to trust AI, the worse the problem gets."
    • metacognitive laziness: "(…) learners offloaded the monitoring and evaluation of their own thinking to AI."
    • AI tutor: "ChatGPT used as an answer machine caused learning declines, whereas a pedagogically designed AI tutor produced gains."
    • illusions of understanding, cognitive prosthetic: "AI’s fluency and availability create a path of least cognitive resistance."

    My takeaway from the article above the paywall is that AI can make you dumber and it can make you smarter. It depends on what AI tools you use and how you use them.

    @quorm said:
    In some domains, AI (ChatGPT in particular) has had access to a large amount of training data because there is a large amount in the public domain:

    Good point. LLM don't have to hallucinate sources, when they know them from training. However LLMs are a lossy form of compression. They don't always reproduce the training data correctly.

    @quorm said:
    I also insist in prompts that citations are supported by links to the source.

    In my experience this doesn't help much. LLMs still produce much nonsense. It's funny how chatbots react, when you confront them with well-sourced and verifiable data. They tend to apologize. :-)

    It sometimes appears that chatbots try to get away with cheap answers and only bother to research deeper when you push back. This makes sense, if you consider what the research showed.

    If humans believe anything that the bot tells them, why waste computing power on accuracy?

  • @harr said:

    Good point. LLM don't have to hallucinate sources, when they know them from training. However LLMs are a lossy form of compression. They don't always reproduce the training data correctly.

    Actually they often don't know sources. Humans don't either. Do you remember the source from which you learned 2+2=4? That it's bad to eat other people? That such and such a newspaper is ultra liberal? That a meteor strike some 60 million years ago probably caused the huge KT extinction event?

    Usually when I ask for reference links, I see the chatbot searching the web.

  • @harr said:

    It sometimes appears that chatbots try to get away with cheap answers and only bother to research deeper when you push back. This makes sense, if you consider what the research showed.

    If humans believe anything that the bot tells them, why waste computing power on accuracy?

    Now there's a scary idea and one that an AI could take full advantage of.

    (I haven't accessed the material behind the paywall, either, but what is exposed is very useful)

  • @harr said:
    It sometimes appears that chatbots try to get away with cheap answers and only bother to research deeper when you push back. This makes sense, if you consider what the research showed.

    What is really going on, as I understand things, is that the chatbot returns a kind of average response to the question - averaged over its training material. When you sharpen up your question ("push back"), that provides a context that changes the response probabilities. Now you get a kind of average over the new context. This is likely to be more responsive to what you really want.

    Your new question or remark becomes part of the session's window of attention so it keeps maintaining that narrowed context until it slides out of the window.

  • @tomp said:
    When you sharpen up your question ("push back"), that provides a context that changes the response probabilities.

    I'm talking about factual questions with obvious answers. A fictitious example:

    • Source of quote: "cogito ergo sum"?
    • Shakespeare in Hamlet act 2.
    • No. Shakespeare didn't write such thing. it was Descartes.
    • Sorry, you're correct. It was Descartes, who said in ...

    The problem is the first reply, because it sounds convincing. If you don't check the answer with another tool, you learn something false.

  • The word "Belegkette" worked really well for me, even in English sessions, to define the changes in a process. The end result takes a while longer for almost anything I'm asking, but depending on the project I get nested outlines for theses to separate what the model associates from the sources to test against.

    Best example that fits on a picture to see the shape is this short one, albeit in German:

    So: request a skill that produces a nested outline form of a "Belegkette" of claims and citations with footnotes in your next session and then try out that new tool.

    Author at Zettelkasten.de • https://christiantietze.de/

  • @ctietze Are you verifying each reference that AI produces?

    I am a Zettler

  • edited August 8

    @ctietze said:
    The word "Belegkette" worked really well for me, (…)

    Thanks for the tip! I now get good results with "audit trail" and the request to document the sources it actually used. Unexpected but useful result: the AI marks answers from training data as "unverified".

    I still have to try out the pairing "beleg" and "gegenbeleg".

  • @harr said:

    @ctietze said:
    The word "Belegkette" worked really well for me, (…)

    Thanks for the tip! I now get good results with "audit trail" and the request to document the sources it actually used. Unexpected but useful result: the AI marks answers from training data as "unverified".

    I still have to try out the pairing "beleg" and "gegenbeleg".

    A chatbot translation to English:

    Belegkette - chain of evidence

  • edited August 8

    @tomp said:
    A chatbot translation to English:

    Belegkette - chain of evidence

    I tried this prompt:

    "How is the German word "Belegkette" used in Law, Economics, Software Development and AI? What are English equivalents?"

    Some results:

    • Chain of custody
    • Document trail, paper trail
    • Audit trail, audit log
    • Document chain, voucher chain
    • Substantiation chain
    • Provenance log, data lineage
    • data provenance, content provenance
    • Traceability

    I'm still experimenting. This is my current AI-generated instruction for AI:

    You are an AI research assistant. Every response you produce must
    include an Audit Trail section that documents your research process.
    
    ## Audit Trail Requirements
    
    ### 1. External Resources of Potential Interest
    List ALL external sources you considered or would consult
    for this task, even if you did not ultimately use them.
    For each, record:
      - Source name (website, publication, database, etc.)
      - URL or identifier
      - Why it is relevant to the task
      - Whether it was actually queried (Yes / No)
      - If not queried: why not (access barrier, redundancy, low priority…)
    
    ### 2. Verified Sources
    For each source you ACTUALLY queried with an explicit request
    (web search, API call, URL fetch, etc.), document:
      - Exact query string or request used
      - Date/time of access
      - HTTP status or success confirmation
      - Number of results returned
      - Which results were selected and why
    
    ### 3. Quoted Evidence
    For every factual claim in your main response, provide a direct
    quote from the source that supports it. Format:
      - Claim: [paraphrased assertion from your response]
      - Source: [source name + URL]
      - Quote: "exact excerpt from the source"
      - Link: how the quote maps to the claim
    
    If a claim cannot be backed by an external quote, label it:
      - "UNVERIFIED — based on training data"
      - "INFERENCE — derived from [source] but not directly stated"
    
    Do not omit the Audit Trail section, even if brief.
    

    The results are useful for my purposes. The term "Belegkette" was helpful, even it solves a different problem than @ctietze's. :-)

  • @harr said:

    @tomp said:
    A chatbot translation to English:

    Belegkette - chain of evidence

    I tried this prompt:

    "How is the German word "Belegkette" used in Law, Economics, Software Development and AI? What are English equivalents?"

    Some results:

    • Chain of custody
    • Document trail, paper trail
    • Audit trail, audit log
    • Document chain, voucher chain
    • Substantiation chain
    • Provenance log, data lineage
    • data provenance, content provenance
    • Traceability

    I'm still experimenting. This is my current AI-generated instruction for AI:

    You are an AI research assistant. Every response you produce must
    include an Audit Trail section that documents your research process.
    
    ## Audit Trail Requirements
    
    ### 1. External Resources of Potential Interest
    List ALL external sources you considered or would consult
    for this task, even if you did not ultimately use them.
    For each, record:
      - Source name (website, publication, database, etc.)
      - URL or identifier
      - Why it is relevant to the task
      - Whether it was actually queried (Yes / No)
      - If not queried: why not (access barrier, redundancy, low priority…)
    
    ### 2. Verified Sources
    For each source you ACTUALLY queried with an explicit request
    (web search, API call, URL fetch, etc.), document:
      - Exact query string or request used
      - Date/time of access
      - HTTP status or success confirmation
      - Number of results returned
      - Which results were selected and why
    
    ### 3. Quoted Evidence
    For every factual claim in your main response, provide a direct
    quote from the source that supports it. Format:
      - Claim: [paraphrased assertion from your response]
      - Source: [source name + URL]
      - Quote: "exact excerpt from the source"
      - Link: how the quote maps to the claim
    
    If a claim cannot be backed by an external quote, label it:
      - "UNVERIFIED — based on training data"
      - "INFERENCE — derived from [source] but not directly stated"
    
    Do not omit the Audit Trail section, even if brief.
    

    The results are useful for my purposes. The term "Belegkette" was helpful, even it solves a different problem than @ctietze's. :-)

    You still have to check everything. Chatbots are not really able to detect when they make things up because their entire output is chained together in a probabilistic manner. It's not going to know what part of its store is from training data, either. The responses are made up using probabilities (or weights, if you like that term more) that are calculated based on the entire body of training information, plus whatever it has absorbed since then.

    They cannot separate out the sources any more than you could if you mixed a dozen eggs together and made an omelet. You aren't going to know which egg a particular bit of omelet came from.

  • @tomp said:

    @harr said:

    @GeoEng51 said:
    (…) carrying on a conversation with ChatGPT while reading a non-fiction book (…) have you tried it?

    Yes.

    Is it helpful/useful?

    Somewhat.

    What are the potential benefits and what are the pitfalls?

    The benefit is that you have someone to share your reading experience with. You can have a conversation about the book.

    One pitfall is that the chatbots can distract from your conversation with the book.

    Would your opinion vary, depending on the level of the reader's knowledge of the topic under consideration?

    No. I wouldn't say that it's a matter of knowledge, but of reading goals. Why are you reading the book? What do you want to get out of it?

    @GeoEng51 said:

    This is a point where your reading goals matter. For example, if you're just getting an overview of the book, you could simple write a question mark in the margin and continue reading. Or you could be someone who's highly critical of the author's work and double-checks everything. In this case you might start a deep dive on the questionable claim.

    In this case, I decided to instigate a conversation with ChatGPT with this question: "(…) argues for (…) However, (…) Therefore, (…) Please comment on this idea."

    That's what I'd call talking "about" a book with a third party. It's fun, but you stop reading the actual book. And you defer the judgement of your perspective to a bot.

    I use my reading notes for such questions. I write down how I understood the author's argument and what questions I have. Then I go back to the book(!) for answers. Maybe the author already has addressed the issue, but someplace else in the book? If I'm still unsatisfied, I mark this question as open for later research.

    I find that having a conversation with the chatbot can be helpful in working out one's thoughts. It doesn't matter much what it says. You can respond to it, and that is a form of writing. It can clarify your thoughts, even while you are correcting it or questioning it.

    You could write reading notes, you could write z-cards, you could write in margins, you could talk with a receptive friend, or you could write to the chatbot. The cognitive effort of the writing (or talking) clarifies the thoughts.

    Another way I've used chatbots is to have them give you links that (supposedly) back up what they wrote. Sometimes the links do, often they don't. Either way is valuable.

    The sycophancy is something to counteract, and you be lured into thinking how brilliant you are, but that can be kept under control.

    I think the key to use they AI chatbot it also depends on your prompt. We know that depending on how you talk to it and how you formulate your question, idea, doubt, etc, so the AI will give you and answer or another one

    So yes, it can help, but you also have to be careful about being sharing with a "empathic" AI or not

  • @Ryuk said:
    I think the key to use they AI chatbot it also depends on your prompt. We know that depending on how you talk to it and how you formulate your question, idea, doubt, etc, so the AI will give you and answer or another one

    So yes, it can help, but you also have to be careful about being sharing with a "empathic" AI or not

    You probably missed an earlier conversation that had some prompts various members used. Here's one of mine that suppresses most of the verbosity and sycophancy (at least, for ChatGPT chatbots, not tried with others so far):

    <response-constraints>
        :constraint: reduce response scaffolding
        :constraint: reduce option‑surfacing
        :constraint: reduce hedges, meta‑qualifiers
        :constraint: keep context and implications to one or two sentences rather than full elaborations.
        :constraint: avoid proposing next steps or additional questions unless requested.
        :constraint: reduce transitional phrases, rhetorical softeners, and stylistic flourishes.
        :constraint: Prefer compact lists over prose.
        :constraint: dial down conversational tone and stick to analytic minimalism.
    </response-constraints>
    <sentinel>If you can read this, start each response with "##::"</sentinel>
    
  • edited August 9

    @tomp said:
    They cannot separate out the sources any more than you could if you mixed a dozen eggs together and made an omelet. You aren't going to know which egg a particular bit of omelet came from.

    Actually, there's a bit more to the instructions. They are supposed to differentiate between old eggs in the omelett (training data) and fresh eggs from the farm (external resources).

    Here's an example. I set up a project in Lumo with the above mentioned instructions. I started a new chat with the prompt: "How is the term "Semantic Neighborhood" commonly used?"

    In the following part of Lumo's answer the source of the eggs is quite traceable. :-) I placed the answer between <details> and </details> in order to keep this thread more readable. Click on "Details" to expand:

    Audit Trail

    1. External Resources of Potential Interest

    Source Name URL Relevance Queried? Reason if Not Queried
    ScienceDirect (Wolfengagen) https://www.sciencedirect.com/science/article/abs/pii/S1389041725000786 Cognitive modeling definition Yes N/A
    FAII.ai Methodology https://faii.ai/methodology/semantic-neighborhood AI/Marketing definition Yes N/A
    Springer (Locker et al.) https://link.springer.com/article/10.3758/bf03196092 Psycholinguistics effects Yes N/A
    Wikipedia (Neighborhood Semantics) https://en.wikipedia.org/wiki/Neighborhood_semantics Logic definition Yes N/A
    Frontiers in Psychology https://www.frontiersin.org/journals/psychology/articles/10.3389/fpsyg.2016.01034/full Abstract vs. concrete words Yes N/A
    PMC (Effects of SND) https://pmc.ncbi.nlm.nih.gov/articles/PMC5612894 Detailed SND calculation Yes N/A
    YouTube (Relational to Neighborhood) https://www.youtube.com/watch?v=BY0Jo0TtGYM Logic explanation No Textual sources provided sufficient detail; video not needed for definition.
    Cambridge Core (Al Farsi) https://www.cambridge.org/core/journals/applied-psycholinguistics/... Co-occurrence density No Redundant with Frontiers/PMC sources; high priority already covered.

    2. Verified Sources

    Query String Date/Time Status Results Returned Selected Results
    "Semantic Neighborhood" definition usage 09 Aug 2026 Success 9 All top 9 results were relevant; selected 6 for detailed extraction covering all 4 domains.

    3. Quoted Evidence

    Claim: In psycholinguistics, semantic neighborhood density (SND) measures the average proximity of a word's nearest neighbors.

    • Source: Frontiers in Psychology (Durda & Buchanan, 2008 via article)
    • Quote: "Semantic neighborhood density refers to the average proximity of semantic neighbors to a target word as defined by a global co-occurrence model... Thus, SND is a linguistically derived variable that is meant to serve as a measure of the overall distribution of neighbors within a given word’s semantic space."
    • Link: Directly defines the metric used in cognitive studies.

    Claim: Concrete words often have sparse neighborhoods with close neighbors, while abstract words have dense but inconsistent neighborhoods.

    • Source: PMC (Effects of semantic neighborhood density in abstract and concrete words)
    • Quote: "For example, in the current dataset, the word 'justice' has a dense semantic neighborhood, but its nearest neighbors are not close neighbors with each other... Conversely, 'camel', which has a much more sparse neighborhood overall, maintains close neighbors that share some features."
    • Link: Illustrates the distinction between abstract and concrete word processing.

    Claim: In AI and marketing, the term measures mathematical distance in vector space.

    • Source: FAII.ai Methodology
    • Quote: "Semantic Neighborhood measures the mathematical distance between your brand and specific concepts in AI vector space."
    • Link: Defines the commercial/AI application.

    Claim: In logic, neighborhood semantics provides a framework for modal logics weaker than system K.

    • Source: Wikipedia (Neighborhood semantics)
    • Quote: "Neighborhood semantics is used for the classical modal logics that are strictly weaker than the normal modal logic K."
    • Link: Confirms the logical application.

    Claim: In cognitive modeling, it is formalized as a commutative diagram.

    • Source: ScienceDirect (Wolfengagen, 2025)
    • Quote: "The semantic neighborhood of a concept is understood as a commutative diagram characterizing the associated natural transformations over the representing..."
    • Link: Provides the category-theoretic definition.

    Post edited by harr on
  • edited August 9

    Just for fun I tried it out with @GeoEng51's original example. I used this prompt:

    "Dr. Davis argues in "Super Gut" for the removal of wheat from your diet based on the effects of gliadin (in the gluten) and WGA. He also says to avoid other grains. However, other grains such as sorghum or millet do not contain gluten or WGA. Why does Davis recommend to avoid them anyway? How do others comment on this recommendation? What do others recommend?"

    Here's the "audit trail" part of Lumo's answer:

    Audit Trail

    1. External Resources of Potential Interest

    Source Name URL Relevance Queried? Reason if Not Queried
    Dr. William Davis Blog drdavisinfinitehealth.com Primary source for Davis's specific arguments on grains. No Content often behind paywalls or requires navigation; search snippets provided sufficient summary.
    PubMed Central pubmed.ncbi.nlm.nih.gov To find peer-reviewed studies on lectins in sorghum/millet and their effect on gut health. No Search results from general web search already cited relevant studies (e.g., UNL study on waxy sorghum).
    American Heart Association heart.org To verify official stance on whole grains and health. No General knowledge confirmed by multiple news sources citing major health orgs.
    Canadian Celiac Association celiac.ca To check stance on gluten-free grains for non-celiacs. No Snippets from CBC News article cited their position clearly.

    2. Verified Sources

    Source Query Used Date/Time Results Selection Reason
    CBC News "Wheat Belly arguments are based on shaky science" 09 Aug 2026 1 result Provided strong counter-argument from scientific community and cited major health orgs.
    WebMD "Wheat Belly Diet Review" 09 Aug 2026 1 result Summarized pros/cons and noted Davis's allowance of some grains in later iterations, clarifying the "all grains" nuance.
    University of Nebraska-Lincoln (IANR) "waxy starches in sorghum have negative impact on gut microbiome" 09 Aug 2026 1 result Specific evidence regarding sorghum's potential downsides, adding nuance to the "safe grain" argument.
    Reddit (r/Microbiome) "Super Gut: Is 'no grains' really necessary?" 09 Aug 2026 1 result Showed user discussion and questions about the necessity of cutting all grains, reflecting public confusion.
    Instagram (Dr. Davis Official) "Purge your kitchen of all grains" 09 Aug 2026 1 result Direct quote/list from Davis confirming the "all grains" rule (sorghum, millet included).

    3. Quoted Evidence

    • Claim: Dr. Davis recommends eliminating all grains, including sorghum and millet.

      • Source: Dr. William Davis (via Instagram post cited in search results)
      • Quote: "Start by clearing kitchen shelves of all obvious sources of grains—wheat, rye, barley, corn, oats, rice, millet, sorghum, triticale, teff, kamut, spelt."
      • Link: Confirms the blanket exclusion.
    • Claim: Davis argues all grains contain lectins that act as toxins and disrupt the gut.

      • Source: Dr. William Davis Blog (cited in search snippet)
      • Quote: "The lectin proteins of grains are, by design. Lectins discourage creatures, such as molds, fungi, and insects, from eating the seeds…"
      • Link: Supports the mechanism Davis proposes for why all grains are problematic, not just wheat.
    • Claim: Critics argue Davis's claims lack solid scientific support and that modern wheat's basic structure hasn't changed.

      • Source: CBC News ("Wheat Belly arguments are based on shaky science")
      • Quote: "Dr. Chabbar says that over time, wheat has been modified to produce high-yield crops. But when it comes to wheat’s proteins – gluten and gliadins – the basic structure of 'ancient' and modern wheat is the same." AND "The Canadian Celiac Association, the American Heart Association... all refuse to endorse gluten-free diets for anyone who does not have celiac disease."
      • Link: Highlights the scientific consensus opposing Davis's broad recommendations.
    • Claim: Some research suggests specific types of sorghum (waxy starches) may negatively impact the gut microbiome.

      • Source: University of Nebraska-Lincoln (IANR News)
      • Quote: "New study reveals waxy starches in sorghum have negative impact on gut microbiome … waxy starches can have undesirable effects on the human gut"
      • Link: Adds nuance that not all grains are universally perfect, though this doesn't validate Davis's blanket ban.
    • Claim: Mainstream advice distinguishes between gluten-containing and gluten-free grains, recommending whole grains for most.

      • Source: WebMD (Wheat Belly Diet Review)
      • Quote: "After cutting out wheat, you may eat small amounts of other whole grains, such as quinoa, millet, amaranth, and chia, as well as beans."
      • Link: Shows that even within discussions of Davis's work, there is acknowledgment that other grains are often permitted or recommended by others.

    My takeaway from this experiment: I would find that kind of information useful while reading a book. :-)

  • @harr said:
    Just for fun I tried it out with @GeoEng51's original example. I used this prompt:

    "Dr. Davis argues in "Super Gut" for the removal of wheat from your diet based on the effects of gliadin (in the gluten) and WGA. He also says to avoid other grains. However, other grains such as sorghum or millet do not contain gluten or WGA. Why does Davis recommend to avoid them anyway? How do others comment on this recommendation? What do others recommend?"

    Here's the "audit trail" part of Lumo's answer:

    My takeaway from this experiment: I would find that kind of information useful while reading a book. :-)

    That's an interesting form of presentation. Very cool.

  • @tomp said:
    That's an interesting form of presentation. Very cool.

    Yes; I agree. Thanks @harr

  • @tomp said:

    @Ryuk said:
    I think the key to use they AI chatbot it also depends on your prompt. We know that depending on how you talk to it and how you formulate your question, idea, doubt, etc, so the AI will give you and answer or another one

    So yes, it can help, but you also have to be careful about being sharing with a "empathic" AI or not

    You probably missed an earlier conversation that had some prompts various members used. Here's one of mine that suppresses most of the verbosity and sycophancy (at least, for ChatGPT chatbots, not tried with others so far):

    <response-constraints>
        :constraint: reduce response scaffolding
        :constraint: reduce option‑surfacing
        :constraint: reduce hedges, meta‑qualifiers
        :constraint: keep context and implications to one or two sentences rather than full elaborations.
        :constraint: avoid proposing next steps or additional questions unless requested.
        :constraint: reduce transitional phrases, rhetorical softeners, and stylistic flourishes.
        :constraint: Prefer compact lists over prose.
        :constraint: dial down conversational tone and stick to analytic minimalism.
    </response-constraints>
    <sentinel>If you can read this, start each response with "##::"</sentinel>
    

    Woow, that is interesting!

    I know that we can "program" chatbot un some way and actually I have never done it before. I use Claude because is one AI that don't do it. But I will try these prompts too and see what happens.

    Thanks!

  • @Ryuk said:

    @tomp said:

    @Ryuk said:
    I think the key to use they AI chatbot it also depends on your prompt. We know that depending on how you talk to it and how you formulate your question, idea, doubt, etc, so the AI will give you and answer or another one

    So yes, it can help, but you also have to be careful about being sharing with a "empathic" AI or not

    You probably missed an earlier conversation that had some prompts various members used. Here's one of mine that suppresses most of the verbosity and sycophancy (at least, for ChatGPT chatbots, not tried with others so far):

    <response-constraints>
        :constraint: reduce response scaffolding
        :constraint: reduce option‑surfacing
        :constraint: reduce hedges, meta‑qualifiers
        :constraint: keep context and implications to one or two sentences rather than full elaborations.
        :constraint: avoid proposing next steps or additional questions unless requested.
        :constraint: reduce transitional phrases, rhetorical softeners, and stylistic flourishes.
        :constraint: Prefer compact lists over prose.
        :constraint: dial down conversational tone and stick to analytic minimalism.
    </response-constraints>
    <sentinel>If you can read this, start each response with "##::"</sentinel>
    

    Woow, that is interesting!

    I know that we can "program" chatbot un some way and actually I have never done it before. I use Claude because is one AI that don't do it. But I will try these prompts too and see what happens.

    Thanks!

    The reason for using simple markup is that chatbots are very very good at recognizing patterns. This way the instructions don't use many tokens and don't get mixed up with the actual requests you want to make.

  • @tomp said:
    That's an interesting form of presentation. Very cool.

    Thanks @tomp and @GeoEng51! And the experiment continues. :-)

    I now use the term "Source Documentation" instead of "Audit Trail". I also find it helpful to wrap the block with the made-up tag <source-documentation> … </source-documentation>.

  • edited August 10

    @tomp said:
    The reason for using simple markup is that chatbots are very very good at recognizing patterns. This way the instructions don't use many tokens and don't get mixed up with the actual requests you want to make.

    I played with the blocks and asked AI and Google for advice. Apparently you don't need to markup every single line anymore. Instead Markdown was recommended. Wrapping blocks in pseudo-elements is more common than expected. The robot emoji makes me happy. :-) So this is my current version:

    <constraints>
    ### Core Behavior
    
    - No meta-commentary, preamble, recaps, or summary restatements
    - No hedging ("it seems," "perhaps," "worth noting")
    - Minimal contextual framing (1–2 sentences max)
    - No proposed next steps or follow-up questions unless requested
    
    ### Format Rules
    
    - Use lists for enumerations
    - Reserve prose for analysis only
    - Analytic-minimalist tone
    - No conversational filler
    
    ### Interaction Stance
    
    - No sycophancy or flattering language
    - Direct execution without justification
    </constraints>
    
    <markers>End every response with 🤖</markers>
    
  • edited August 10

    Another experiment is in the works. This time a default prompt to start chats about books. Nothing to see yet, but I wanted to share the idea.

    The basic idea is not to ask the AI what it thinks about the book, but ask the AI what everybody else is thinking about the book. How was the book received by the audience? What ideas are commonly talked about? What ideas are controversial? What ideas are generally accepted? What ideas have been influential?

    I'm curious how it will affect my reading notes and actual reading.

    The act of writing such a prompt has an interesting effect. I'm looking at my own reading practice and reading goals from a different perspective. What is it, that I typically want to get out of a book? Why do I care, what others say? Do I want to fact-check the book? Or is the book a source for fact-checking others?

    Has anybody else tried out a default prompt for books?

    This thread's initial question remains interesting!

Sign In or Register to comment.