Triple
T17071751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qianlong Emperor |
E414237
|
entity |
| Predicate | child |
P120
|
FINISHED |
| Object | Yongcheng |
E414237
|
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: Yongcheng | Statement: [Qianlong Emperor, child, Yongcheng]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yongcheng Context triple: [Qianlong Emperor, child, Yongcheng]
-
A.
Yongcheng
chosen
Yongcheng was a Qing dynasty imperial prince, known as one of the sons of the Qianlong Emperor of China.
-
B.
Yuncheng
Yuncheng is a major city in southern Shanxi Province, China, known for its historical sites and role as a regional transportation and economic hub.
-
C.
Licheng
Licheng is the courtesy name of the Daoguang Emperor, a Qing dynasty ruler of China in the early 19th century.
-
D.
Zicheng
Zicheng is the courtesy name of Zeng Guofan, a prominent Qing dynasty statesman, military leader, and Confucian scholar who played a key role in suppressing the Taiping Rebellion.
-
E.
Houyuan
Houyuan was a historical Chinese era name used during the reign of Emperor Jing of the Western Han dynasty.
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbc1b7d48190979a848b4188cb22 |
completed | April 18, 2026, 7:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a012edbce988190a784448ba8a258a5 |
completed | May 11, 2026, 1:20 a.m. |
Created at: April 10, 2026, 5:34 a.m.