Triple
T4008149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qianlong Emperor |
E89576
|
entity |
| Predicate | child |
P120
|
FINISHED |
| Object | Yongyan |
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: Yongyan | Statement: [Qianlong Emperor, child, Yongyan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yongyan Context triple: [Qianlong Emperor, child, Yongyan]
-
A.
Yongli
Yongli was the era name of the last emperor of the Southern Ming dynasty, whose reign marked the final resistance of Ming loyalists against the Qing conquest in 17th-century China.
-
B.
Guangyi
Guangyi was a warship that served in China's late 19th-century Beiyang Fleet, one of the Qing dynasty's principal modern naval forces.
-
C.
Yongcheng
chosen
Yongcheng was a Qing dynasty imperial prince, known as one of the sons of the Qianlong Emperor of China.
-
D.
Yuanhong
Yuanhong is a Chinese given name that appears in the full name of the historical figure Li Yuanhong.
-
E.
Zhizhong
Zhizhong is a Chinese given name shared by various individuals, including historical and contemporary figures.
- 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_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_69b5768fae4881908c9dea4e39e3788c |
completed | March 14, 2026, 2:54 p.m. |
Created at: March 9, 2026, 3:34 p.m.