Triple

T7551564
Position Surface form Disambiguated ID Type / Status
Subject 天神 E178545 entity
Predicate 代表的な神社 P24330 FINISHED
Object 太宰府天満宮 E201891 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: 太宰府天満宮 | Statement: [天神, 代表的な神社, 太宰府天満宮]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: 太宰府天満宮
Context triple: [天神, 代表的な神社, 太宰府天満宮]
  • A. 八坂神社
    八坂神社 is a famous Shinto shrine in Kyoto, Japan, renowned for hosting the Gion Matsuri, one of the country’s most celebrated annual festivals.
  • B. Dazaifu Tenmangū chosen
    Dazaifu Tenmangū is a major Shinto shrine in Fukuoka Prefecture, Japan, dedicated to the deified scholar and politician Sugawara no Michizane, revered as Tenjin, the god of learning.
  • C. Tsurugaoka Hachimangū
    Tsurugaoka Hachimangū is a historically significant Shinto shrine in Kamakura, Japan, closely associated with the samurai and the Minamoto (Genji) clan.
  • D. 意賀美神社
    意賀美神社は、大阪府枚方市に鎮座し、古くから地域の人々に親しまれている歴史ある神社です。
  • E. Miyazaki Shrine
    Miyazaki Shrine is a historic Shinto shrine in Miyazaki, Japan, dedicated to Emperor Jimmu and known for its tranquil forested grounds and traditional festivals.
  • 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_69c69f2cbe08819088f9eb0c03ef529b completed March 27, 2026, 3:15 p.m.
NER Named-entity recognition batch_69c7017134608190bd51fb2d0ab1ff34 completed March 27, 2026, 10:15 p.m.
NED1 Entity disambiguation (via context triple) batch_69c856bb83b88190947c0efed84b891a completed March 28, 2026, 10:31 p.m.
Created at: March 27, 2026, 3:49 p.m.