Triple
T13823327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baohe Dian |
E332188
|
entity |
| Predicate | chineseName |
P4878
|
FINISHED |
| Object | 保和殿 |
E332187
|
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: 保和殿 | Statement: [Baohe Dian, chineseName, 保和殿]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 保和殿 Context triple: [Baohe Dian, chineseName, 保和殿]
-
A.
保和殿
chosen
保和殿 is one of the principal ceremonial halls within Beijing’s Forbidden City, historically used for imperial banquets and important state rituals.
-
B.
中和殿
中和殿 is a ceremonial hall within Beijing’s Forbidden City, historically used by Chinese emperors to rest and prepare before major state rituals.
-
C.
仁寿殿
仁寿殿 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.
-
D.
交泰殿
交泰殿 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.
-
E.
太和殿
太和殿是位于北京故宫中轴线上的最高等级宫殿建筑，也是明清两代皇帝举行重大典礼和朝会的主要场所。
- 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_69d81c5ae7c88190b0dd41bdafeb5999 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0285fb7c8190be4b90bdc0d6fa53 |
completed | April 14, 2026, 9:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7c70454a8819097b5e5091f84be33 |
completed | May 3, 2026, 10:07 p.m. |
Created at: April 9, 2026, 10:13 p.m.