Triple

T22533200
Position Surface form Disambiguated ID Type / Status
Subject 中山慶子 E557095 entity
Predicate 別名 P39 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: [中山慶子, 別名, 中山慶子（なかやま よしこ）]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: 中山慶子（なかやま よしこ）
Context triple: [中山慶子, 別名, 中山慶子（なかやま よしこ）]
  • A. 中山慶子 chosen
    中山慶子 was a Japanese noblewoman and lady-in-waiting of the late Edo period, best known as the birth mother of Emperor Meiji.
  • B. Konoe Sakiko
    Konoe Sakiko was a Japanese noblewoman of the powerful Konoe family who became an imperial consort to Emperor Go-Yōzei during the late Azuchi–Momoyama and early Edo periods.
  • C. Konoe Chiyoko
    Konoe Chiyoko was a Japanese noblewoman best known as the wife of pre-World War II and wartime Prime Minister Fumimaro Konoe.
  • D. Higashikuni Nobuko
    Higashikuni Nobuko was a Japanese princess of the Imperial Family who became a member of the Higashikuni-no-miya house through marriage.
  • E. Nagako Kuni
    Nagako Kuni, later known as Empress Kōjun, was the wife of Emperor Shōwa (Hirohito) and the longest-serving empress consort in Japanese history.
  • 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_69e11e57483c8190b0887c4f8ff26446 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15ed88cf08190ae7e5b6bf9a80372 completed April 29, 2026, 1:28 a.m.
Created at: April 16, 2026, 8:51 p.m.