Triple
T15398024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | He Shuheng |
E368231
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Shuheng |
E368231
|
NE FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Shuheng | Statement: [He Shuheng, givenName, Shuheng]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shuheng Context triple: [He Shuheng, givenName, Shuheng]
-
A.
Shuheng
chosen
Shuheng is the given name of He Shuheng, an early Chinese Communist revolutionary and political figure.
-
B.
Zhihong
Zhihong is a Chinese given name that represents an alternative romanization of the name Zhizhong.
-
C.
Jianwei
Jianwei is a given name most notably borne by Pan Jianwei, a prominent Chinese quantum physicist recognized for his pioneering work in quantum communication and quantum computing.
-
D.
Shengzhi
Shengzhi is the given name of Tang Shengzhi, a prominent Chinese Nationalist general active during the early 20th century.
-
E.
Zhengping
Zhengping is a Chinese given name commonly used for males and composed of characters that often convey meanings related to righteousness and peace.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d85a16c68c819099c1b547fbc87b32 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e8c5d40819086622b70edcb6294 |
completed | April 16, 2026, 1:42 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff13542c908190abf765b0530c76ce |
completed | May 9, 2026, 10:58 a.m. |
Created at: April 10, 2026, 3:19 a.m.