Triple

T1145848
Position Surface form Disambiguated ID Type / Status
Subject 皇室 E23562 entity
Predicate member P10 FINISHED
Object 紀子妃 E73393 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: [皇室, member, 紀子妃]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: 紀子妃
Context triple: [皇室, member, 紀子妃]
  • A. Empress Masako
    Empress Masako is the current Empress of Japan, a Harvard-educated former diplomat known for her international background and marriage to Emperor Naruhito.
  • B. 敬宮愛子内親王
    敬宮愛子内親王 is the only child of Emperor Naruhito and Empress Masako of Japan and a member of the Japanese imperial family.
  • C. Empress Michiko
    Empress Michiko is the former Empress consort of Japan, renowned as the first commoner to marry into the Japanese imperial family and for her widespread popularity and humanitarian work.
  • D. Kiko, Crown Princess Akishino chosen
    Kiko, Crown Princess Akishino is a member of the Japanese imperial family who serves as the wife of Crown Prince Fumihito and is known for her public service and involvement in social and cultural activities in Japan.
  • 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_69a493ef399c8190b04b9146d2314f59 completed March 1, 2026, 7:30 p.m.
NER Named-entity recognition batch_69a4bc6e8c2081909fb3534413b7aacb completed March 1, 2026, 10:23 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac6677c7e48190ba8da088b78775a5 completed March 7, 2026, 5:55 p.m.
Created at: March 1, 2026, 7:44 p.m.