Likely valid entities or surfaces whose registry alias/canonical/type/subtype guard must be edited or clarified before any row acceptance.

Explanation: 氏-form recurring person surface; all rows carry role/title risk and many are multi-ref or held/debt overlapped.

Sample chapters 5, 7, 8, 10, 11, 16, and 19 before any broad decision.

Confirm 尤氏 always points to one person and not a household/family or another You-surname woman.

Keep the UID person-bound only after confirmation and record 尤氏 as a title/surname-style alias surface.

Prefer a fuller canonical identity if the registry already has one; preserve 尤氏 as alias/display surface.


Explicit, comparatively low-ambiguity surfaces. These are accept candidates only after operator sampling/checks; they are not accepted UID decisions.

Explanation: Explicit proper-name surface with small row count; residual risk is multi-ref context and registry claim/link count mismatch.

Inspect all seven linked rows because every row is multi-ref.

Resolve why registry candidate_ref_count_claim is 8 while linked rows are 7.


High-volume, held/debt-overlapped, or context-sensitive groups that require stratified row review before any acceptance path.

Explanation: 418-row high-frequency 宝玉 group with multi-ref, held/debt overlap, and possible 甄宝玉 confusion; unsafe for broad acceptance.

Stratify by held/debt rows, multi-ref rows, high-frequency-only rows, and chapter bands.

Explicitly inspect rows where 宝玉 and 甄宝玉 are adjacent or share a draft row.

Consider a fuller canonical identity for the main 宝玉 UID while retaining 宝玉 as high-frequency alias.

Add a guard against auto-binding 宝玉 to the object 通灵宝玉 or the distinct person 甄宝玉.


Explanation: 太虚幻境 is likely a valid named non-person entity, but type/subtype must distinguish location, dream realm, or narrative concept.

Inspect all six candidate rows because the set is small.

Confirm each row refers to the same named place/realm, not an inscription, concept, object label, or title.

Set or confirm a non-person location/realm/setting subtype.

Use a more specific dream/metaphysical realm subtype if available.


Explanation: 荣国府 is a clear named surface but can denote estate/location, household, or institutional family seat.

Inspect all seven rows and separately review held/debt rows.

Confirm whether each row needs a location binding, household/org binding, or a split.

Clarify subtype as estate/location when rows refer to the physical place.

Split household/institution references if they are not the same UID.


Explanation: 甄宝玉 is an explicit full-name surface with only three rows; semantic identity is likely distinct but all rows are held/debt multi-ref.

Inspect all three rows before any operator decision.

Confirm 甄宝玉 is explicitly named and not confused with 宝玉 or counterpart narration.

Keep 甄宝玉 distinct from 宝玉 in any future high-frequency alias guard.


Explanation: 秦氏 likely points to a recurring person, but all rows are 氏-form role/title-like surface and many are multi-ref.

Inspect rows from chapters 5, 7, 10, 11, 13, and 14 before any broad decision.

Confirm 秦氏 always refers to one person and not another Qin-surname entity or household reference.

Use a fuller canonical identity if available and retain 秦氏 as title/surname-style alias.

Split or reject rows where 秦氏 refers to a different Qin-related entity.


Explanation: 薛姨妈 is probably a fixed person title/name, but every row is role/title surface and many rows are multi-ref.

Sample chapters 4 and 8 multi-ref rows to confirm the surface points to the same person.

Confirm bare 姨妈 or other relation terms are not merged into this UID.

Mark 薛姨妈 as a fixed kinship/honorific person surface, not a generic role/title.


Explanation: 120-row high-frequency 黛玉 group with many multi-ref and held/debt overlaps; not safe for bulk accept from metadata-only review.

Sample dense chapter bands including chapters 3, 8, 19, and 20.

Split review into held/debt, multi-ref, and ordinary high-frequency subqueues before acceptance.


Explanation: 贾雨村 is an exact name, but all linked rows are held/debt multi-ref and registry claim count differs from linked rows.

Clarify whether the 30 claimed refs include rows outside this deferred linked set.

Split exact-name alias confirmation from held/debt row-level binding confirmation.


Explanation: 贾琏 is an exact person-name surface; accept-candidate path is reasonable after held/debt and chapter sampling.

Prioritize held/debt overlap rows DEFERREDUIDCAND000038, DEFERREDUIDCAND000239, and DEFERREDUIDCAND000244.

Sample dense chapter 16 rows to exclude adjacent-person overbinding.


Explanation: 贾母 is a fixed person appellation in this work but still kinship-style; sample before accepting.

Prioritize chapter 3 held/debt samples, then sample chapters 5, 8, 11, and 16.

Confirm generic 母 or 老太太 aliases are not silently added.

Mark 贾母 as a fixed person appellation if alias typing is supported.


Explanation: 莺儿 is a small exact-name/nickname group with no held/debt overlap; source evidence is low and rows are multi-ref.

Check chapter 8 continuous rows and chapter 20 samples.

