心臓、脳、ニューロン向け人体解剖図プロンプト20選

<think>The user wants me to translate an article fragment from English to Japanese. Let me carefully follow all the rules:

1. Keep ALL markdown syntax intact
2. Keep every URL, image path, and HTML tag EXACTLY as-is
3. Keep code blocks and inline code untranslated
4. Keep "GLMImage" untranslated
5. Use native, fluent Japanese expression
6. Output ONLY the translated markdown

Let me translate the content:

The image alt text describes a human heart frontal cutaway - I should translate this to Japanese but keep the image URL.

The main content talks about anatomically correct heart cutaways, anatomy prompts, and a warning about AI-generated anatomy.

Let me translate carefully:

• "Human heart frontal cutaway with chambers, valves and great vessels labeled" → 「心室、心房、弁、大血管がラベル付けされた人体の心臓前面の断面図」
• "An anatomically correct heart cutaway" → 「解剖学的に正確な心臓の断面図」
• "four chambers, valves, great vessels, flow arrows" → 「四つの心腔、弁、大血管、血流の矢印」
• "from one prompt" → 「一つのプロンプトから」
• "This page collects 20 anatomy prompts at that standard: heart, brain, neurons, barriers, and organ systems." → 「このページでは、その水準の20個の解剖学プロンプトをまとめて紹介しています。心臓、脳、ニューロン、屏障、各種臓器系。」
• "Each prompt names its panels, quotes its labels, and carries a verify note" → 「各プロンプトはパネルの名称、ラベルの引用、検証ノートを備えています」
• "because anatomy is exactly where AI illustration earns trust or loses it." → 「なぜなら、解剖学はまさにAIイラストが信頼を得るか失うかの分かれ目だからです。」
• "[Open the anatomy presets]" → 「[解剖学プリセットを開く]」
• "[Medical illustration guide]" → 「[医療イラストガイド]」
• "[Biology prompt pack]" → 「[生物学プロンプトパック]」
• "A warning before the prompts" → 「プロンプトを見る前の注意」
• "mirrored and subtly wrong anatomy" → 「左右反転や微妙に誤った解剖」
• "the most common AI failure in this discipline" → 「この分野で最も多いAIの失敗」
• "and it is plausible-looking" → 「しかも、一見もっともらしく見える」
• "that combination is why every entry below has a specific check" → 「この組み合わせがあるからこそ、以下の各項目には具体的なチェック項目を設けています」
• "For anything clinical, teaching-critical, or published" → 「臨床用、教育上重要、あるいは出版目的の場合は」
• "treat output as a draft and verify against an atlas" → 「出力は下書きとして扱い、解剖アトラスで検証してください」
• "Our verification guide covers the full protocol." → 「当社の検証ガイドでは完全なプロトコルを解説しています。」

Let me write this out properly in Japanese with natural flow.</think>

一つのプロンプトから生み出された、解剖学的に正確な心臓の断面図 ―― 四つの心腔、弁、大血管、血流の矢印までを描き切ります。このページでは、その水準に達した20個の解剖学プロンプトをまとめて紹介しています。心臓、脳、ニューロン、各種屏障、そして臓器系まで。各プロンプトはパネルの名称を明示し、ラベルをそのまま引用し、検証ノートを添えています。なぜなら、解剖学はまさにAIイラストが信頼を得るか、失うかの分かれ目になる領域だからです。

解剖学プリセットを開く · 医療イラストレーションガイド · 生物学プロンプトパック

プロンプト一覧の前に、ひとつ警告をしておきます。左右が反転していたり、微妙に間違った解剖が描かれていたりする――これがこの分野で最も多いAIの失敗例であり、しかも「それっぽく見える」のが厄介なところです。この組み合わせがあるからこそ、以下のすべての項目に具体的な検証チェックを付けてあります。臨床利用、教育上クリティカルな用途、出版目的の場合は、出力をあくまで下書きとして扱い、必ず解剖アトラスで照合してください。当社の検証ガイドで、その完全なプロトコルを解説しています。

<think>The user wants me to translate a fragment of an article into Japanese. The fragment is very short - just "## Heart and circulation" which is a heading. I need to translate this into natural Japanese while keeping the markdown syntax intact.

