Triple

T13823202
Position Surface form Disambiguated ID Type / Status
Subject 中和殿 E332185 entity
Predicate neighboringBuilding P231 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: [中和殿, neighboringBuilding, 保和殿]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: 保和殿
Context triple: [中和殿, neighboringBuilding, 保和殿]
  • 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_69de0284428081908043c55caeefb833 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.