Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Two people who share a name end as one entity through the bare-name entity

Open
  • Is something wrong?
#1,136 9 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@virtue039 is already working on this.

Since Oct 10, 2026.

  • #1377 by @virtue039 — open

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
15/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
data

Research direction

Start with the two dumps named in the issue (ib_dev-16bases and ib_fix-16bases) and the identity bench, to see where the bare 张伟 entities are created and merged. Trace how an exact-name mention is resolved when two entities share that name, and how the adjudication step decided to merge the two bare entities. Done means the two people stay separate across the 16 bases, shown by a before-and-after run of the identity bench.

Written by the indexing model from the issue text.

Description

bug
What happens

The identity bench has two people named 张伟, a finance director and an engineer. They should end as two entities. In the 16 bases run for #1134 (8 on dev, 8 on the branch; deepseek-v4-flash with thinking off, bge-m3) one entity ended up holding facts of both in 10: 3 of 8 on dev, 7 of 8 on the branch. #1134 does not touch this path (no name involved has digits, and both sides made 12 merges between 张伟 entities), so the gap between the sides reads as variance, and the variance is large.

Where the two people meet

In all three dev bases the meeting point is the entity named plainly 张伟. The titled entities (财务部总监张伟, 工程部工程师张伟) stay correct.

Base Bare 张伟 entity holds How it got there
…05d2 年度技术奖, 年度管理奖, 预算管理, 数据回传 one adjudicated merge of 张伟 with 张伟 at 0.85: "the facts describe different achievements, which is not a contradiction"
…3773 年度预算, 年度管理奖, 预算管理, and 年度技术奖 no merge between the two; a second bare 张伟 exists with 数据回传 only
…edea 年度技术奖 and 年度管理奖 no merge between the two; a second bare 张伟 exists with no facts

So there are two ways in:

  1. At resolution. A mention written as just 张伟 goes to an existing entity of that exact name with no review, and when two such entities exist the mention can land on the wrong one. Two of the three bases.
  2. At adjudication. Two entities of the same bare name are merged because nothing contradicts, though nothing connects them either. One of the three.

Merges of a bare 张伟 into a titled one were each backed by a matching passage and look right.

What to find out
  1. How an exact-name mention chooses between two entities of the same name, and whether its passage is consulted.
  2. Whether "same bare name, nothing in common" should be kept for a person instead of merged.
  3. The noise floor: one base adjudicated twice, so a change can be told from variance.

Dumps of both sides are kept (ib_dev-16bases, ib_fix-16bases). Any change here gets the identity bench before and after.

Dominant language
Rust
Stars
8.1k
Forks
1.1k
Avg merge
21h 2m
Merged PRs (30d)
263

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from deeplethe/utopia

All issues in deeplethe/utopia

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.