"Heart and circulation" in Japanese would be "心臓と循環" or "心臓と循環器系". Since this is about health/medical content (given it's GLMImage which seems to be a medical/health blog), I'll use natural Japanese medical terminology.

Let me keep the markdown syntax (##) intact and translate the content.</think>

心臓と循環

<think>The user wants me to translate a blog fragment about human heart blood flow into natural, fluent Japanese. Let me carefully translate this while maintaining all the markdown syntax, URLs, image paths, HTML tags, code blocks, and the brand name "GLMImage".

Let me translate:

1. "Human heart blood flow" - ヒトの心臓の血流
2. The code block contains a prompt for image generation - I should keep this untranslated but the instructions say to translate only comments inside them when trivially safe. However, this is a prompt description, not code comments. Looking at the rules again: "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)." So I should keep the code block as-is since it's not actual code with comments.
3. "Verify:" - 検証: or 確認:
4. The description about oxygenated/deoxygenated blood flow.

Let me write this out in natural Japanese:

• Heading: ヒトの心臓の血流
• Code block: keep as-is (it's a prompt, not code with comments)
• The verification text needs natural Japanese translation

"right side = deoxygenated (blue), left = oxygenated (red); the pulmonary artery carries blue blood and the pulmonary vein red — the one fact every generated heart gets wrong first."

Translation: 右側 = 脱酸素（青色）、左側 = 酸素化（赤色）；肺動脈は青色の血液を運び、肺静脈は赤色の血液を運ぶ — これは生成された心臓が最初に間違える唯一のポイント。

Let me make this more natural in Japanese:
右側が脱酸素血（青）、左側が酸素化血（赤）。肺動脈は青い血液を運び、肺静脈は赤い血液を運ぶ — これはAI生成の心臓画像がほぼ必ずといっていいほど最初につまずくポイントだ。

Actually, let me reconsider. The original says "every generated heart gets wrong first" - meaning this is the first thing that goes wrong. Let me phrase it naturally:

右側 = 脱酸素血（青）、左側 = 酸素化血（赤）。肺動脈は青色の血液を、肺静脈は赤色の血液を運ぶ — これは生成された心臓画像が真っ先に間違えるポイントだ。

Or even more natural:
右側が脱酸素血（青）、左側が酸素化血（赤）で、肺動脈が青色の血液を、肺静脈が赤色の血液を運ぶ — 実は、生成された心臓画像がほぼ例外なく最初に間違えるのはここだ。

Let me finalize the translation. I'll make sure the italic formatting (artery and vein) is preserved.

For the title in the code: "THE HUMAN HEART" - this is inside the code block so it should remain untranslated.

Final version:

1. ヒトの心臓の血流

An anatomically correct frontal cutaway of the human heart showing blood flow, with
oxygenated and deoxygenated paths, a small valve close-up and directional arrows.
Label "RIGHT ATRIUM", "RIGHT VENTRICLE", "LEFT ATRIUM", "LEFT VENTRICLE", "AORTA",
"PULMONARY ARTERY". Title: "THE HUMAN HEART".

検証: 右側 = 脱酸素血（青）、左側 = 酸素化血（赤）。肺動脈は青色の血液を、肺静脈は赤色の血液を運ぶ — 実は、生成された心臓画像が真っ先に間違えるのがこの一点だ。

I think this is good. Let me also think about whether "Verify" should be translated - yes, it should be 検証.

Actually, looking again at the original text "the one fact every generated heart gets wrong first" - this means "the one fact that every generated heart gets wrong first" - it's the first thing they get wrong. So my translation captures this.

Let me refine once more for naturalness:

右側が脱酸素血（青）、左側が酸素化血（赤）。肺動脈は青、肺静脈は赤の血液を運ぶ — これは生成された心臓画像が真っ先に間違える、定番のミスだ。

This sounds natural. Let me finalize.</think>

1. ヒトの心臓の血流

An anatomically correct frontal cutaway of the human heart showing blood flow, with
oxygenated and deoxygenated paths, a small valve close-up and directional arrows.
Label "RIGHT ATRIUM", "RIGHT VENTRICLE", "LEFT ATRIUM", "LEFT VENTRICLE", "AORTA",
"PULMONARY ARTERY". Title: "THE HUMAN HEART".

検証: 右側が脱酸素血（青）、左側が酸素化血（赤）。肺動脈は青、肺静脈は赤の血液を運ぶ — これは生成された心臓画像が真っ先に間違える、定番のミスだ。

<think>The user wants me to translate an article fragment into natural, fluent Japanese. Let me analyze the content:

1. This is about a medical atlas plate showing the human heart and circulation
2. It contains a code block with a description of an image to be generated
3. It has a verification note at the end

I need to:

• Translate the text into natural Japanese
• Keep the code block content as-is (no translation of code)
• Keep all markdown syntax
• Keep the brand name "GLMImage" untranslated (though it doesn't appear here)
• Output only the translated markdown

Wait - looking at the rules again: "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)."

So the code block should remain untranslated. Let me re-read...

The code block contains what appears to be an image generation prompt in English. Since it's a code block, I should keep it untranslated.

But wait, looking more carefully at the structure - the first part under "### 2. Cardiovascular atlas plate" is the code block content, and then the Verify: section is outside the code block.

Let me translate:

• "Cardiovascular atlas plate" → 心血管アトラス図版 or 心臓血管アトラスの図版
• The Verify: section needs translation

Actually, looking at the structure again:

• The code block contains the image description/prompt
• The Verify: line is outside the code block and needs translation

Let me write this in natural Japanese:

### 2. 心血管アトラス図版

[unchanged code block]

**確認事項:**僧帽弁は左側、三尖弁は右側に配置されているか。冠状動脈は心臓の*表面*に描かれており、心室内には描かれていないか。

Wait, I need to keep the code block content exactly as it is - untranslated. So the image description stays in English.

Let me reconsider the heading translation. "Cardiovascular atlas plate" - in medical Japanese, this could be:

• 心血管アトラス図版
• 心臓・血管アトラスの図版

I think 心血管アトラス図版 is most natural and concise.

For the Verify section, "mitral valve on the left, tricuspid on the right; coronary arteries on the heart surface, not inside chambers."

Translation: 僧帽弁は左、三尖弁は右に配置され、冠状動脈は心室内ではなく心臓の表面に描かれていること。

Let me also keep the bold and italic markers. The original has Verify: with bold, and surface with italic.

Let me finalize:

### 2. 心血管アトラス図版

A comprehensive medical-atlas plate of the human heart and circulation: a large
anatomically accurate frontal cutaway with all four chambers and valves, the
coronary arteries traced on the surface, the great vessels entering and leaving,
one magnified valve inset showing leaflet detail, one coronary cross-section inset,
and a compact schematic of the pulmonary and systemic loops with red and blue flow
arrows. Label "RIGHT ATRIUM", "LEFT VENTRICLE", "AORTA", "MITRAL VALVE", "CORONARY
ARTERY". Title: "THE HEART AND CIRCULATION".

**確認事項:** 僧帽弁は左、三尖弁は右に配置されているか。冠状動脈は心臓の*表面*に描かれており、心室内には描かれていないか。

Hmm, let me make it more natural Japanese:

確認: 僧帽弁が左側に、三尖弁が右側にあるか。冠状動脈は心室内ではなく、心臓の表面に描かれているか。

Actually, the original "Verify:" is more like a directive/instruction. Let me think...

"Verify:" as a header/label in this context seems to be a checklist item - "verify that [these things are correct]".

A natural Japanese translation would be:

• 確認: 僧帽弁が左、三尖弁が右にあること。冠状動脈は心室内ではなく心臓の表面に描かれていること。
• 検証: 僧帽弁は左、三尖弁は右にあるか。冠状動脈は心臓の表面に描かれ、心室内にはないか。

I think the second style (using か) is more natural for a verification checklist. Let me go with that.

Final version:

### 2. 心血管アトラス図版

A comprehensive medical-atlas plate of the human heart and circulation: a large
anatomically accurate frontal cutaway with all four chambers and valves, the
coronary arteries traced on the surface, the great vessels entering and leaving,
one magnified valve inset showing leaflet detail, one coronary cross-section inset,
and a compact schematic of the pulmonary and systemic loops with red and blue flow
arrows. Label "RIGHT ATRIUM", "LEFT VENTRICLE", "AORTA", "MITRAL VALVE", "CORONARY
ARTERY". Title: "THE HEART AND CIRCULATION".

**確認:** 僧帽弁は左、三尖弁は右にあるか。冠状動脈は心臓の*表面*に描かれ、心室内には描かれていないか。

This looks good. Let me check the rules one more time:

1. Keep ALL markdown syntax intact ✓
2. Keep URLs/image paths/HTML tags as-is - none in this fragment
3. Keep code blocks untranslated ✓
4. Keep "GLMImage" untranslated - not present
5. Native, fluent expression ✓
6. Output ONLY the translated markdown ✓

I think this is good.</think>

2. 心血管アトラス図版

A comprehensive medical-atlas plate of the human heart and circulation: a large
anatomically accurate frontal cutaway with all four chambers and valves, the
coronary arteries traced on the surface, the great vessels entering and leaving,
one magnified valve inset showing leaflet detail, one coronary cross-section inset,
and a compact schematic of the pulmonary and systemic loops with red and blue flow
arrows. Label "RIGHT ATRIUM", "LEFT VENTRICLE", "AORTA", "MITRAL VALVE", "CORONARY
ARTERY". Title: "THE HEART AND CIRCULATION".

確認: 僧帽弁は左、三尖弁は右にあるか。冠状動脈は心臓の表面に描かれ、心室内には描かれていないか。

<think>The user wants me to translate an article fragment into natural, fluent Japanese. Let me carefully analyze the content:

1. There's a heading "### 3. Heart anatomy QA comparison" - this needs to be translated to Japanese
2. There's a code block that contains an image description/prompt - this should NOT be translated (code blocks stay untranslated per rule 3, though only comments would be translatable - this is a description, not really a comment, so I'll keep it as-is)
3. Wait, looking again - the code block contains a description of an image. According to rule 3, code blocks should be kept untranslated. But this looks like it's actually content describing an image, not code. Let me reconsider.

Actually, looking at the format more carefully, this appears to be an image description/alt text or prompt that's wrapped in a code block. The rules say to keep code blocks untranslated, but this is descriptive text. However, since it's in a code block, I should keep it as-is.

Wait, re-reading rule 3: "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)." So I should keep the code block content untranslated.

But actually, this seems to be an image description/caption that happens to be in a code block format. In the context of the article, it's describing an image. Let me think about this more carefully.

Looking at the structure:

• Heading: "### 3. Heart anatomy QA comparison"
• Code block with image description
• Paragraph text: "Use this one in teaching about AI anatomy — it shows what the failure actually looks like."

The paragraph text needs to be translated. The heading needs to be translated. The code block... given that it's clearly an image description/prompt for the image, and considering this is a blog post about images (GLMImage), this is likely meant to be an image caption or alt text.

Hmm, but the rule is clear: keep code blocks untranslated. I'll keep it as-is.

Actually, wait. Let me look again. The text inside the code block describes an image - it's basically saying "compare two heart cutaways, version A vs version B, with labels, etc." This is image generation prompt or image description.

Given the rules, I should keep code blocks untranslated. So I'll keep that as-is.

Let me translate:

Heading: "### 3. Heart anatomy QA comparison" → "### 3. 心臓解剖学のQA比較"

Wait, "QA" here likely means "Quality Assurance" or "Question Answering" or just "comparison" based on context. Given the context "QA comparison", it could mean "Quality Assurance comparison" or in Japanese medical imaging context, it could be a comparison/check. Let me translate as "心臓解剖学のQA比較" or perhaps "心臓解剖学の品質保証比較". Actually, looking at the context more carefully, "QA comparison" in this AI/image generation context likely means a quality check comparison. I'll go with "心臓解剖学のQA比較" which is natural in Japanese tech contexts.

Actually, "QA" in Japanese tech contexts often stays as "QA" (Quality Assurance). So "心臓解剖学のQA比較" works well.

Paragraph: "Use this one in teaching about AI anatomy — it shows what the failure actually looks like."
Translation: "AIによる解剖学について教える際にこの画像を使いましょう——実際の失敗がどのように見えるかを示しています。"

Wait, I need to preserve the italic formatting: about
So: "AIによる解剖学について教える際にこの画像を使いましょう——実際の失敗がどのように見えるかを示しています。"

Or more naturally: "AIによる解剖学について教える際にこれを使用してください——実際の失敗がどのように見えるかを示しています。"

Hmm, the original has "teaching about AI anatomy" - the italic is around "about". So the emphasis is on "about" - meaning teaching about AI anatomy (not teaching AI). Let me preserve that:

"AI解剖学について教える際にこの画像を使用してください——実際の失敗がどのように見えるかを示しています。"

With the italic preserved: "AI解剖学について教える際にこの画像を使用してください——実際の失敗の見え方を示しています。"

Wait, let me re-read: "Use this one in teaching about AI anatomy — it shows what the failure actually looks like."

The italic is on "about". So the sentence is: "Use this one in teaching about AI anatomy — it shows what the failure actually looks like."

Translation with italic preserved on "について" or equivalent:
"AI解剖学について教える際にこの画像を活用してください——実際の失敗の具体例を示しています。"

Or: "AI解剖学について教える際にこの画像を使用してください——失敗が実際にどのように見えるかを示しています。"

Let me think about the natural Japanese flow. The sentence is somewhat casual/instructional.

"AIによる解剖学の教育でこの画像を活用しましょう——AIが実際にどのような失敗をするかを示しています。"

With italic on appropriate word. Since "about" is italicized, in Japanese I could italicize "について" but that might look odd. I could italicize the whole phrase about AI anatomy, or restructure.

Actually, looking at it again, the emphasis on "about" suggests contrast with "teaching AI anatomy" vs "teaching ABOUT AI anatomy". In Japanese, this distinction might be hard to capture. Let me just keep it natural:

"AI解剖学の教育にこの画像を活用しましょう——実際の失敗例を具体的に示しています。"

Hmm, that changes the meaning slightly. Let me try:
"AIによる解剖学の説明でこの画像を使用しましょう——実際の失敗例を示しています。"

Or more faithful:
"AI解剖学について教える際にこの画像を活用してください——実際の失敗の様相を示しています。"

I think the most natural would be to translate it as:
"AIによる解剖学の教育でこの画像を活用しましょう——AIが実際にどのような失敗をするかを示しています。"

But I need to preserve italic. The word "about" emphasizes that this is teaching ABOUT AI anatomy (the subject of AI doing anatomy), not teaching anatomy TO AI.

Let me try: "AI解剖学について教える際にこの画像を活用しましょう——AIが実際にどのような失敗をするかを示しています。"

Hmm. Let me just go with:
"AI解剖学について教える際にこの画像を活用しましょう——AIが実際にどのような失敗をするかを示しています。"

Actually, I think the most natural Japanese that preserves the intent and the italic:

"AIによる解剖学教育でこの画像を活用しましょう——AIが実際にどのように失敗するかを示しています。"

Wait, I'm overcomplicating this. Let me re-read the original carefully:

"Use this one in teaching about AI anatomy — it shows what the failure actually looks like."

The italic "about" emphasizes the topic. The translation should preserve this emphasis somehow.

Best translation:
"AI解剖学について教える際にこの画像を使いましょう——AIが実際にどのように失敗するかを示しています。"

Or with "について" italicized:
"AI解剖学について教える際にこの画像を使いましょう——AIの失敗が実際にどのように見えるかを示しています。"

I'll go with italicizing "について" as it preserves the emphasis on the topic/preposition:

"AI解剖学について教える際にこの画像を活用しましょう——AIが実際にどのような失敗をするかを示しています。"

Let me finalize:

3. 心臓解剖学のQA比較

A QA comparison of two generated heart cutaways: version A with four chambers
correctly placed, version B with mirrored chambers and a stray vessel, each error
circled in red with short correction notes. Label "CORRECT", "FLAWED".
Title: "TRUST BUT VERIFY".

AI解剖学について教える際にこの画像を活用しましょう——AIが実際にどのような失敗をするかを示しています。

Actually, I should reconsider the code block. This is described as an "image description" or similar - in GLMImage context, this might be the prompt used to generate the image. The rule says to keep code blocks untranslated. So I'll keep it.

Wait, I want to reconsider once more. The code block contains:
"A QA comparison of two generated heart cutaways: version A with four chambers
correctly placed, version B with mirrored chambers and a stray vessel, each error
circled in red with short correction notes. Label "CORRECT", "FLAWED".
Title: "TRUST BUT VERIFY"."

This is clearly an image description/alt text, likely for accessibility or for the image generation tool. Since it's in a code block, per rule 3, I should keep it untranslated.

Final translation:

3. 心臓解剖学のQA比較

A QA comparison of two generated heart cutaways: version A with four chambers
correctly placed, version B with mirrored chambers and a stray vessel, each error
circled in red with short correction notes. Label "CORRECT", "FLAWED".
Title: "TRUST BUT VERIFY".

AI解剖学について教える際にこの画像を活用しましょう——AIが実際にどのような失敗をするかを示しています。

Let me review once more for naturalness and accuracy.

"Use this one" - "この画像を使いましょう" or "この画像を活用しましょう" - both natural
"in teaching" - "教える際に" or "教育で"
"about AI anatomy" - "AI解剖学について" with italic on "について"
"—" - "——" (Japanese em dash)
"it shows" - "示しています"
"what the failure actually looks like" - "実際の失敗の見え方" or "AIが実際にどのような失敗をするか"

I think my translation is good. Let me finalize.

One more consideration: "TRUST BUT VERIFY" is a phrase that could be kept in English or translated. In Japanese business/tech contexts, it's often kept as "トラスト・バット・ベリファイ" or simply kept in English. Given the context and that it appears in quotes in the code block (which I'm keeping untranslated), I'll keep the code block as is.

Also, "CORRECT" and "FLAWED" are labels in the image, kept in English in the original.

Final answer:

3. 心臓解剖学のQA比較

A QA comparison of two generated heart cutaways: version A with four chambers
correctly placed, version B with mirrored chambers and a stray vessel, each error
circled in red with short correction notes. Label "CORRECT", "FLAWED".
Title: "TRUST BUT VERIFY".

AI解剖学について教える際にこの画像を活用しましょう——AIが実際にどのような失敗をするかを示しています。</think>

3. 心臓解剖学のQA比較

A QA comparison of two generated heart cutaways: version A with four chambers
correctly placed, version B with mirrored chambers and a stray vessel, each error
circled in red with short correction notes. Label "CORRECT", "FLAWED".
Title: "TRUST BUT VERIFY".

AI解剖学について教える際にこの画像を活用しましょう——AIが実際にどのような失敗をするかを示しています。

<think>The user wants me to translate the article fragment "Brain and neurons" into Japanese. This is a very short fragment - just a heading. Let me translate it naturally into Japanese.

"Brain and neurons" → "脳とニューロン" or "脳と神経細胞"

In Japanese, "neurons" can be translated as either "ニューロン" (loanword) or "神経細胞" (native term). For a more academic/scientific blog style, "ニューロン" is commonly used in modern contexts. However, "神経細胞" is also perfectly natural.

Let me go with "脳とニューロン" as it's more concise and commonly used in Japanese tech/science blogs.

Since this is just a heading (h2), I should output only the markdown heading.</think>

脳とニューロン

<think>The user wants me to translate a fragment of an article into Japanese. The fragment contains:

1. A heading "### 4. Four specialized cells"
2. A code block describing an image with specialized cells
3. An image with markdown alt text and URL
4. A verification note about the neuron

Let me translate this carefully into natural Japanese while keeping all markdown syntax intact, URLs unchanged, code blocks untranslated, etc.

Let me think about the translations:

• "Four specialized cells" → 「4つの特殊化した細胞」or 「4種類の専門細胞」
• The code block contains the image description - I should keep it untranslated since it's a code block (image prompt), but actually the rules say "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)". Hmm, but this is more of an image description in a code block. Let me keep it as is since it's a code block.
• Wait, looking again - the user has provided code blocks for image generation prompts. These should remain untranslated.
• The image markdown with alt text "Four specialized cells including a neuron with long axon" - I should translate the alt text? Actually, looking at rules again - "Keep every URL, image path, and HTML tag EXACTLY as-is." Alt text is not specifically mentioned, but it's part of the markdown image syntax. I think I should keep it as-is since it's a technical description that matches the image prompt.
• The "Verify:" note - I need to translate this.

Let me reconsider the code blocks. They appear to be image generation prompts in English. The rules say to keep code blocks untranslated. So I'll keep them as is.

For the "Verify:" part - this is a verification note for the image. I'll translate it to Japanese.

Let me write the translation:

4. 4種類の専門細胞

A comparative row of four specialized cells at matching scale: a neuron with
dendrites and long axon, a red blood cell as a biconcave disc, a sperm cell, and a
macrophage spreading pseudopods, each with two functional labels.
Title: "CELL SPECIALISTS".

確認: ニューロン — 多数の短い樹状突起と、1本の長い軸索。描画で軸索が2本になっている場合は再生成してください。

Hmm, let me reconsider the alt text. The rule says "Keep every URL, image path, and HTML tag EXACTLY as-is. Do not translate or alter them." Alt text is technically not URL or HTML tag. However, since the alt text describes the image and is in English matching the code block prompt, I'll keep it as-is to maintain the technical integrity. Actually, the alt text is descriptive content for the image, so it could be translated. But I think it's safer to keep it as is since it matches the image prompt content.

Let me reconsider - looking at typical translation conventions for blog localization, alt text is often translated since it's user-facing. But the rule says to keep URLs and HTML tags as-is. Alt text falls in between. I'll translate it to be consistent with the Japanese context.

Actually, looking more carefully - the rule says "Keep every URL, image path, and HTML tag EXACTLY as-is." This is specifically about URLs, image paths, and HTML tags. Alt text is technically the descriptive text shown when an image can't be loaded, and is often translated. Let me translate it.

Actually, I'm going to translate the alt text since it's user-facing descriptive content.

Let me finalize:

4. 4種類の専門細胞

A comparative row of four specialized cells at matching scale: a neuron with
dendrites and long axon, a red blood cell as a biconcave disc, a sperm cell, and a
macrophage spreading pseudopods, each with two functional labels.
Title: "CELL SPECIALISTS".

確認: ニューロン — 多数の短い樹状突起と、1本の長い軸索。描画で軸索が2本になっている場合は再生成してください。

That looks good. Let me double-check everything.

The heading translates well.
The code block is kept as-is per the rules.
The image markdown URL is unchanged.
The alt text is translated.
The verify note is translated.

Wait, I should think about whether to translate the alt text or not. Looking at it again - the alt text is part of the image markdown, and the rule says "Keep every URL, image path, and HTML tag EXACTLY as-is." Alt text is not technically a URL, image path, or HTML tag. It's content within the markdown image syntax. I think translating it is appropriate for a Japanese reader.

Final answer looks good.</think>

4. 4種類の専門細胞

A comparative row of four specialized cells at matching scale: a neuron with
dendrites and long axon, a red blood cell as a biconcave disc, a sperm cell, and a
macrophage spreading pseudopods, each with two functional labels.
Title: "CELL SPECIALISTS".

確認: ニューロン — 樹状突起は多数で短く、軸索は1本で長いこと。描画で軸索が2本になっている場合は再生成してください。

<think>The user wants me to translate an article fragment into Japanese. Let me analyze the content:

1. It's about a "Hippocampus memory circuit" diagram
2. There's a code block describing the figure
3. There's an image with alt text
4. There's a verification note

I need to:

• Keep all markdown syntax intact
• Keep URLs and image paths exactly as-is
• Keep code blocks untranslated (translate only comments if trivially safe)
• Keep "GLMImage" untranslated
• Use natural Japanese

Let me translate:

"5. Hippocampus memory circuit" → "5. 海馬の記憶回路"

The code block contains an image description (alt text). Looking at it, it's not really code - it's a description in a code block. I should keep it untranslated as per the rules, but actually, this looks like it's describing an image. The rules say "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)."

Hmm, but this is in a code block that's actually just text description. Let me look again - it does appear to be code-blocked text. I should keep it untranslated per the rules.

Wait, looking more carefully - this seems to be a prompt/description for an image, formatted as a code block. The instructions say code blocks should be kept untranslated. So I'll keep it as-is.

For the image alt text: "Hippocampal memory circuit from entorhinal cortex to CA1 labeled" - this is in an image markdown, which contains alt text. The image path should stay, but alt text could be translated. Actually, alt text is typically translated for accessibility. Let me translate it to Japanese.

For the verify note: "Verify: the loop order entorhinal → dentate → CA3 → CA1 → subiculum; arrows all one way around the loop." → This should be translated to Japanese.

Let me write the translation:

5. 海馬の記憶回路

A hippocampal circuit figure: entorhinal cortex input entering the dentate gyrus,
the CA3-CA1 trisynaptic loop, and output via the subiculum, with a
long-term-potentiation inset showing synaptic strengthening spikes.
Label "ENTORHINAL", "DENTATE GYRUS", "CA3", "CA1", "LTP". Title: "MEMORY CIRCUIT".

確認: ループの順序は内嗅皮質 → 歯状回 → CA3 → CA1 → 海馬支脚; 矢印はすべてループを一方向に回っている。

Let me reconsider. The code block content looks like it might be a prompt for image generation. The rules say keep code blocks untranslated. So I should keep it as-is.

Actually, I should be more careful here. Looking at the code block content, it's not really code - it's an image description/prompt. But it IS formatted as a code block. Per the rules, I'll keep it untranslated.

For the bold verify line, I'll translate it.

Let me finalize my translation.</think>

5. 海馬の記憶回路

A hippocampal circuit figure: entorhinal cortex input entering the dentate gyrus,
the CA3-CA1 trisynaptic loop, and output via the subiculum, with a
long-term-potentiation inset showing synaptic strengthening spikes.
Label "ENTORHINAL", "DENTATE GYRUS", "CA3", "CA1", "LTP". Title: "MEMORY CIRCUIT".

確認: ループの順序は内嗅皮質 → 歯状回 → CA3 → CA1 → 海馬支脚; 矢印はすべてループを一方向に回っている。

<think>The user wants me to translate an article fragment about Alzheimer pathology into Japanese. Let me carefully translate while keeping all markdown syntax, URLs, and technical terms intact.

The content includes:

1. A heading "6. Alzheimer pathology"
2. A code block with a description of the image
3. An image with alt text and URL
4. A verification note

Let me translate this naturally into Japanese:

• "Alzheimer pathology" → "アルツハイマー病理"
• The code block contains a prompt that should remain untranslated (translate only comments if trivially safe - there are no comments here, so keep as-is)
• The alt text describes the image
• "Verify:" → "確認:" or "検証:"
• The note about plaques and tangles needs accurate translation

Let me be careful with technical terms:

• amyloid plaques = アミロイド斑
• neurofibrillary tangles = 神経原線維変化
• hippocampus = 海馬
• extracellular = 細胞外
• intracellular = 細胞内
• neurons = ニューロン / 神経細胞

For the code block, since it's a prompt (likely used for image generation), I should keep it in English as per the rules. Actually, looking again at the rules - "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)." There are no comments in this code block, so I should keep it untranslated.

Wait, let me reconsider. The code block is just descriptive text wrapped in a code fence. It doesn't appear to be actual code. However, the rule says "Keep code blocks and inline code untranslated". So I'll keep it as-is.

Let me translate:

6. Alzheimer pathology → ### 6. アルツハイマー病理

For the verify note:
"plaques extracellular, tangles intracellular — the two get swapped surprisingly often."
→ "プラークは細胞外、 tangle（神経原線維変化）は細胞内 — この二つは意外とよく取り違えられます。"

Actually, let me use proper Japanese medical terminology:

• プラーク (plaque)
• 神経原線維変化 (neurofibrillary tangle) - or just tangle as it's a common term

Let me finalize the translation.</think>

6. アルツハイマー病理

A coronal brain section highlighting the hippocampus in Alzheimer disease, with
amyloid plaques as small extracellular deposits and neurofibrillary tangles inside
neurons, plus one magnified inset of a plaque and a tangle. Label "HIPPOCAMPUS",
"PLAQUE", "TANGLE", "NEURON". Title: "ALZHEIMER PATHOLOGY".

確認点: プラークは細胞外、tangle（神経原線維変化）は細胞内です — この二つは意外にもよく取り違えられます。

<think>The user wants me to translate an article fragment about synapse pruning into natural, fluent Japanese. I need to:

1. Keep all markdown syntax intact
2. Keep URLs and image paths exactly as-is
3. Keep code blocks untranslated (but can translate comments if trivially safe)
4. Keep "GLMImage" untranslated
5. Use native, fluent Japanese
6. Output only the translated markdown

Let me translate the content:

The heading "7. Synapse pruning" → "7. シナプス刈り込み"

The code block content describes an image generation prompt. This should be kept as-is since it's a code block, but I could translate the English description inside it. Actually, looking at the rules more carefully: "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)."

The code block here appears to be a prompt description, not actual code. It's inside triple backticks. I should probably keep it as-is or could consider it a comment. Let me keep it untranslated since it's in a code fence - actually, looking at it again, this is just descriptive text wrapped in code fences. I think the safest interpretation is to keep it as code (untranslated) since the instructions say "Keep code blocks... untranslated."

Wait, let me re-read: "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)."

So I should keep code blocks untranslated. The text inside is not in comment syntax (like // or #), so I should leave it as English.

Actually, this looks like it might be a prompt for image generation. The block fence is being used to format this prompt. Since the rule says to keep code blocks untranslated, I'll leave the English content inside.

The image alt text: "Synapse pruning figure with microglia removing weak synapses" - this is inside an image markdown. The URL must stay exact. The alt text - should I translate it? The rules say "Keep every URL, image path, and HTML tag EXACTLY as-is. Do not translate or alter them." This refers to URLs and HTML tags. The alt text is descriptive text. I think I should translate it to Japanese for accessibility, as it's user-facing text, not a URL/HTML tag/technical element.

Let me translate: "Synapse pruning figure with microglia removing weak synapses" → "マイクログリアが弱いシナプスを除去しているシナプス刈り込みの図"

Let me finalize the translation:

7. Synapse pruning

7. シナプス刈り込み

Code block - keep as-is (English)

Image with translated alt text:
</think>

7. シナプス刈り込み

A developmental neuroscience figure: an over-wired neonatal dendrite with many weak
synapses, microglia tentacles tasting and removing the weak ones, and the refined
adolescent circuit with fewer strong connections, plus a density curve inset.
Label "DENDRITE", "MICROGLIA", "WEAK SYNAPSE", "STRONG SYNAPSE".
Title: "PRUNING THE BRAIN".

<think>The user wants me to translate the heading "## Barriers and systems" into Japanese. This is a simple heading translation.

"Barriers and systems" in Japanese could be:

• 障壁とシステム
• バリアとシステム
• 障壁と仕組み

Given the context appears to be about image generation or technical content related to GLMImage, and considering natural Japanese expression, "障壁とシステム" or "バリアとシステム" would work. Let me go with the more natural "障壁とシステム" or perhaps "バリアと仕組み".

Actually, looking at this more carefully, in technical Japanese contexts, "システム" is commonly used as a loanword. So "障壁とシステム" would be a good translation.

However, since this is just a heading and I don't have more context, I'll provide a natural translation.</think>

障壁とシステム

<think>The user wants me to translate an article fragment about the blood-brain barrier into Japanese. Let me carefully translate while keeping all the markdown, URLs, code blocks, and specific terms intact.

Key rules:

• Keep ALL markdown syntax
• Keep URLs, image paths, HTML tags exactly as is
• Keep code blocks untranslated
• Keep "GLMImage" untranslated
• Natural Japanese
• Output only translated markdown

Let me translate:

• "Blood-brain barrier" = 血液脳関門
• "cross-section" = 断面図 / 断面
• The code block should remain in English
• The image caption and verification text need to be translated

Let me work through this carefully.

The code block contains English text describing the image - I should keep this untranslated as it's a prompt/code block.

The image alt text and URL should remain unchanged.

The "Verify" section needs translation.

Let me craft natural Japanese:

"血液脳関門" for blood-brain barrier
"断面図" for cross-section
"密着結合" for tight junctions
"内皮細胞" for endothelial cells
"基底膜" for basement membrane
"アストロサイト" for astrocyte
"ペリサイト" or "周皮細胞" for pericyte

The verification:

• tight junctions = 密着結合
• endothelial cells = 内皮細胞
• astrocyte end-feet = アストロサイトの終足
• brain side = 脳側
• outside the membrane = 膜の外側

Let me put this together.</think>

8. 血液脳関門

A cross-section of the blood-brain barrier: capillary endothelial cells joined by
tight junctions, the basement membrane, astrocyte end-feet wrapping the outside,
and a pericyte, with small molecules crossing while large proteins cannot.
Label "ENDOTHELIUM", "TIGHT JUNCTION", "BASEMENT MEMBRANE", "ASTROCYTE",
"PERICYTE". Title: "THE GATEKEEPER".

確認ポイント: 内皮細胞間の密着結合（これがバリアとなる構造です）；アストロサイトの終足が膜の外側、つまり脳側を取り囲んでいること。

<think>The user wants me to translate an article fragment into natural, fluent Japanese. The fragment appears to be a description/figure caption for an image about plaque burden in brain tissue. It includes a code block with what appears to be a description for generating an image.

Let me translate this carefully:

• The heading "9. Plaque burden in brain tissue" should be translated to Japanese
• The code block content should be kept as-is (code blocks untranslated), but the user said to translate comments inside them when trivially safe. Looking at this, it seems to be a description/prompt for image generation, not really code. However, it's in a code block, so I should keep it untranslated per the rules. Wait, let me re-read: "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)."

Actually, looking at this more carefully, this appears to be a figure description in a code block format, not actual code. But since it's in a code block, I'll keep it as-is. Actually, on reflection, this looks like it could be an image prompt. Let me keep it untranslated as instructed.

Wait, let me reconsider. The instruction says "Keep code blocks and inline code untranslated". So I'll keep the content of the code block as-is.

Let me translate the heading:
"9. Plaque burden in brain tissue" → "9. 脳組織におけるプラーク負荷"

Actually, let me make this more natural Japanese. "プラーク負荷" is acceptable but could be more natural. In medical/biology contexts, this might be better as "プラーク蓄積" or "プラーク沈着". Let me go with "プラーク負荷" as it's a direct translation and is used in Japanese medical literature.

The code block content should remain in English per the rules.

Let me finalize:

9. 脳組織におけるプラーク負荷

A cross-section of cerebral cortex tissue showing extracellular amyloid deposits,
dystrophic neurites around them, and a magnified inset detailing one deposit with
its dense core and diffuse halo. Label "CORTEX", "DEPOSIT", "DARK CORE", "HALO".

This should be the output. Let me double-check the rules:

1. Markdown syntax intact ✓
2. URLs/paths unchanged ✓ (none in this fragment)
3. Code blocks untranslated ✓
4. "GLMImage" not mentioned here, but kept untranslated ✓
5. Native fluent expression ✓
6. Output only translated markdown ✓

The output looks good.</think>

9. 脳組織におけるプラーク負荷

A cross-section of cerebral cortex tissue showing extracellular amyloid deposits,
dystrophic neurites around them, and a magnified inset detailing one deposit with
its dense core and diffuse halo. Label "CORTEX", "DEPOSIT", "DARK CORE", "HALO".

<think>The user wants me to translate an article fragment into Japanese. Let me analyze the content:

1. There's a section heading "Tau therapy strategies" - I need to translate this
2. There's a code block describing a figure with an image alt-text or description
3. There's a "Verify" section with bold text

Let me translate this naturally into Japanese while keeping all markdown syntax intact.

Key translations:

• "Tau therapy strategies" → "タウ療法戦略" or "タウタンパク質治療戦略"
• The code block content should be kept as-is (it's describing a figure)
• "Verify:" → "検証：" or "確認："

For the code block, the instructions say "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)." This is a code block but it's actually a description of an image/figure, not actual code. Looking at it more carefully, it seems to be an alt-text or description for an image. Since it's inside a code fence, I should keep it untranslated.

Actually, wait. Let me re-read the instructions: "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)."

The content inside the code fence is descriptive text about a figure. It's not really code, but it's inside a code fence. I think the safest interpretation is to keep it untranslated as instructed for code blocks.

However, the user might want this translated since it's part of the article content. Let me think... The instructions are clear: "Keep code blocks... untranslated". So I'll keep the code block as-is.

For the rest:

• "Verify:" with bold → "確認：" or "検証："

Let me write the translation:

10. タウ療法戦略

A two-path therapy figure for tau pathology: the upper path shows an antibody
binding tau outside the neuron to speed clearance, the lower path shows an
antisense oligonucleotide entering the neuron to reduce tau production, both
meeting at reduced tangle load. Label "ANTIBODY", "TAU", "ASO", "REDUCED TANGLES".
Title: "TARGETING TAU".

確認： 抗体はニューロンの外側に留まり、ASOはニューロン内に入る — この内外の区別こそが図の要点である。

Let me reconsider the translation of "tangle load" - this refers to the burden of neurofibrillary tangles. "REDUCED TANGLES" would be "減少したタングル" or "タングル負荷の軽減". The verification sentence should sound natural in Japanese.

Also, "speed clearance" → "クリアランスを促進する" or "除去を促進する"
"reduce tau production" → "タウ産生を減少させる" or "タウの生成を抑える"

But these are inside the code block, so they remain untranslated.

Let me finalize:

10. タウ療法戦略

A two-path therapy figure for tau pathology: the upper path shows an antibody
binding tau outside the neuron to speed clearance, the lower path shows an
antisense oligonucleotide entering the neuron to reduce tau production, both
meeting at reduced tangle load. Label "ANTIBODY", "TAU", "ASO", "REDUCED TANGLES".
Title: "TARGETING TAU".

確認： 抗体はニューロンの外側に留まり、ASOはニューロン内部に入る — この内外の区別こそが図の要点である。

This looks good. The translation is natural Japanese, all markdown syntax is preserved, the code block is untranslated, and the brand "GLMImage" isn't in this fragment anyway.</think>

10. タウ療法戦略

A two-path therapy figure for tau pathology: the upper path shows an antibody
binding tau outside the neuron to speed clearance, the lower path shows an
antisense oligonucleotide entering the neuron to reduce tau production, both
meeting at reduced tangle load. Label "ANTIBODY", "TAU", "ASO", "REDUCED TANGLES".
Title: "TARGETING TAU".

確認： 抗体はニューロンの外側に留まり、ASOはニューロン内に入る — この内外の区別こそが図の要点である。

<think>The user wants me to translate the article fragment "Immunology figures" into natural, fluent Japanese.

The fragment is just a heading: "## Immunology figures"

I need to translate this to Japanese while keeping the markdown syntax intact.

"Immunology figures" - this likely refers to "免疫学の図" or "免疫学関連の図" or "免疫学の数値". Given the context (a heading in what appears to be a research article about GLMImage), "免疫学の図" (Immunology figures) seems most appropriate.

Let me translate it as "免疫学の図" which is natural Japanese.

Since this is just a heading, I should output just the heading in markdown format.</think>

免疫学の図

<think>The user wants me to translate an article fragment about CAR-T manufacturing workflow into Japanese. Let me analyze what's in the fragment:

1. A heading "11. CAR-T manufacturing workflow"
2. A code block with English description about a five-step hospital workflow
3. An image with markdown image syntax
4. A caption/description for the image

I need to:

• Keep markdown syntax intact
• Keep URLs and image paths exactly as-is
• Keep code blocks untranslated (only translate comments if trivially safe)
• Keep "GLMImage" untranslated
• Output natural, fluent Japanese

The code block contains instructions for image generation - this is a prompt/specification, so I should keep it as-is per the rules (code blocks untranslated). Wait, let me re-read: "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)." So I keep the code block exactly as-is.

The image markdown should be kept as-is for the URL, but the alt text could potentially be translated. However, the rule says "Keep every URL, image path, and HTML tag EXACTLY as-is." The alt text is part of the markdown image syntax. Let me think... The alt text describes the image and is part of the markdown syntax for the image. Since the user says to keep markdown syntax intact, and alt text is part of image markdown, I should probably translate the alt text since it's content, not syntax. Actually, looking at it more carefully - the alt text "Five-step CAR-T manufacturing workflow labeled" is descriptive content for the image. I'll translate it to Japanese.

Let me craft the translation:

• Heading: "11. CAR-T manufacturing workflow" → "11. CAR-T製造ワークフロー"
• Code block: keep as-is (it's a prompt for image generation)
• Image markdown: translate the alt text but keep URL exact
  • "Five-step CAR-T manufacturing workflow labeled" → "5ステップのCAR-T製造ワークフローがラベル付けされた図"

Let me write the output now.</think>

11. CAR-T製造ワークフロー

A five-step hospital workflow for producing a patient's own CAR-T cells: blood
draw, T-cell separation in the lab, gene transfer with a viral vector, cell
expansion in a culture bag, and infusion back into the patient.
Label "LEUKAPHERESIS", "SELECTION", "GENE TRANSFER", "EXPANSION", "INFUSION".
Title: "CAR-T JOURNEY".

<think>The user wants me to translate an article fragment into Japanese. Let me analyze the content:

1. It's about CAR-T cell therapy in the body
2. There's a heading "12. CAR-T in the body"
3. There's a code block describing an end-to-end therapy figure
4. There's an image with alt text

Let me translate this naturally into Japanese while keeping all markdown syntax, URLs, and the brand name "GLMImage" intact.

For the heading: "CAR-T in the body" → "CAR-Tが体内で作用する"

For the code block - this is describing an image/figure, so the technical terms should remain. Let me think about this carefully:

• "An end-to-end therapy figure" - this describes a figure
• The labels are: "INFUSED CELLS", "ANTIGEN", "GRANZYME", "TUMOR CELL"
• Title: "CAR-T IN THE BODY"

Wait, the instructions say "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)." But this code block contains a description of an image, not actual code. Let me re-read...

Looking at it again, the code block contains a description/instructions for creating a figure. This isn't really code - it's more like a figure description. However, since it's in a code block, I should keep it untranslated according to rule 3. But the labels within (like "INFUSED CELLS") seem to be text that would appear in the image itself.

Hmm, this is a bit ambiguous. The labels inside quotes seem to be text labels that would appear on the figure. But they're inside a code block...

Actually, looking more carefully, this code block appears to be a prompt or description for generating an anatomy diagram. The labels in quotes would appear in the actual image. Since the image itself isn't translated (it's an image), these labels might stay in English on the image.

But wait - the user wants the article fragment translated. The text content should be translated. The code block content seems to be a prompt for image generation, which would include English text.

I think the safest interpretation is:

• The code block content represents instructions/prompts for an image, which would typically stay in English
• The labels in quotes are labels for the image
• The alt text should be translated

Let me re-read the rules:
"3. Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)."

So the code block should remain untranslated. The image alt text should be translated since it's not in a code block.

Let me translate the image alt text: "Engineered T cells attacking tumor cells, labeled" → "遺伝子改変T細胞が腫瘍細胞を攻撃する様子（ラベル付き）"

For the heading, I'll translate it to Japanese.

Actually, looking at this more carefully, I think the code block contains the prompt that was used to generate the image, and it should remain as-is. The translation should focus on the article text itself.

Let me also think about whether the image alt text should be translated. The rule says "Keep every URL, image path, and HTML tag EXACTLY as-is." but alt text isn't mentioned. I think it's reasonable to translate the alt text since it's descriptive content for the article.

Let me finalize my translation:

Heading: "12. CAR-T in the body" → "12. CAR-Tが体内で作用する"

Image alt text: "Engineered T cells attacking tumor cells, labeled" → "遺伝子改変T細胞が腫瘍細胞を攻撃する様子（ラベル付き）"

Code block: Keep as-is per rule 3

URL: Keep as-is per rule 2

Let me reconsider the heading translation. "CAR-T in the body" is the original heading. A natural Japanese translation could be:

• "12. 体内でのCAR-T"
• "12. CAR-Tの体内での作用"
• "12. 体内におけるCAR-T"

I'll go with "12. 体内におけるCAR-T" as it's natural Japanese.

Actually, the fragment is quite minimal. Let me make sure I'm translating everything properly. The content is:

1. A heading "12. CAR-T in the body"
2. A code block with figure description
3. An image with alt text

I'll keep the code block untranslated per rule 3, translate the heading, and translate the image alt text.

Wait - I should also think about whether to translate the alt text. The image is an anatomy diagram, and the alt text describes it for accessibility purposes. For a Japanese article, the alt text should ideally be in Japanese too. Let me translate it.

Let me draft the final output:

12. 体内におけるCAR-T

An end-to-end therapy figure: engineered T cells circulating in a vessel, exiting
into a tumor bed, recognizing their antigen, and destroying tumor cells by granzyme
release, with a small patient-silhouette inset locating the action.
Label "INFUSED CELLS", "ANTIGEN", "GRANZYME", "TUMOR CELL".
Title: "CAR-T IN THE BODY".

Hmm, actually, I'm second-guessing whether to translate the image alt text. Let me look at the rule again: "Keep every URL, image path, and HTML tag EXACTLY as-is. Do not translate or alter them."

The alt text isn't a URL, image path, or HTML tag - it's the descriptive text for the image. I think it's safe to translate. But to be extra safe, I could keep it as-is.

Actually, looking at professional localization practices, alt text should be translated for the target language to maintain accessibility. I'll translate it.

Let me refine my translation of the alt text: "Engineered T cells attacking tumor cells, labeled"

• "Engineered T cells" = "遺伝子改変T細胞" or "改変T細胞"
• "attacking tumor cells" = "腫瘍細胞を攻撃する"
• "labeled" = "ラベル付き"

Final translation: "改変T細胞が腫瘍細胞を攻撃する様子（ラベル付き）"

Actually, looking at the code block content once more - it's describing a figure prompt. The labels "INFUSED CELLS", "ANTIGEN", "GRANZYME", "TUMOR CELL" would appear on the actual image (which is in English). These are not part of the article's prose text - they're part of the image description. So keeping them in English makes sense.

Final answer:

12. 体内におけるCAR-T

An end-to-end therapy figure: engineered T cells circulating in a vessel, exiting
into a tumor bed, recognizing their antigen, and destroying tumor cells by granzyme
release, with a small patient-silhouette inset locating the action.
Label "INFUSED CELLS", "ANTIGEN", "GRANZYME", "TUMOR CELL".
Title: "CAR-T IN THE BODY".

</think>

12. 体内におけるCAR-T

An end-to-end therapy figure: engineered T cells circulating in a vessel, exiting
into a tumor bed, recognizing their antigen, and destroying tumor cells by granzyme
release, with a small patient-silhouette inset locating the action.
Label "INFUSED CELLS", "ANTIGEN", "GRANZYME", "TUMOR CELL".
Title: "CAR-T IN THE BODY".

<think>The user wants me to translate an article fragment about a bispecific antibody bridge into Japanese. This is a technical/scientific text about a bispecific T-cell engager mechanism. I need to:

1. Keep all markdown syntax intact
2. Keep URLs and image paths exactly as-is
3. Keep code blocks untranslated
4. Keep "GLMImage" untranslated
5. Use natural Japanese

Let me translate the content. The main text is a description in English that needs to be translated to Japanese, while the code block content (which is an image generation prompt) should be kept in English, and the image URL should stay as-is.

Let me think about the Japanese translation:

• "Bispecific antibody bridge" = 二重特異性抗体ブリッジ or 二重特異性抗体の橋渡し
• "A mechanism figure..." - this describes an image

The code block is a prompt for image generation, so I should keep it in English per the rules about code blocks.

Let me translate:

• Heading: "13. Bispecific antibody bridge" → "13. 二重特異性抗体ブリッジ"
• The descriptive text → translate to Japanese

Actually, looking more carefully, the text after the code block seems to be the main content. Let me translate it properly:

"A mechanism figure of a bispecific T-cell engager: one antibody arm binding CD3 on the T cell, the other arm binding a tumor antigen, pulling the two cells into a synapse where the T cell releases perforin."

This is the image caption/description. Let me translate to natural Japanese.

The labels in the prompt:

• "CD3 ARM" - keep in English since it's a label in the image
• "TUMOR ANTIGEN ARM" - keep in English
• "T CELL" - keep in English
• "TUMOR CELL" - keep in English
• "PERFORIN" - keep in English
• "BITE BRIDGE" - keep in English

Wait, the rule says to keep code blocks untranslated. The labels are inside the code block, so they should remain in English. Good.

The image alt text is in the markdown image syntax, which I'll keep as-is per the rules (URLs and image paths).

Let me draft the translation:

Heading: "13. 二重特異性抗体ブリッジ"

Then the code block stays as-is.

Then the image with the URL stays as-is.

But wait, the image alt text "Bispecific antibody bridging T cell and tumor cell labeled" - should this be translated? The rule says "Keep every URL, image path, and HTML tag EXACTLY as-is." Alt text isn't a URL or image path, but it's part of the markdown image syntax. Hmm. Looking at rule 2 more carefully: "Keep every URL, image path, and HTML tag EXACTLY as-is. Do not translate or alter them." The alt text is technically part of the image syntax but is a text attribute. I think it's safer to translate it since it's visible content, not a URL. Actually, looking at the structure - the alt text describes the image content. In many localization contexts, alt text is translated. But the rule specifies URLs, image paths, and HTML tags. The alt text is text content within the image markdown, so I'll translate it.

Actually, let me re-read: "Keep every URL, image path, and HTML tag EXACTLY as-is." This is specifically about URLs and image paths. Alt text isn't a URL or image path. I'll translate the alt text.

Let me write the final translation:

13. 二重特異性抗体ブリッジ

A mechanism figure of a bispecific T-cell engager: one antibody arm binding CD3 on
the T cell, the other arm binding a tumor antigen, pulling the two cells into a
synapse where the T cell releases perforin. Label "CD3 ARM", "TUMOR ANTIGEN ARM",
"T CELL", "TUMOR CELL", "PERFORIN". Title: "BITE BRIDGE".

Hmm, but actually, the main content here is just the heading, code block, and image. There's no separate paragraph text to translate. The description is inside the code block as a prompt.

Wait, looking at the structure again - the code block contains what appears to be a prompt for generating an image. This is meta-content (the prompt used to create the image). The actual article content might just be the heading and the image with caption.

I think the translation is:

• Heading: translate
• Code block: keep as-is (it's a prompt/code)
• Image with alt text: translate alt text, keep URL

Let me finalize.</think>

13. 二重特異性抗体ブリッジ

A mechanism figure of a bispecific T-cell engager: one antibody arm binding CD3 on
the T cell, the other arm binding a tumor antigen, pulling the two cells into a
synapse where the T cell releases perforin. Label "CD3 ARM", "TUMOR ANTIGEN ARM",
"T CELL", "TUMOR CELL", "PERFORIN". Title: "BITE BRIDGE".

<think>The user wants me to translate an article fragment about "Antigen escape" into Japanese. Let me analyze what needs translation:

1. The heading "Antigen escape" - this should be translated
2. The image alt text/description in the code block - translate to Japanese
3. The labels in quotes - "TARGET POSITIVE", "TARGET LOST", "CAR-T CELLS", "RELAPSE" - keep these as they're labels
4. The title "ESCAPE ROUTE" - keep as is (it's a label)
5. The image markdown - keep URL and alt text exactly as-is

Wait, let me re-read the rules:

• Rule 1: Keep ALL markdown syntax intact
• Rule 2: Keep every URL, image path, and HTML tag EXACTLY as-is
• Rule 4: Keep the brand word "GLMImage" untranslated

The image alt text: "Antigen escape branching population tree labeled" - this is the alt text inside the markdown, so it should be kept as-is per Rule 2 (URL and image attributes).

Actually, alt text isn't a URL or HTML tag, but the rule says to keep it as-is. Let me keep the image markdown structure exactly.

For the code block content - the description inside the code block. The code block appears to be a description of the image. According to Rule 3: "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)."

Hmm, this is tricky. The content in the code block looks like it's describing the image in plain text, not actual code. It's not really comments either. Let me think about this more carefully.

Looking at it again, this appears to be an image generation prompt (note the URL contains "anatomy-diagram-prompts"). The code block contains a description/prompt for the image.

Given that this is a prompt/specification for image generation and it's inside a code block, I should keep it untranslated per Rule 3. The labels in quotes ("TARGET POSITIVE", etc.) should also remain as they're labels in the actual image.

Let me reconsider the labels. The labels are English words that appear in the image itself. Since they're labels of the diagram, they should remain in English. But the surrounding descriptive text "Label" and "Title" could be translated... but they're inside a code block.

Actually, the code block content should not be translated per Rule 3. Let me keep everything inside the code block exactly as-is.

So my translation would be:

• Translate "14. Antigen escape" to Japanese
• Keep the code block unchanged
• Keep the image markdown unchanged

Translation of "Antigen escape":

• 抗原逃避 (Kōgen tōhi) - this is the standard medical term in Japanese
• or 抗原エスケープ

Let me go with 抗原逃避 as it's the more established Japanese medical term.

So the output:

14. 抗原逃避

A relapse-mechanism figure: after CAR-T cells eliminate target-positive leukemia
cells, a few cells that lost the target antigen survive and expand, shown as a
branching population tree with the escape branch highlighted.
Label "TARGET POSITIVE", "TARGET LOST", "CAR-T CELLS", "RELAPSE".
Title: "ESCAPE ROUTE".

Wait, I need to reconsider the image alt text. The alt text "Antigen escape branching population tree labeled" - should this be translated?

Rule 2 says "Keep every URL, image path, and HTML tag EXACTLY as-is. Do not translate or alter them." This is specifically about URLs, image paths, and HTML tags. Alt text isn't explicitly mentioned, but it's part of the markdown image syntax. I think it's safer to keep it as-is, especially since it serves as descriptive alt text for the image.

Let me finalize my answer.</think>

14. 抗原逃避

A relapse-mechanism figure: after CAR-T cells eliminate target-positive leukemia
cells, a few cells that lost the target antigen survive and expand, shown as a
branching population tree with the escape branch highlighted.
Label "TARGET POSITIVE", "TARGET LOST", "CAR-T CELLS", "RELAPSE".
Title: "ESCAPE ROUTE".

<think>The user wants me to translate a table fragment from an article about GLMImage into natural, fluent Japanese. The table contains anatomical image prompts with labels. I need to:

1. Translate the content naturally into Japanese
2. Keep the table markdown syntax intact
3. Keep the labels (which are anatomical terms) - these are typically kept in English in Japanese medical/scientific contexts, but I should consider whether to translate them or keep them in English. Looking at the context, these are English labels that appear on the image, so they should probably remain in English as they are literal text labels. But the descriptions around them should be in Japanese.

Let me think about this more carefully. The labels in quotes (like 'GLOMERULUS', 'BOWMAN'S CAPSULE', etc.) are literal text strings that would appear on the generated image. These should remain in English (as they're labels for the AI to generate). However, I could provide Japanese translations for anatomical terms in the topic column and descriptions.

Actually, looking again - the labels are in capital letters and appear to be literal strings to be rendered on the image. I should keep these as-is. But for the topic and descriptions, I should translate to natural Japanese.

Wait, but rule 4 says "Keep the brand word 'GLMImage' untranslated." It doesn't say to keep anatomical labels untranslated. However, since these are literal text labels meant to appear on the image, keeping them in English makes sense.

Let me translate the topic names and descriptions into natural Japanese while keeping the label strings in English (since they're literal text to appear on the image).

Topics:

• Nephron = ネフロン
• Lung alveoli = 肺胞
• Digestive system = 消化器系
• Skeletal muscle = 骨格筋
• Kidney position = 腎臓の位置
• Skin layers = 皮膚の層

Let me craft natural Japanese translations:

For row 15 (Nephron):
"A nephron from glomerulus through tubule to collecting duct…"
→ 「糸球体から尿細管、集合管までを示すネフロン…」
Label: 'GLOMERULUS', 'BOWMAN'S CAPSULE', 'LOOP OF HENLE', 'COLLECTING DUCT'
→ ラベル: 'GLOMERULUS', 'BOWMAN'S CAPSULE', 'LOOP OF HENLE', 'COLLECTING DUCT'

Hmm, but should I translate the labels too? The instruction says to keep URLs, image paths, and HTML tags as-is. It doesn't explicitly say to keep these label strings as-is. However, since these are literal text strings meant to be rendered on the image, they probably should remain in English for technical accuracy.

Actually, looking at the structure, the labels are part of the prompt description that includes "Label 'XXX'" - this is a directive to the AI to put these text labels on the image. So they should remain in English as the actual text to be rendered.

But I should translate the surrounding description. Let me draft this:

Row 15:

• Topic: ネフロン
• Change: 「糸球体から尿細管を経て集合管にいたるネフロン…『GLOMERULUS』『BOWMAN'S CAPSULE』『LOOP OF HENLE』『COLLECTING DUCT』のラベルを付与」

Wait, I should consider the headers too:

• "Six quick variants" = 「6つのクイックバリエーション」
• "Topic" = 「トピック」or 「テーマ」
• "One-line change" = 「1行での変更点」or 「変更内容」

Let me refine:

Headers:

• "Six quick variants" → 「6つのクイックバリエーション」
• "Topic" → 「トピック」
• "One-line change" → 「変更内容（一行）」or simpler「変更概要」

For the descriptions, I'll translate them naturally:

15. Nephron - ネフロン
    "A nephron from glomerulus through tubule to collecting duct… Label 'GLOMERULUS', 'BOWMAN'S CAPSULE', 'LOOP OF HENLE', 'COLLECTING DUCT'"
    → 「糸球体から尿細管を経て集合管にいたるネフロン…『GLOMERULUS』『BOWMAN'S CAPSULE』『LOOP OF HENLE』『COLLECTING DUCT』と表示」

16. Lung alveoli - 肺胞
    "A respiratory bronchiole ending in an alveolar sac with capillary net around each alveolus… Label 'BRONCHIOLE', 'ALVEOLUS', 'CAPILLARY', 'SURFACTANT'"
    → 「肺胞嚢に終わる呼吸細気管支と、各肺胞を取り囲む毛細血管網…『BRONCHIOLE』『ALVEOLUS』『CAPILLARY』『SURFACTANT』と表示」

17. Digestive system - 消化器系
    "A full-length digestive tract figure with organ callouts and one villus inset… Label 'STOMACH', 'SMALL INTESTINE', 'VILLUS', 'LARGE INTESTINE'"
    → 「臓器のコールアウトと絨毛の拡大図を伴う、消化管全体を示す図…『STOMACH』『SMALL INTESTINE』『VILLUS』『LARGE INTESTINE』と表示」

18. Skeletal muscle - 骨格筋
    "A muscle cross-section from whole muscle to fascicle to single fiber with myofibril inset… Label 'FASCICLE', 'MUSCLE FIBER', 'MYOFIBRIL', 'SARCOMERE'"
    → 「筋肉全体から筋束、単一線維にいたる断面図と筋原線維の拡大図…『FASCICLE』『MUSCLE FIBER』『MYOFIBRIL』『SARCOMERE』と表示」

19. Kidney position - 腎臓の位置
    "A torso cross-section showing both kidneys with vessels and ureters… Label 'CORTEX', 'MEDULLA', 'URETER', 'RENAL VEIN'"
    → 「両側の腎臓、血管、尿管を示す体幹の断面図…『CORTEX』『MEDULLA』『URETER』『RENAL VEIN』と表示」

20. Skin layers - 皮膚の層
    "A skin cross-section from epidermis through dermis to hypodermis with hair follicle and gland… Label 'EPIDERMIS', 'DERMIS', 'FOLLICLE', 'SEBACEOUS GLAND'"
    → 「表皮から真皮、皮下組織にいたる皮膚の断面図と、毛包および腺…『EPIDERMIS』『DERMIS』『FOLLICLE』『SEBACEOUS GLAND』と表示」

Let me reconsider the use of single quotes vs double quotes for the labels. In the original, the labels are in single quotes like 'GLOMERULUS'. In Japanese, we often use 『 』 for emphasis or quotation. I'll use 『 』 to match Japanese typographic conventions while keeping the labels in English as they appear in the prompt.

Actually, I should be careful here. The original uses single quotes 'GLOMERULUS' which is a programming-style notation. In Japanese translation, I could keep them as single quotes for consistency with the technical prompt format, or use Japanese quotation marks. Since this is a prompt being given to an AI image generator, the labels are literal strings, so I should preserve the structure as much as possible. I'll keep the single quotes.

Let me finalize my translation:

#	トピック	変更内容
15	ネフロン	「糸球体から尿細管を経て集合管にいたるネフロン…'GLOMERULUS'、'BOWMAN'S CAPSULE'、'LOOP OF HENLE'、'COLLECTING DUCT'とラベル付け」
16	肺胞	「肺胞嚢に終わる呼吸細気管支と、各肺胞を取り囲む毛細血管網…'BRONCHIOLE'、'ALVEOLUS'、'CAPILLARY'、'SURFACTANT'とラベル付け」
17	消化器系	「臓器の注釈と絨毛の拡大図を伴う、消化管全体を示す図…'STOMACH'、'SMALL INTESTINE'、'VILLUS'、'LARGE INTESTINE'とラベル付け」
18	骨格筋	「筋肉全体から筋束、単一線維にいたる断面図と筋原線維の拡大図…'FASCICLE'、'MUSCLE FIBER'、'MYOFIBRIL'、'SARCOMERE'とラベル付け」
19	腎臓の位置	「両側の腎臓と血管、尿管を示す体幹の断面図…'CORTEX'、'MEDULLA'、'URETER'、'RENAL VEIN'とラベル付け」
20	皮膚の層	「表皮から真皮、皮下組織にいたる皮膚の断面図と、毛包および腺…'EPIDERMIS'、'DERMIS'、'FOLLICLE'、'SEBACEOUS GLAND'とラベル付け」

Wait, I should double-check my translations:

• "alveolar sac" = 肺胞嚢 ✓
• "respiratory bronchiole" = 呼吸細気管支 ✓
• "capillary net" = 毛細血管網 ✓
• "villus inset" = 絨毛の拡大図 ✓
• "organ callouts" = 臓器の注釈 ✓
• "fascicle" = 筋束 ✓
• "myofibril" = 筋原線維 ✓
• "epidermis" = 表皮 ✓
• "dermis" = 真皮 ✓
• "hypodermis" = 皮下組織 ✓
• "hair follicle" = 毛包 ✓
• "sebaceous gland" = 皮脂腺 ✓
• "Bowman's capsule" = ボーマン嚢 ✓
• "Loop of Henle" = ヘンレのループ ✓
• "collecting duct" = 集合管 ✓

For "one villus inset", I translated as 絨毛の拡大図 (enlarged view of villus). That's good.

For "myofibril inset", I translated as 筋原線維の拡大図. Good.

For the title "Six quick variants" - これは「6つのクイックバリエーション」または「6つのバリエーション案」でしょうか。日本語としてより自然なのは「6つのバリエーション」または「6案のバリエーション」でしょうか。技術文書的なニュアンスを保ちつつ自然にするなら「6つのクイックバリエーション」で良いと思いますが、「6種類のバリエーション案」なども考えられます。

Let me go with "6つのクイックバリエーション" as it preserves the original meaning while being natural.

Actually, I want to reconsider the header "One-line change". This could be:

• 「変更内容（一行）」
• 「変更概要」
• 「一行での変更点」

In context, this appears to be a column showing how the prompt was changed (as a one-line change). I'll go with 「変更内容」with maybe a hint about it being one-line, or just 「変更内容（一行で）」. Let me use 「変更内容」for simplicity and naturalness.

Hmm, looking again at "One-line change" - this means the change is described in one line. So the column header indicates that these are one-line descriptions of the changes. I'll translate as 「変更内容（一行）」or simpler 「変更概要」.

Actually "One-line change" is a bit ambiguous. It could mean:

1. The change (described in one line)
2. A single-line change/diff

Given the context of a table showing variants, it means these are brief one-line descriptions of what was changed in each variant. So 「変更概要」or 「変更点（一行）」would work. Let me use 「変更内容」for simplicity.

Wait, I should be more careful. Let me re-read: "Topic | One-line change". This is showing what the topic is and a one-line summary of the change. I'll translate as 「変更概要」.

Actually, I think 「変更内容（一行）」is clearer. Or just 「一行の変更点」.

Let me finalize: "One-line change" → 「変更内容（一行）」

Hmm, that might be a bit awkward. Let me think again. In Japanese tech documentation, this might just be:

• 「変更点」
• 「変更概要」
• 「変更内容」

I'll go with 「変更内容」and accept that the "one-line" aspect is implicit in the brevity of the content.

Actually, since the original specifies "One-line change", I should preserve that nuance. Let me use 「変更内容（1行）」.

Now let me reconsider whether to use Japanese quotation marks or keep the English single quotes. Looking at the original prompt format:

"Label 'GLOMERULUS', 'BOWMAN'S CAPSULE', ..."

This is a typical AI prompt structure where the labels are quoted strings. In Japanese translation, using 「 」or 『 』would be more natural, but since these are literal strings to be passed to an AI, I should preserve them as code-like strings.

Actually, since this is a fragment of a longer article and we're translating it for a Japanese audience, the Japanese reader needs to understand the prompt. The labels themselves are English terms that the AI will render, so they need to remain in English. The single quotes are part of the prompt syntax.

I'll keep the single quotes around the English labels to preserve the prompt structure.

Final translation:

6つのクイックバリエーション

#	トピック	変更内容（1行）
15	ネフロン	「糸球体から尿細管を経て集合管にいたるネフロン…'GLOMERULUS'、'BOWMAN'S CAPSULE'、'LOOP OF HENLE'、'COLLECTING DUCT'とラベル付け」
16	肺胞	「肺胞嚢に終わる呼吸細気管支と、各肺胞を取り囲む毛細血管網…'BRONCHIOLE'、'ALVEOLUS'、'CAPILLARY'、'SURFACTANT'とラベル付け」
17	消化器系	「臓器の注釈と絨毛の拡大図を伴う、消化管全体を示す図…'STOMACH'、'SMALL INTESTINE'、'VILLUS'、'LARGE INTESTINE'とラベル付け」
18	骨格筋	「筋肉全体から筋束、単一線維にいたる断面図と筋原線維の拡大図…'FASCICLE'、'MUSCLE FIBER'、'MYOFIBRIL'、'SARCOMERE'とラベル付け」
19	腎臓の位置	「両側の腎臓と血管、尿管を示す体幹の断面図…'CORTEX'、'MEDULLA'、'URETER'、'RENAL VEIN'とラベル付け」
20	皮膚の層	「表皮から真皮、皮下組織にいたる皮膚の断面図と、毛包および腺…'EPIDERMIS'、'DERMIS'、'FOLLICLE'、'SEBACEOUS GLAND'とラベル付け」

Let me review once more for naturalness and accuracy:

Row 15:

• "A nephron from glomerulus through tubule to collecting duct" - I translated as 「糸球体から尿細管を経て集合管にいたるネフロン」. This is natural.

Row 16:

• "A respiratory bronchiole ending in an alveolar sac" - 「肺胞嚢に終わる呼吸細気管支」. Natural.
• "with capillary net around each alveolus" - 「各肺胞を取り囲む毛細血管網」. Natural.

Row 17:

• "A full-length digestive tract figure" - 「消化管全体を示す図」. Natural.
• "with organ callouts" - 「臓器の注釈」or 「臓器のコールアウト」. "callout" in technical illustrations is often kept as コールアウト in Japanese. Let me use that.

Actually, "callout" in the context of anatomical illustrations means a label with a line pointing to the structure. In Japanese, this is often translated as 注釈 (annotation) or kept as コールアウト. For medical illustrations, 注釈 or 注記 is common. Let me use 「臓器の注釈」.

Row 18:

• "A muscle cross-section from whole muscle to fascicle to single fiber" - 「筋肉全体から筋束、単一線維にいたる断面図」. Good.
• "with myofibril inset" - 「筋原線維の拡大図」. Good.

Row 19:

• "A torso cross-section showing both kidneys with vessels and ureters" - 「両側の腎臓、血管、尿管を示す体幹の断面図」. Good.

Row 20:

• "A skin cross-section from epidermis through dermis to hypodermis" - 「表皮から真皮、皮下組織にいたる皮膚の断面図」. Good.
• "with hair follicle and gland" - 「毛包および腺」. Maybe should specify "sebaceous gland" since the label says SEBACEOUS GLAND. Let me use 「毛包および皮脂腺」. But then it would be redundant with the label. Actually, the description doesn't say "sebaceous gland" explicitly - just "gland". In context, it's referring to a skin gland, most likely sebaceous. Let me keep it as 「毛包および腺」or specify 「皮脂腺」.

Looking at the original: "with hair follicle and gland" - it's just "gland", not "sebaceous gland". So I should translate it literally as 「腺」or specify based on context. Since the label says SEBACEOUS GLAND, I'll use 「皮脂腺」.

Actually, the description says "gland" generically, and the label specifies SEBACEOUS GLAND. So I should translate "gland" as just 「腺」in the description. But that might be too vague. Let me use 「皮脂腺」for clarity, or 「皮脂腺などの皮膚付属器」.

Let me just use 「毛包と皮脂腺」for clarity.

Wait, but the label 'SEBACEOUS GLAND' is meant to be a literal text rendered on the image. The description mentions "gland" generically, so I should match that. I'll use 「毛包と腺」and let the label specify which gland.

Hmm, actually on reflection, the description "with hair follicle and gland" is a bit vague. Let me just translate it naturally as 「毛包と腺を伴った」.

Let me finalize the table:

#	トピック	変更内容（1行）
15	ネフロン	「糸球体から尿細管を経て集合管にいたるネフロン…'GLOMERULUS'、'BOWMAN'S CAPSULE'、'LOOP OF HENLE'、'COLLECTING DUCT'とラベル付け」
16	肺胞	「肺胞嚢に終わる呼吸細気管支と、各肺胞を取り囲む毛細血管網…'BRONCHIOLE'、'ALVEOLUS'、'CAPILLARY'、'SURFACTANT'とラベル付け」
17	消化器系	「臓器の注釈と絨毛の拡大図を伴う、消化管全体を示す図…'STOMACH'、'SMALL INTESTINE'、'VILLUS'、'LARGE INTESTINE'とラベル付け」
18	骨格筋	「筋肉全体から筋束、単一線維にいたる断面図と筋原線維の拡大図…'FASCICLE'、'MUSCLE FIBER'、'MYOFIBRIL'、'SARCOMERE'とラベル付け」
19	腎臓の位置	「両側の腎臓、血管、尿管を示す体幹の断面図…'CORTEX'、'MEDULLA'、'URETER'、'RENAL VEIN'とラベル付け」
20	皮膚の層	「表皮から真皮、皮下組織にいたる皮膚の断面図と、毛包と腺…'EPIDERMIS'、'DERMIS'、'FOLLICLE'、'SEBACEOUS GLAND'とラベル付け」

I think this is good. Let me output the final translation.</think>

6つのクイックバリエーション

#	トピック	変更内容（1行）
15	ネフロン	「糸球体から尿細管を経て集合管にいたるネフロン…'GLOMERULUS'、'BOWMAN'S CAPSULE'、'LOOP OF HENLE'、'COLLECTING DUCT'とラベル付け」
16	肺胞	「肺胞嚢に終わる呼吸細気管支と、各肺胞を取り囲む毛細血管網…'BRONCHIOLE'、'ALVEOLUS'、'CAPILLARY'、'SURFACTANT'とラベル付け」
17	消化器系	「臓器の注釈と毛の拡大図を伴う、消化管全体を示す図…'STOMACH'、'SMALL INTESTINE'、'VILLUS'、'LARGE INTESTINE'とラベル付け」
18	骨格筋	「筋肉全体から筋束、単一線維にいたる断面図と筋原線維の拡大図…'FASCICLE'、'MUSCLE FIBER'、'MYOFIBRIL'、'SARCOMERE'とラベル付け」
19	腎臓の位置	「両側の腎臓と血管、尿管を示す体幹の断面図…'CORTEX'、'MEDULLA'、'URETER'、'RENAL VEIN'とラベル付け」
20	皮膚の層	「表皮から真皮、皮下組織にいたる皮膚の断面図と、毛包と腺…'EPIDERMIS'、'DERMIS'、'FOLLICLE'、'SEBACEOUS GLAND'とラベル付け」

<think>The user wants me to translate a scientific review checklist into natural, fluent Japanese. This is a fragment about anatomy illustration review. Let me translate it carefully.

The text is about reviewing anatomical illustrations, with specific items to check like labels, structures, orientations, flow arrows, stages, and verification.

Let me translate this into natural Japanese:

• "Scientific review checklist" → "科学的レビューチェックリスト" or "科学的なレビュー時のチェックリスト"
• "Anatomy doubles the stakes on this list" → "解剖学では、このリストの重要性が倍増します"
• "Are all labels spelled correctly?" → "すべてのラベルの綴りは正しいか？"
• "Are all requested structures present — and nothing mirrored?" → "要求されたすべての構造が描かれており、ミラー化されたものはないか？"
• "Are positions, proportions and left/right orientations reasonable against an atlas?" → "位置、比率、左右の向きは解剖図譜と比較して妥当か？"
• "Do flow arrows match physiology (blue right heart, red left heart)?" → "流れの矢印は生理学と一致しているか（右心を青、左心を赤）？"
• "Are stages shown in the correct order?" → "ステージは正しい順序で示されているか？"
• "Has it been checked against a trusted source?" → "信頼できる情報源と照合されているか？"

Let me refine these to sound more natural in Japanese:

• "科学的レビュー時のチェックリスト"
• "解剖図では、このリストの重要性がさらに増します："
• "すべてのラベルの綴りは正確か？"
• "要望されたすべての構造が描画されており、ミラー化された構造はないか？"
• "位置・比率・左右の向きは、解剖図譜と照らし合わせて妥当か？"
• "血流などの矢印は生理学に合っているか（右心を青、左心を赤）？"
• "各段階は正しい順序で示されているか？"
• "信頼できる情報源と照合済みか？"

Let me think more carefully:

"Anatomy doubles the stakes on this list" - This means anatomy makes this checklist more important/critical. "このチェックリストにおいて、解剖学の正確性は特に重要です" or "解剖図の場合、このリストの重要性がさらに増します"

Let me finalize the translation with natural Japanese phrasing:</think>

科学的レビューのチェックリスト

解剖図では、このリストの重要性がさらに増します：

• [ ] すべてのラベルの綴りは正確か？
• [ ] 要請された構造はすべて描かれており、ミラー化された部分はないか？
• [ ] 位置・比率・左右の向きは、解剖図譜と照らし合わせて妥当か？
• [ ] 流れの矢印は生理学と一致しているか（右心を青、左心を赤）？
• [ ] 各ステージは正しい順序で示されているか？
• [ ] 信頼できる情報源と照合済みか？

<think>The user wants me to translate an FAQ section from what appears to be a blog post about AI-generated scientific illustrations (related to GLMImage) into natural, fluent Japanese. Let me translate this carefully while keeping all markdown syntax intact.

Key points:

• Keep markdown syntax (bold, headings, etc.)
• Keep URLs exactly as-is
• Keep "GLMImage" untranslated
• Natural, fluent Japanese
• Complete translation, no summarization

Let me translate each FAQ entry:

1. Why capital letters? - Capital letters are more reliable in AI-generated figures. The convention matches classic atlas plates. Mixed-case is fine for typeset captions.

2. Can I use in nursing/pre-med presentation? - Yes with verification. References the verification guide link.

3. How to fix mirrored heart? - Name the orientation explicitly. References error #1 link.

4. Accurate enough for exams? - As drafts yes, as final figures need checking. The prompts give textbook vocabulary.

Let me write this in natural Japanese:</think>

よくある質問

プロンプトではラベルの綴りを大文字にしているのはなぜですか？

大文字は、生成された図版において大小混在よりも確実にレンダリングされ、プレートサイズでも読みやすくなります。これは道路標識が大文字であるのと同じ理由です。また、この表記法は古典的なアトラスの図版とも一致しています。大小混在は、自分で組版するキャプションでは問題ありませんが、モデルが描画するテキストには大文字が安全なレジスタです。

看護や医学予備校のプレゼンでこれらの図を使用できますか？

はい。ただし、検証ガイドに従って正直に検証プロセスを経すことが前提です。成績評価や臨床に関わる用途では、必ず「Corrected（修正済み）」レベルまで確認してください。上記で紹介した心臓とニューロンのプロンプトは比較的安定しています。一方、冠状断の脳の図は、アトラスの出番となるテーマです。

鏡像になった心臓を修正するにはどうすればよいですか？

向きを明示的に指定してください。たとえば「右心房は観察者の左側、患者が検査者の方を向いている配置で」のように記述します。左右反転はエラー第1位に挙げられる問題であり、制約を指定せずに再生成しても同じサイコロを振り直すだけです。

試験用には十分な精度がありますか？

ドラフトとしては安定して使用できます。ただし最終的な図版としては、各ラベルをコースの参考文献で確認することが必要です。プロンプトは教科書で使用されている語彙を提供してくれますが、実はそこが最も難しい部分です。確認作業自体は、教科書を手元に置いて5分もあれば終わります。

<think>The user wants me to translate a blog fragment into Japanese. Let me analyze the content:

• It's a closing fragment about scientific illustration
• Contains links to other resources
• Mentions GLMImage (brand name to keep untranslated)
• Has markdown links and bold text

Let me translate this naturally into Japanese:

• "Next" → "次のステップ"
• "Start from the anatomy presets" → "解剖学のプリセットから始める"
• "run any prompt above" → "上記のプロンプトを実行する"
• "verify before use" → "使用する前に検証する"
• "Related:" → "関連項目:"
• "how to verify an AI scientific illustration" → "AI科学イラストを検証する方法"
• "12 common errors and fixes" → "よくある12のエラーと修正方法"
• "what is scientific illustration" → "科学イラストとは"

I need to keep all URLs and markdown syntax intact.</think>

次のステップ

解剖学のプリセットから始めて、上記の任意のプロンプトを実行し、使用前に検証してください。関連項目: AI科学イラストの検証方法 · よくある12のエラーと修正方法 · 科学イラストとは。