Triple
T8186181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor Ling of Han |
E191188
|
entity |
| Predicate | eraNameIntroduced |
P2938
|
FINISHED |
| Object | Zhongping |
E746417
|
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: Zhongping | Statement: [Emperor Ling of Han, eraNameIntroduced, Zhongping]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zhongping Context triple: [Emperor Ling of Han, eraNameIntroduced, Zhongping]
-
A.
Zhongping
chosen
Zhongping was an era name used during the later years of Emperor Ling’s rule in the Eastern Han dynasty of China.
-
B.
Zhizhong
Zhizhong is a Chinese given name shared by various individuals, including historical and contemporary figures.
-
C.
Yuncheng
Yuncheng is a major city in southern Shanxi Province, China, known for its historical sites and role as a regional transportation and economic hub.
-
D.
Yongcheng
Yongcheng was a Qing dynasty imperial prince, known as one of the sons of the Qianlong Emperor of China.
-
E.
Jianye
Jianye is an ancient name for the city now known as Nanjing, a historically significant capital in several Chinese dynasties.
- 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_69ca82c5b6948190a583c096fb0a6c71 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb7266bc148190984060b7b95effb5 |
completed | March 31, 2026, 7:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cf27abf324819098bd6ecfd5a4d8cc |
completed | April 3, 2026, 2:36 a.m. |
Created at: March 30, 2026, 5:41 p.m.