Triple

T11433834
Position Surface form Disambiguated ID Type / Status
Subject Empress Genshō E270954 entity
Predicate personalName P24312 FINISHED
Object Abe-hime E926010 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: Abe-hime | Statement: [Empress Genshō, personalName, Abe-hime]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Abe-hime
Context triple: [Empress Genshō, personalName, Abe-hime]
  • A. Hidaka-hime chosen
    Hidaka-hime is the birth name of Empress Genshō, a Nara-period Japanese empress who ruled in the early 8th century.
  • B. 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.
  • C. 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.
  • D. Himegami
    Himegami is a Shinto deity venerated in Japan, associated with sacred shrines and traditional religious worship.
  • E. Nōhime
    Nōhime was a 16th-century Japanese noblewoman, traditionally regarded as the politically significant but enigmatic wife of the warlord Oda Nobunaga.
  • 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_69d6aadeef688190874bcecd88b3dd9b completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d806c485f481909dd3d9b0993f3faf completed April 9, 2026, 8:06 p.m.
NED1 Entity disambiguation (via context triple) batch_69e5e8ed579c8190b1ddc1dce20d9617 completed April 20, 2026, 8:50 a.m.
Created at: April 8, 2026, 9:35 p.m.