Triple
T3481173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hongxi Emperor |
E73492
|
entity |
| Predicate | eraName |
P2938
|
FINISHED |
| Object | Hongxi |
E360807
|
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: Hongxi | Statement: [Hongxi Emperor, eraName, Hongxi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hongxi Context triple: [Hongxi Emperor, eraName, Hongxi]
-
A.
Hongxi
chosen
Hongxi was the brief era name of a Ming dynasty emperor whose short reign marked a transitional period in early 15th-century China.
-
B.
Xiluoyuan
Xiluoyuan is a residential neighborhood and subdistrict located in Beijing’s Fengtai District.
-
C.
Yuxiang
Yuxiang is a Chinese given name notably borne by the early 20th-century warlord and military leader Feng Yuxiang.
-
D.
Huaxiang
Huaxiang is a subdistrict-level area within Beijing’s Fengtai District, known primarily as a residential and urban community zone.
-
E.
Zijincheng
Zijincheng is the Chinese name for the Forbidden City, the vast imperial palace complex in central Beijing that served as the home of emperors and the political heart of China for nearly five centuries.
- 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_69ad85b3c9b08190857cae74c7f36da9 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb75850c8190ad02cf2bde8be8a7 |
completed | March 8, 2026, 6:09 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b373b5086081908ee4491860597557 |
completed | March 13, 2026, 2:17 a.m. |
Created at: March 8, 2026, 3:17 p.m.