Confirm all rows point to the same person rather than a non-person nickname use.


Explanation: 李纨 is an exact person-name surface with only three linked rows; confirm claim/link scope before acceptance.

Confirm the remaining claimed refs are outside this decision or separately reviewed.


Explanation: 贾政 is an exact person-name surface; high-frequency and multi-ref rows require sampling before any operator acceptance.

Check held/debt overlap rows and chapter 9 continuous multi-ref rows.

Confirm shared-context rows with 李贵 bind both UIDs correctly.


Explanation: 平儿 is an exact/common person name; claim/link gap and held/debt chapter 6 rows need review.

Check chapters 7, 11, and 16 for cross-chapter stability.

Resolve the 35 claimed vs 28 linked difference.


Explanation: 宝钗 is a clear person surface with reasonable evidence, but high-frequency and multi-ref rows still require sampling.

Also sample chapters 16, 19, and 20 because candidate chapter counts show wider coverage.


Explanation: 李嬷嬷 likely names one person, but 嬷嬷 is a role/title component and registry typing needs an alias guard.

Check chapter 8 and chapter 20 samples for same-person continuity.

Confirm the full surface is 李嬷嬷 and not a stitched role description.

Mark 李嬷嬷 as a concrete person surface/honorific-role name.

Do not add bare 嬷嬷 as alias without row-level evidence.


Explanation: 李贵 is an exact person-name surface with six linked rows; check all rows and claim/link scope.

Confirm chapter 9 shared-context rows distinguish 李贵 from 贾政.


Explanation: 胡氏 is a surname-style 氏 surface; all rows are held/debt overlapped and cannot be safely decided without text.

Read all seven rows and decide whether 胡氏 is one person, family/surname reference, spouse appellation, or generic mention.

Confirm the UID has enough identity description to distinguish it from other surname-style women.

If confirmed as a person, add disambiguation notes for surname-style person surface.

Reject row-level refs rather than writing 胡氏 to person UID if context is family/surname/generic.


Explanation: 凤姐 is likely a stable nickname for one person, but 267 high-frequency rows and canonical-name alias risk require registry clarification.

First confirm whether this UID is the one that should carry 凤姐/王熙凤 aliases.

Sample held/debt and multi-ref rows, especially chapters 3 and 6, plus dense chapters 11, 14, and 16.

If a full canonical exists, bind 凤姐 as nickname/alias to that UID rather than keeping duplicate person identity.

Do not auto-include nearby surfaces such as 凤姐儿 without separate review.


Explanation: 通灵宝玉 is likely one object/artifact, but all rows carry object/location, held/debt, and multi-ref risks.

Inspect all three rows and confirm the surface points to the jade itself, not a person, holder, action, or setting.

Confirm the entity type/subtype is object/artifact/token/jade, not person or location.

Keep 通灵宝玉 as exact object surface and explicitly guard against short 宝玉 binding to the object.

Add a person/object disambiguation note against 贾宝玉.


Explanation: 封肃 is an exact proper name; small linked set makes manual confirmation practical.

Inspect both linked rows and confirm 封肃 points to the person, not family/location/relationship label.

Sample unlisted affected rows to exclude broad 封-character matching.


Explanation: 甄士隐 is an exact person-name surface; multi-ref/held-debt context and chapter-stat mismatch keep confidence medium.

Check affected rows for non-exact 士隐 or 甄家 matching before accepting the group.


Explanation: 刘姥姥 likely names one person, but the surface is high-frequency, title-like, and entirely held/debt overlapped.

Prioritize multi-entity rows and then sample later chapter 6 rows.

Confirm the full surface 刘姥姥 is fixed-person naming and not a generic 姥姥 relation term.

Mark 刘姥姥 as fixed honorific person name.

Do not accept bare 姥姥 or 刘氏 as aliases without separate evidence.


Explanation: 戴权 is an exact proper-name surface with only two linked rows and no high-frequency, role/title, object/location, or held/debt risk.

Inspect both linked rows and confirm they point to the same person.

Confirm no office/title or palace institution surface is merged into this UID.


Explanation: 秦钟 is an exact name, but 73 high-frequency rows span many chapters with multi-ref and aggregation-scope risks.

Sample chapter 7 start, chapter 8 continuation, chapters 15/16 dense rows, and chapter 17 tail rows.

Confirm 秦氏, 秦可卿, 秦业, and 秦家 surfaces are not folded into 秦钟.

Do not write registry changes until stratified sampling confirms exact-surface stability.

Add Qin-family disambiguation guard if later edited.


Explanation: 贾珍 is an exact name, but high-frequency, multi-ref, held/debt, broad chapter spread, and Jia-family confusion make bulk accept unsafe.

Prioritize chapter 10 held/debt rows and chapter 11 multi-entity rows.

Supplement with chapters 13, 14, 16, and 17 samples.

Do not write registry changes until cross-chapter sampling confirms exact-surface stability.

Add Jia-family disambiguation guard if later edited.