Triple

T22440166
Position Surface form Disambiguated ID Type / Status
Subject 上皇 E554732 entity
Predicate relatedTo P37 FINISHED
Object 上皇后 NE NERFINISHED

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: [上皇, relatedTo, 上皇后]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: 上皇后
Context triple: [上皇, relatedTo, 上皇后]
  • A. 萬貴妃
    萬貴妃 was a powerful and long-favored imperial consort of the Ming dynasty Chenghua Emperor, known for her significant influence at court and her controversial relationship with the much younger emperor.
  • B. 香淳皇后
    香淳皇后 was the Empress of Japan as the wife of Emperor Shōwa (Hirohito) and the mother of Emperor Akihito.
  • C. Xiaozhuangwen Empress Dowager
    Xiaozhuangwen Empress Dowager was a highly influential Qing dynasty matriarch and political figure, grandmother of the Kangxi Emperor, known for her key role in consolidating early Qing rule in China.
  • D. Empress Wang (Longwu Emperor’s consort)
    Empress Wang (Longwu Emperor’s consort) was the primary wife and empress of the Southern Ming Longwu Emperor, remembered for her role in the short-lived resistance court against the Qing conquest.
  • E. 上皇后美智子 chosen
    上皇后美智子は、日本の上皇・明仁の皇后として平成時代の象徴的存在となり、民間出身の皇后として国民に広く親しまれた人物である。
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e11e5010e48190ae1e9c9db9697637 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15ae0edcc8190919b198035de0df2 completed April 29, 2026, 1:12 a.m.
Created at: April 16, 2026, 8:47 p.m.