Triple

T22440126
Position Surface form Disambiguated ID Type / Status
Subject 香淳皇后 E554731 entity
Predicate 子女 P980 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
    常陸宮正仁親王 is a member of the Japanese imperial family, the younger brother of Emperor Emeritus Akihito and the head of the Hitachi-no-miya household.
  • B. 秩父宮 雍仁親王
    秩父宮 雍仁親王 was a Japanese imperial prince, younger brother of Emperor Shōwa (Hirohito), known for his military career and role in early Shōwa-era politics.
  • C. 悠仁親王
    悠仁親王は、日本の皇室に属する秋篠宮文仁親王と紀子妃の長男であり、皇位継承順位上位に位置する皇族男子である。
  • D. 三笠宮崇仁親王
    三笠宮崇仁親王は、大正天皇の第四皇子であり、昭和から平成にかけて長く存命した日本の皇族で、歴史学者としても知られた人物である。
  • E. 東久邇宮稔彦王
    東久邇宮稔彦王 was a Japanese imperial prince and military officer who briefly served as prime minister of Japan in the immediate aftermath of World War II.
  • 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.