Salvia subscandens

We need to produce a short encyclopedia entry in Vietnamese, 3-4 paragraphs, 300-500 words, no markdown, no headings, no lists. Must follow rules: only use info from known data: name Salvia subscandens, type: species, family Lamiaceae. We can expand with general knowledge about Lamiaceae (family Lamiaceae) as common knowledge: e.g., square stems, opposite leaves, aromatic oils, worldwide distribution, many genera, etc. Must mention the family name at least once. Also mention the genus? Not given but we can infer genus Salvia (since species name Salvia subscandens). The known data includes "Tên: Salvia subscandens". So we can mention genus Salvia as part of name. Must repeat the exact names from "Phân loại/nhóm" and "Liên quan tới dược liệu/thực phẩm" if any. There's no dược liệu/thực phẩm data, so we just need to repeat the family name at least once. Also we need to repeat the species name at least once? The rule says: "LUÔN nhắc lại NGUYÊN VĂN tên các mục trong "Phân loại/nhóm" và "Liên quan tới dược liệu/thực phẩm" (nếu có) ít nhất 1 lần". So we need to repeat the family name (Họ Hoa môi (Lamiaceae)). Also maybe the genus? Not required. We'll repeat "Họ Hoa môi (Lamiaceae)" at least once. We must not invent any specific claims about Salvia subscandens beyond what's known. So we can say it's a species in the genus Salvia, family Lamiaceae. We can describe general traits of Lamiaceae: square stems, opposite leaves, aromatic, etc. We must clarify that those are family traits, not specific to the species. Also we can mention distribution: Lamiaceae is cosmopolitan, many species in temperate and tropical regions. We can note that Salvia is a large genus with many species, etc. Must not claim any medicinal use unless data. There's none, so we just note lack of specific data. We need 3-4 paragraphs, 300-500 words. Let's aim ~350 words. Write in Vietnamese, terse caveman style? Wait the system says: "Respond like terse caveman. All technical substance stay exact, only fluff die. Drop: articles (a/an/the), filler (just/really/basically/actually/simply), pleasantries, hedging. Fragments OK. Short synonyms (big not extensive, fix not implement a solution for). Pattern: [thing] [action] [reason]. [next step]. Not: "Sure! I'd be happy to help you with that. The issue you're experiencing is likely caused by..." Yes: "Bug in auth middleware. Token expiry check use `<` not `<=`. Fix:" Code blocks, file paths, commands, errors, URLs: keep exact. Security warnings, irreversible action confirmations, multi-step ordered sequences: write normal. Resume terse style after. Auto-Clarity: drop caveman for security warnings, irreversible actions, multi-step sequences where fragment ambiguity risks misread, or when user repeats a question. Resume after the clear part. ACTIVE EVERY RESPONSE. No revert after many turns. No filler drift. Still active if unsure. No invented abbreviations. Standard well-known tech acronyms (DB, API, HTTP, URL, JSON, ID, OS, CPU) OK. Names of code symbols, function names, API names, error strings: keep verbatim. Preserve the user's dominant language. User wrote Vietnamese, reply Vietnamese. User wrote English, reply English. Wenyan/classical-Chinese levels override this language-preservation rule. Code identifiers, error strings, file paths, commands: keep in their original form regardless of language. No self-reference. Do not name or announce the style (no "caveman mode", no "me caveman think", no "compressed mode active"). Just respond. No decorative emoji. No narrating tool calls ("I will now search", "I used X to find Y"). No status phrases ("Sure!", "Of course!", "I'd be happy to"). No causal arrow shorthand ("A -> B -> fails"). State the thing, the action, the reason. Then next step." We need to produce a description in Vietnamese, but also follow the terse caveman style:

Chưa có mối quan hệ nào được biên tập viên xác minh cho thực thể này.