Triple
T20282513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhihong |
E503184
|
entity |
| Predicate | hasOrthographicForm |
P33995
|
FINISHED |
| Object | Zhihong |
—
|
NE NERFINISHED |
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: Zhihong | Statement: [Zhihong, hasOrthographicForm, Zhihong]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zhihong Context triple: [Zhihong, hasOrthographicForm, Zhihong]
-
A.
Zhihong
chosen
Zhihong is a Chinese given name that represents an alternative romanization of the name Zhizhong.
-
B.
Shuheng
Shuheng is the given name of He Shuheng, an early Chinese Communist revolutionary and political figure.
-
C.
Zhaohui
Zhaohui was a prominent Qing dynasty general best known for leading imperial forces in several of the Ten Great Campaigns under the Qianlong Emperor.
-
D.
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.
-
E.
Zhizhi
Zhizhi was the era name used during the brief reign of Gegeen Khan, a Yuan dynasty emperor of the early 14th century.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4b0e79c8190bd61f22ef1329fa8 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6768f86448190842389a98b93a918 |
completed | April 20, 2026, 6:55 p.m. |
Created at: April 16, 2026, 10:40 a.m.