Triple
T15654221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taichang Emperor |
E376388
|
entity |
| Predicate | templeName |
P44027
|
FINISHED |
| Object | Taichang |
E376388
|
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: Taichang | Statement: [Taichang Emperor, templeName, Taichang]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Taichang Context triple: [Taichang Emperor, templeName, Taichang]
-
A.
Taichang
chosen
Taichang was the posthumous temple name of a short-reigning Ming dynasty emperor who ruled China briefly in 1620.
-
B.
Zhuzihu
Zhuzihu is a scenic valley area in Taipei’s Yangmingshan National Park, best known for its cool-climate agriculture and seasonal calla lily fields.
-
C.
Daizong
Daizong is the posthumous temple name of the Ming dynasty's Jingtai Emperor, used in ancestral rites and historical records.
-
D.
Tudigong
Tudigong is a widely venerated Chinese earth god and local tutelary deity associated with protecting land, villages, and community welfare.
-
E.
Zixu
Zixu is the courtesy name of Wu Zixu, a prominent statesman and military strategist of the late Spring and Autumn period in ancient China.
- 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_69d85cd1564c8190991adda63bfab4b0 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04ef089948190902ec22f4d7bc932 |
completed | April 16, 2026, 2:52 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff6797954c8190ac05ee3db634efa7 |
completed | May 9, 2026, 4:57 p.m. |
Created at: April 10, 2026, 4:15 a.m.