Triple
T13503806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yongli Emperor |
E320958
|
entity |
| Predicate | reignTitle |
P10605
|
FINISHED |
| Object | Yongli |
E320959
|
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: Yongli | Statement: [Yongli Emperor, reignTitle, Yongli]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yongli Context triple: [Yongli Emperor, reignTitle, Yongli]
-
A.
Yongli
chosen
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.
Lüshun
Lüshun is a strategically important port city in northeastern China, historically known as Port Arthur and noted for its role in several major conflicts.
-
C.
Yongxi
Yongxi was an era name used during the reign of Emperor Taizong of the Song dynasty in imperial China.
-
D.
Xingyuan
Xingyuan was the Chinese era name used during part of Emperor Dezong of Tang’s reign in the late eighth century.
-
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_69d807629d6c8190998f1b9bb12d2ed0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaf810e248190a060481004503f96 |
completed | April 12, 2026, 2:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f77f8239c481909faf5a9c403b55f2 |
completed | May 3, 2026, 5:01 p.m. |
Created at: April 9, 2026, 9:43 p.m.