Triple

T8337751
Position Surface form Disambiguated ID Type / Status
Subject Hisahito E195830 entity
Predicate familyName P18 FINISHED
Object Akishino E299987 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: Akishino | Statement: [Hisahito, familyName, Akishino]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Akishino
Context triple: [Hisahito, familyName, Akishino]
  • A. Akishino chosen
    Akishino is the imperial family name of a branch of Japan’s monarchy, borne by members such as Prince Hisahito and his parents, Crown Prince Fumihito and Crown Princess Kiko.
  • B. Akiruno
    Akiruno is a city in western Tokyo, Japan, known for its natural scenery, including rivers, forests, and hiking areas.
  • C. Marunouchi
    Marunouchi is a central Tokyo business district known for its concentration of corporate headquarters, upscale offices, and proximity to Tokyo Station and the Imperial Palace.
  • D. Shibukawa
    Shibukawa is a city in Gunma Prefecture, Japan, known as a regional transport hub and gateway to nearby hot spring resorts such as Ikaho Onsen.
  • E. Higashikurume
    Higashikurume is a suburban city in western Tokyo, Japan, known for its residential neighborhoods and role as a commuter area for central Tokyo.
  • 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_69ca82ecbdc481908a55cad8ca062d88 completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cb7fd5027c81909724f25aa30bbe58 completed March 31, 2026, 8:03 a.m.
NED1 Entity disambiguation (via context triple) batch_69d1bc96f7288190ab8d1bbf9d428903 completed April 5, 2026, 1:36 a.m.
Created at: March 30, 2026, 5:57 p.m.