Triple
T4060275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hall of Benevolence and Longevity |
E86193
|
entity |
| Predicate | hasChineseName |
P4878
|
FINISHED |
| Object |
仁寿殿
仁寿殿 is a historic palace hall in Beijing’s Forbidden City, notable as one of the imperial residential and ceremonial buildings of the Ming and Qing dynasties.
|
E410392
|
NE FINISHED |
How this triple was built (4 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: 仁寿殿 | Statement: [Hall of Benevolence and Longevity, hasChineseName, 仁寿殿]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 仁寿殿 Context triple: [Hall of Benevolence and Longevity, hasChineseName, 仁寿殿]
-
A.
保和殿
保和殿 is one of the principal ceremonial halls within Beijing’s Forbidden City, historically used for imperial banquets and important state rituals.
-
B.
交泰殿
交泰殿 is a historic hall within Beijing’s Forbidden City, traditionally used for important imperial ceremonies and symbolizing the harmony of heaven and earth in Chinese imperial architecture.
-
C.
中和殿
中和殿 is a ceremonial hall within Beijing’s Forbidden City, historically used by Chinese emperors to rest and prepare before major state rituals.
-
D.
太庙
太庙是北京故宫东侧一座明清皇家宗庙建筑群,现为对公众开放的历史文化景区。
-
E.
午门
午门 is the grand southern entrance and main gate of Beijing’s Forbidden City, historically used for important imperial ceremonies and proclamations.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: 仁寿殿 Triple: [Hall of Benevolence and Longevity, hasChineseName, 仁寿殿]
Generated description
仁寿殿 is a historic palace hall in Beijing’s Forbidden City, notable as one of the imperial residential and ceremonial buildings of the Ming and Qing dynasties.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: 仁寿殿 Target entity description: 仁寿殿 is a historic palace hall in Beijing’s Forbidden City, notable as one of the imperial residential and ceremonial buildings of the Ming and Qing dynasties.
-
A.
保和殿
保和殿 is one of the principal ceremonial halls within Beijing’s Forbidden City, historically used for imperial banquets and important state rituals.
-
B.
交泰殿
交泰殿 is a historic hall within Beijing’s Forbidden City, traditionally used for important imperial ceremonies and symbolizing the harmony of heaven and earth in Chinese imperial architecture.
-
C.
中和殿
中和殿 is a ceremonial hall within Beijing’s Forbidden City, historically used by Chinese emperors to rest and prepare before major state rituals.
-
D.
太庙
太庙是北京故宫东侧一座明清皇家宗庙建筑群,现为对公众开放的历史文化景区。
-
E.
午门
午门 is the grand southern entrance and main gate of Beijing’s Forbidden City, historically used for important imperial ceremonies and proclamations.
- F. None of above. chosen
Provenance (5 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_69aed93c69208190a4efac0efe3cd69b |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefbd32c0c8190bc575974ccf831b3 |
completed | March 9, 2026, 4:56 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b562a98c488190a7e77cd46ff998bc |
completed | March 14, 2026, 1:29 p.m. |
| NEDg | Description generation | batch_69b5637e72948190989169b0a46916a8 |
completed | March 14, 2026, 1:32 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69b563fc4cb081908ba0f1a799338a8c |
completed | March 14, 2026, 1:34 p.m. |
Created at: March 9, 2026, 3:38 p.m.