Triple

T15158795
Position Surface form Disambiguated ID Type / Status
Subject Hozuki-ichi E362151 entity
Predicate associatedWith P37 FINISHED
Object Senso-ji 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: Senso-ji | Statement: [Hozuki-ichi, associatedWith, Senso-ji]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Senso-ji
Context triple: [Hozuki-ichi, associatedWith, Senso-ji]
  • A. Senso-ji Temple chosen
    Senso-ji Temple is Tokyo’s oldest and most famous Buddhist temple, renowned for its iconic Kaminarimon gate and bustling Nakamise shopping street.
  • B. Ryōzenji
    Ryōzenji is a Buddhist temple in Tokushima Prefecture, Japan, best known as the traditional starting point of the Shikoku 88-temple pilgrimage.
  • C. Shitenno-ji
    Shitenno-ji is one of Japan’s oldest Buddhist temples, founded in Osaka in the 6th century and renowned as a major historical and religious site.
  • D. Shiromine-ji
    Shiromine-ji is a Buddhist temple in Kagawa Prefecture, Japan, known as Temple 81 on the Shikoku Pilgrimage.
  • E. Shōsan-ji
    Shōsan-ji is a Buddhist temple in Tokushima Prefecture, Japan, known as Temple 12 on the Shikoku Pilgrimage.
  • 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_69d85a087b7c81908baa94a53dac8d68 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e0060dd71881908ecc4a4f52d438a5 completed April 15, 2026, 9:41 p.m.
Created at: April 10, 2026, 3:08 a.m.