Triple

T22225718
Position Surface form Disambiguated ID Type / Status
Subject Association of Shinto Shrines E549332 entity
Predicate nativeName P15 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: [Association of Shinto Shrines, nativeName, 神社本庁]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: 神社本庁
Context triple: [Association of Shinto Shrines, nativeName, 神社本庁]
  • A. 神社本庁 chosen
    神社本庁は、日本全国の神社を包括・統括し神道の伝統と祭祀を維持・普及する宗教法人組織です。
  • B. Iwashimizu Hachimangū
    Iwashimizu Hachimangū is an important Shinto shrine in Kyoto Prefecture, Japan, renowned as one of the principal centers of worship for the deity Hachiman and noted for its historical and cultural significance.
  • C. Umenomiya Taisha
    Umenomiya Taisha is a historic Shinto shrine in Kyoto, Japan, renowned for its sake-related rituals, plum blossoms, and association with the imperial family.
  • D. Tsurugaoka Hachimangū
    Tsurugaoka Hachimangū is a historically significant Shinto shrine in Kamakura, Japan, closely associated with the samurai and the Minamoto (Genji) clan.
  • E. Ōyamato Jinja
    Ōyamato Jinja is a historic Shinto shrine in Nara Prefecture, Japan, revered for its ancient origins and its role in the early Yamato state.
  • 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_69e11e403d6481909a94d0aaf157f6ef completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f12bee8de8819091ec5d14ea057f9e completed April 28, 2026, 9:51 p.m.
Created at: April 16, 2026, 8:37 p.m.