Triple

T11603965
Position Surface form Disambiguated ID Type / Status
Subject Shibuya-ku E275204 entity
Predicate contains P35 FINISHED
Object Meiji Shrine E26789 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: Meiji Shrine | Statement: [Shibuya-ku, contains, Meiji Shrine]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Meiji Shrine
Context triple: [Shibuya-ku, contains, Meiji Shrine]
  • A. Meiji Shrine chosen
    Meiji Shrine is a major Shinto shrine in Tokyo dedicated to Emperor Meiji and Empress Shōken, known for its expansive forested grounds and traditional ceremonies.
  • B. Nezu Shrine
    Nezu Shrine is a historic Shinto shrine in Tokyo renowned for its lush grounds, vermilion torii tunnel, and traditional architecture.
  • C. Kamigamo Shrine
    Kamigamo Shrine is one of Kyoto’s oldest and most important Shinto shrines, renowned for its historic architecture and role in the Kamo faith tradition.
  • D. Fushimi Inari Taisha
    Fushimi Inari Taisha is a famous Shinto shrine in Japan renowned for its thousands of vermilion torii gates winding up the forested slopes of Mount Inari.
  • E. Hirota Shrine
    Hirota Shrine is a historic Shinto shrine in Nishinomiya, Hyōgo Prefecture, revered as one of the region’s principal religious sites.
  • 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_69d6aaf84b548190ac072e4fb89ae18f completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d895502e0081909ee9c3d45d26cd91 completed April 10, 2026, 6:14 a.m.
NED1 Entity disambiguation (via context triple) batch_69f6f5b196bc8190a643f2b534497476 completed May 3, 2026, 7:13 a.m.
Created at: April 8, 2026, 9:38 p.m.