Triple
T9640671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor Yizong of Tang |
E233055
|
entity |
| Predicate | eraName |
P2938
|
FINISHED |
| Object | Xian Tong |
E812636
|
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: Xian Tong | Statement: [Emperor Yizong of Tang, eraName, Xian Tong]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Xian Tong Context triple: [Emperor Yizong of Tang, eraName, Xian Tong]
-
A.
Xian Tong
chosen
Xian Tong was the era name used during the reign of Emperor Yizong of the Tang dynasty in China.
-
B.
Xuan
Xuan is the posthumous honorific title given to the influential Cao Wei general and statesman Sima Yi, who played a key role in the Three Kingdoms period of Chinese history.
-
C.
Xuan
Xuan is a Vietnamese surname commonly used as a family name in Vietnam.
-
D.
Xiaolingdi
Xiaolingdi is the posthumous temple name of Emperor Ling of Han, a late Eastern Han dynasty ruler whose ineffective reign contributed to the dynasty’s decline and the rise of warlordism in China.
-
E.
Zhenyuan
Zhenyuan was a late 19th-century Chinese ironclad battleship of the Beiyang Fleet that played a prominent role in the First Sino-Japanese War.
- 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_69ca848a5a908190aad251f4137b0c3a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9b552a1c81909a1fab347110eeb1 |
completed | April 1, 2026, 10:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d189fd53fc8190bc36f2b8e0e21036 |
completed | April 4, 2026, 10 p.m. |
Created at: March 30, 2026, 8:12 p.m.