Triple

T21237848
Position Surface form Disambiguated ID Type / Status
Subject Emperor Suizei E523391 entity
Predicate spouse P13 FINISHED
Object Isuzuyori-hime 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: Isuzuyori-hime | Statement: [Emperor Suizei, spouse, Isuzuyori-hime]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Isuzuyori-hime
Context triple: [Emperor Suizei, spouse, Isuzuyori-hime]
  • A. Ahiratsu-hime
    Ahiratsu-hime is a figure in Japanese imperial mythology known as the mother of Emperor Suizei, traditionally regarded as Japan’s second emperor.
  • B. Kushinadahime
    Kushinadahime is a goddess in Japanese mythology, best known as the rescued maiden whom the storm god Susanoo marries after saving her from the eight-headed serpent Yamata no Orochi.
  • C. Himetatara Isuzuhime chosen
    Himetatara Isuzuhime is a legendary figure in Japanese mythology known as the consort of Emperor Jimmu, the first emperor of Japan.
  • D. Asahi-hime
    Asahi-hime was a Japanese noblewoman of the late Sengoku period, known for her politically significant marriage into the Tokugawa clan that helped secure alliances during Japan’s unification.
  • E. Hidaka-hime
    Hidaka-hime is the birth name of Empress Genshō, a Nara-period Japanese empress who ruled in the early 8th century.
  • 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_69e0b513b89c81908b27147e91368db2 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e735212ad4819082d85f4d4342faf9 completed April 21, 2026, 8:28 a.m.
Created at: April 16, 2026, 3:46 p.m.