Triple
T16983226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhu Houcong |
E411996
|
entity |
| Predicate | templeName |
P44027
|
FINISHED |
| Object | Shizong |
E371787
|
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: Shizong | Statement: [Zhu Houcong, templeName, Shizong]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shizong Context triple: [Zhu Houcong, templeName, Shizong]
-
A.
Shizong
chosen
Shizong is the temple name of the Jiajing Emperor, a Ming dynasty ruler known for his long reign and efforts to strengthen imperial authority and Confucian orthodoxy in China.
-
B.
Shizong
Shizong is the posthumous temple name given to Emperor Wu of Han, one of China’s most powerful and expansionist Han dynasty rulers.
-
C.
Shizong
Shizong was the temple name of a prominent emperor of the Jurchen-led Jin dynasty in China, noted for consolidating imperial power and promoting cultural and administrative reforms.
-
D.
Yizong
Yizong was the temple name of an emperor of the Tang dynasty who ruled China during the mid-9th century.
-
E.
Huaiji
Huaiji is a county in Guangdong Province, China, known historically as the ancestral home of the Yang clan.
- 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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d188ede48190baead48aac84c78d |
completed | April 18, 2026, 6:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00dc0d437c81908f003a10b798998a |
completed | May 10, 2026, 7:27 p.m. |
Created at: April 10, 2026, 5:32 a.m.