Triple
T3176192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palace of Heavenly Purity |
E66470
|
entity |
| Predicate | ChineseName |
P744
|
FINISHED |
| Object | 乾清宫 |
E332186
|
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: [Palace of Heavenly Purity, ChineseName, 乾清宫]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 乾清宫 Context triple: [Palace of Heavenly Purity, ChineseName, 乾清宫]
-
A.
中和殿
中和殿 is a ceremonial hall within Beijing’s Forbidden City, historically used by Chinese emperors to rest and prepare before major state rituals.
-
B.
保和殿
保和殿 is one of the principal ceremonial halls within Beijing’s Forbidden City, historically used for imperial banquets and important state rituals.
-
C.
颐和园
颐和园是位于北京市西北部、以宏伟的皇家园林建筑和昆明湖、万寿山自然景观著称的世界文化遗产。
-
D.
Outer Court of the Forbidden City
chosen
The Outer Court of the Forbidden City is the grand southern ceremonial precinct of Beijing’s imperial palace complex, where Ming and Qing emperors conducted major state rituals and governance.
-
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_69ad8586a34c8190944c63ec11a8de1a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada69b0bec8190957913b44d876079 |
completed | March 8, 2026, 4:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b235f16e60819091cbdb76130ecc40 |
completed | March 12, 2026, 3:41 a.m. |
Created at: March 8, 2026, 3:06 p.m.