Triple
T13823322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 保和殿 |
E332187
|
entity |
| Predicate | UNESCOWorldHeritageSite |
P923
|
FINISHED |
| Object | 明清皇家宫殿：北京故宫 |
E68470
|
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: [保和殿, UNESCOWorldHeritageSite, 明清皇家宫殿：北京故宫]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 明清皇家宫殿：北京故宫 Context triple: [保和殿, UNESCOWorldHeritageSite, 明清皇家宫殿：北京故宫]
-
A.
北京皇城
北京皇城是明清两代北京城中围绕皇宫设置的内城区域，汇集重要宫殿、坛庙和皇家建筑群的核心防御与礼制空间。
-
B.
皇居
皇居は、日本の天皇と皇室の公的な居所および宮中行事の中心となる東京都千代田区に位置する宮殿・庭園の総称である。
-
C.
Summer Palace, an Imperial Garden in Beijing
The Summer Palace is a vast, historic imperial garden and palace complex in Beijing renowned for its classical Chinese landscape design, lakes, and pavilions.
-
D.
颐和园
颐和园是位于北京市西北部、以宏伟的皇家园林建筑和昆明湖、万寿山自然景观著称的世界文化遗产。
-
E.
Imperial Palaces of the Ming and Qing Dynasties in Beijing and Shenyang
chosen
The Imperial Palaces of the Ming and Qing Dynasties in Beijing and Shenyang comprise the former imperial residences and political centers of China’s last two dynasties, including the Forbidden City, renowned for their grand architecture, historical significance, and exceptional preservation.
- 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_69f7b8e60e1c81908d51d723e85e0541 |
completed | May 3, 2026, 9:06 p.m. |
Created at: April 9, 2026, 10:13 p.m.