Triple
T4008147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qianlong Emperor |
E89576
|
entity |
| Predicate | child |
P120
|
FINISHED |
| Object |
Yongcheng
Yongcheng was a Qing dynasty imperial prince, known as one of the sons of the Qianlong Emperor of China.
|
E414237
|
NE FINISHED |
How this triple was built (4 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.
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.
-
B.
Jianye
Jianye is an ancient name for the city now known as Nanjing, a historically significant capital in several Chinese dynasties.
-
C.
Ruchang
Ruchang is a Chinese given name most notably borne by Ding Ruchang, a late Qing dynasty naval commander.
-
D.
Hucheng
Hucheng is the given name of Yang Hucheng, a prominent Chinese general and political figure best known for his role in the Xi'an Incident of 1936.
-
E.
Jianyang
Jianyang is a county-level city in northern Fujian Province, China, known for its historical role in tea production and its location along the Min River.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Yongcheng Triple: [Qianlong Emperor, child, Yongcheng]
Generated description
Yongcheng was a Qing dynasty imperial prince, known as one of the sons of the Qianlong Emperor of China.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Yongcheng Target entity description: Yongcheng was a Qing dynasty imperial prince, known as one of the sons of the Qianlong Emperor of China.
-
A.
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.
-
B.
Jianye
Jianye is an ancient name for the city now known as Nanjing, a historically significant capital in several Chinese dynasties.
-
C.
Ruchang
Ruchang is a Chinese given name most notably borne by Ding Ruchang, a late Qing dynasty naval commander.
-
D.
Hucheng
Hucheng is the given name of Yang Hucheng, a prominent Chinese general and political figure best known for his role in the Xi'an Incident of 1936.
-
E.
Jianyang
Jianyang is a county-level city in northern Fujian Province, China, known for its historical role in tea production and its location along the Min River.
- F. None of above. chosen
Provenance (5 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_69aed9585e788190bec2d39deba3750f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefa647f80819081180eb267f1cfcc |
completed | March 9, 2026, 4:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b56b47294c8190871f4a6a57b3470f |
completed | March 14, 2026, 2:05 p.m. |
| NEDg | Description generation | batch_69b56f0f94c08190b92deb5373c525e5 |
completed | March 14, 2026, 2:22 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69b56fee67088190ab9a42ccac03d10f |
completed | March 14, 2026, 2:25 p.m. |
Created at: March 9, 2026, 3:34 p.m.