Triple

T16744216
Position Surface form Disambiguated ID Type / Status
Subject Aoshima Shrine E406906 entity
Predicate dedicatedTo P500 FINISHED
Object Toyotama-hime E126333 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: Toyotama-hime | Statement: [Aoshima Shrine, dedicatedTo, Toyotama-hime]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Toyotama-hime
Context triple: [Aoshima Shrine, dedicatedTo, Toyotama-hime]
  • A. Tamayori-hime chosen
    Tamayori-hime is a goddess in Japanese mythology, often associated with water and the sea, revered as the mother of Japan’s legendary first emperor, Emperor Jimmu.
  • B. Hidaka-hime
    Hidaka-hime is the birth name of Empress Genshō, a Nara-period Japanese empress who ruled in the early 8th century.
  • C. 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.
  • D. Yakami-hime
    Yakami-hime is a goddess in Japanese mythology known as a consort of the deity Ōkuninushi and as a figure in the Izumo cycle of legends.
  • E. Himegami
    Himegami is a Shinto deity venerated in Japan, associated with sacred shrines and traditional religious worship.
  • 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_69d8838ffb088190a0b11149929006bf completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e3aa210ef88190be74bd60d7144953 completed April 18, 2026, 3:58 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00a51e69c08190a5bff74823df430c completed May 10, 2026, 3:32 p.m.
Created at: April 10, 2026, 5:21 a.m.