> For the complete documentation index, see [llms.txt](https://docs.nested-knowledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nested-knowledge.com/review-workflow/tagging/ai-tools-in-tagging.md). # AI Tools in Tagging Learn about the AI tools available in Tagging and when to use which. Nested Knowledge has three AI tools for tagging, and their names alone don't make the split between them obvious. They split cleanly along two questions: does the tool build the hierarchy, and does it extract the data? No two of them do the same combination. | Tool | Builds the hierarchy | Extracts the data | Reads | | --------------------- | ------------------------------------------------------------------ | ----------------------------------------------------------------------------------------- | ------------------------------------ | | Core Smart Tags | Yes — a fixed PICO, Study Type, Study Location, and Study Size set | Yes — generates values for every applicable study; recommend for review or apply directly | Abstracts only | | Smart Config: Tagging | Yes — a custom hierarchy drafted from your research question | No | — | | Adaptive Smart Tags | No | Yes — for any tag that isn't an unedited Core Smart Tags tag | Abstracts, Full texts or Supplements | **Core Smart Tags** alone builds and extracts in one step. Use **Recommend** to review values first, or **Apply** to apply them directly. Run it early, including during **Screening**, when its fixed set is useful. **Smart Config: Tagging** and hand-built hierarchies need **Adaptive Smart Tags** for extraction. Edited Core Smart Tags become regular tags, which **Adaptive Smart Tags** can extract. All three tools are meant to be combined and adjusted, not chosen between once and left alone. A typical nest ends up mixing all three: Core Smart Tags for the fixed set, Smart Config for a custom hierarchy on top of it, and Adaptive Smart Tags to extract that custom layer. Every tag any of them creates is a regular tag afterward — rename it, move it, change its question, or delete it, the same as a tag you built by hand. ### Core Smart Tags Builds and extracts a standard PICO, Study Type, Study Location, and Study Size hierarchy in one step, directly from every study's abstract. Run it early, after adding a search, when you need this fixed set.


Core Smart Tags	Build and extract a standard hierarchy from abstracts.	Core Smart Tags

### Smart Config: Tagging Drafts a custom, multi-level hierarchy from your research question. Review and edit its questions before extracting data.


Smart Config: Tagging	Draft a custom hierarchy from your research question.	Smart Config: Tagging

### Adaptive Smart Tags Extracts data from abstracts, full texts or supplements for hand-built, Smart Config-generated, imported, and edited Core Smart Tags tags.


Adaptive Smart Tags	Extract data from abstracts, full texts or supplements.	Adaptive Smart Tags

### Prompt Guidance: Tagging How a tag's question is worded affects how well Smart Config: Tagging and Adaptive Smart Tags can work with it. Review **Prompt Guidance** before finalizing wording for AI-assisted building or extraction.


Prompt Guidance	Write clear tag questions for AI-assisted extraction.	Prompt Guidance

### Next Steps


Configure Tagging	Set up a tag hierarchy for your extraction data.	Configure Tagging
Match Tags To Your Exports	Plan a tag hierarchy that matches your export columns.	Match Tags to your Exports
Core Smart Tags	Build and extract a standard PICO hierarchy from abstracts.	Core Smart Tags
Smart Config: Tagging	Generate a custom hierarchy from your research question.	Smart Config: Tagging
Adaptive Smart Tags	Extract custom tag data from abstracts, full texts or supplements.	Adaptive Smart Tags
Prompt Guidance: Tagging	Write clear tag questions for AI-assisted extraction.	https://app.gitbook.com/s/ImZjDBRRBE8RjPHvFXy6/ai-in-nested-knowledge/prompt-guidance
Apply Tags	Capture data from your included studies.	Apply Tags

### FAQs

Can I run Core Smart Tags and Smart Config: Tagging in the same nest?

Yes — they serve different purposes and don't conflict. Core Smart Tags produces its own fixed, already-extracted set of concepts; Smart Config drafts a separate, custom set of questions you extract later, typically with Adaptive Smart Tags.

Do I need to turn on Smart Tags separately for each of these tools?

No — a single **Smart Tags** setting in Nest Settings controls availability for all three.

Why would I run Adaptive Smart Tags on a Core Smart Tags concept?

You wouldn't, unless you'd already edited that tag — editing a Core Smart Tags tag converts it into a regular, human-created tag, which is what makes it eligible for Adaptive Smart Tags. An untouched Core Smart Tags tag already has its data from Core Smart Tags' own extraction.

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.nested-knowledge.com/review-workflow/tagging/ai-tools-in-tagging.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.