Tag Archives: LLM

Learnings from assignments / open book exams at Indian Institute of Technology Gandhinagar – Executive Masters in Data Science for Decision Making

One important lesson I learned while working with spatio-temporal graph data on the METR-LA dataset during my Executive Masters open-book assignment:

Do not keep switching between Claude, ChatGPT, Perplexity, Gemini, and other LLMs or AI tools during the execution stage. This lesson has repeated itself in the two years throughout the Executive Masters whenever we have been allowed to use LLMs.

My learning:

• Different LLMs reason differently

• They are trained and fine-tuned differently

• They suggest different libraries, assumptions, fixes, and coding styles

• Mixing their guidance during debugging can create unnecessary chaos

• What looks like “more intelligence” can become “more confusion”

• Multi-model thinking is useful during brainstorming

• It helps in debating, exploring, comparing, and expanding ideas

• But once execution begins, consistency matters more than variety

• Pick one model and work through the problem step by step

• Ask it to explain, debug, simplify, correct, and iterate

• Stay with one reasoning path until the solution stabilizes

My conclusion:

Use multiple LLMs for exploration.

Use one LLM for execution.

Mixing models during ideation can create insight.

Mixing models during implementation can create chaos.

This is especially true in technical work involving data science, graph ML, spatio-temporal modeling, package dependencies, tensor shapes, runtime environments, and debugging.

Progress comes from disciplined iteration, not tool-hopping.

Note: Enhanced / compiled with help of AI / LLMs

How can portals & commerce have intelligence via LLMs/GAI/ChatGPT/Gemini/etc. – Part 1

Here is my solution template for having intelligence from AI/GAI/LLMs in Portals & Commerce – Part 1:

  • Assumptions: Java/PHP/Dot Net/SharePoint/Liferay/WordPress/Drupal type of a portal and / or commerce
  • Just like we have HTML – HEAD / BODY / FOOTER / HEADER / META TAGS / BACKEND LOGIC in Java / Front end JSP / etc. in web applications, let’s say we define a section in HEAD / META / etc. to contextualize the page and it’s content – WHAT, WHY, WHERE, WHEN, HOW, etc.? Right now in classic HTML / Java / JSP we define Meta tags and actual content but no semantics / context / etc. Till now it was fine because we could manage with search engines, basic chatbots and so on.
  • What these new tags and standard does is it gives context for ChatBots, Agents & LLMs/GAI/ChatGPT/Gemini and so on. Now these AI systems can talk to these pages and users on it with a context which immediately results in much better intelligence.
  • How do we define intelligence for above components:
  • Context sensitive help
  • Context sensitive agentic work
  • Semantic / contextual / relevance-based flow suggestions of usage of system pages
  • Automated suggestions on shopping
  • Context sensitive content generation
  • Use cases are endless and all these get enabled at GAI/LLMs/Agentic level instead of customized baking in the product or customizations. This is a repeat of Google / Bing / Yahoo search but at AI level
  • What this basically does is it adds context to all the pages and the portal or commerce as a whole.
  • Also, it removes to a large extent though not fully the need to continuously generate training data for the integrated intelligence as context is prebuilt along with meta tags and actual content.
  • This could be a larger standard under Mozilla / Apache Foundation or IETF or similar to enhance our web to the new world beyond simple search which is agents and LLMs / GAI / AI. Whole web could slowly become context aware along with content and meta tags. We are enhancing the META DATA itself on the web with this. All we have to do is add context and the SUPER AI like agents / LLMs / GAI will do the rest on their own.
  • Various plugins with governance and privacy for nonpublic sites could be thought off.