Triple

T21887443
Position Surface form Disambiguated ID Type / Status
Subject 玉依姫 E540442 entity
Predicate 別名 P39 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. 櫛稲田姫命
    櫛稲田姫命 is a Japanese Shinto goddess associated with marriage, protection, and agriculture, best known as the wife of the storm god Susanoo.
  • B. Azaihime-no-mikoto
    Azaihime-no-mikoto is a Shinto goddess venerated at Chikubu Island, often associated with local protective and benevolent divine powers.
  • C. Inahi no Mikoto
    Inahi no Mikoto is a deity in Japanese mythology, known as one of the divine offspring in the lineage leading to the imperial family.
  • D. Kamo Tamayori-hime no Mikoto chosen
    Kamo Tamayori-hime no Mikoto is a Shinto goddess of the Kamo Shrine in Kyoto, revered as a divine ancestress and mother of the thunder deity Kamo Wake-ikazuchi.
  • E. Tagitsuhime-no-Mikoto
    Tagitsuhime-no-Mikoto is a Shinto goddess, one of the three Munakata deities associated with seas, navigation, and protection, venerated at major shrines in Japan.
  • 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_69e0c47a95908190ae3e19b716accb3d completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f118ed35948190bbffba2c40029eee completed April 28, 2026, 8:30 p.m.
Created at: April 16, 2026, 7:05 p.m.