Triple
T9780072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Wen of Zhou |
E237344
|
entity |
| Predicate | templeName |
P44027
|
FINISHED |
| Object | Taizu |
E723918
|
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: Taizu | Statement: [King Wen of Zhou, templeName, Taizu]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Taizu Context triple: [King Wen of Zhou, templeName, Taizu]
-
A.
Taizu
Taizu is the temple name of the Hongwu Emperor, the founding ruler of China’s Ming dynasty.
-
B.
Taizu
chosen
Taizu is the temple name given to Tang of Shang, the founding king of China’s Shang dynasty.
-
C.
Gaozu
Gaozu is the posthumous temple name honoring the influential Cao Wei statesman and strategist Sima Yi, later revered as a dynastic founder figure.
-
D.
Thái Tổ
Thái Tổ is the posthumous temple name traditionally given to founding emperors of Vietnamese dynasties, notably used for Lý Thái Tổ, the founder of the Lý dynasty.
-
E.
Jingdi
Jingdi is the posthumous temple name of Emperor Jing of Han, a Western Han dynasty ruler known for consolidating imperial power and promoting economic stability 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_69ca84d975a08190aab25b02a89bdab3 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda1b0b15881909ef52d0156148c59 |
completed | April 1, 2026, 10:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1bd28b0e48190984cf44d88f324d7 |
completed | April 5, 2026, 1:38 a.m. |
Created at: March 30, 2026, 8:27 p.m.