Triple

T13492357
Position Surface form Disambiguated ID Type / Status
Subject Nijūnisha E320666 entity
Predicate hasMember P10 FINISHED
Object Isonokami Jinja E297741 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: Isonokami Jinja | Statement: [Nijūnisha, hasMember, Isonokami Jinja]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Isonokami Jinja
Context triple: [Nijūnisha, hasMember, Isonokami Jinja]
  • A. Isonokami Shrine chosen
    Isonokami Shrine is an ancient Shinto shrine in Japan, renowned for its historical significance and legendary association with early imperial and military traditions.
  • B. Ō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.
  • C. Hirota Jinja
    Hirota Jinja is an ancient and historically significant Shinto shrine in Japan, revered for its imperial connections and longstanding religious importance.
  • D. Shirayama Hime Jinja
    Shirayama Hime Jinja is a prominent Shinto shrine in Japan revered for its ancient worship of Mount Hakusan and its role as a central spiritual site in the region.
  • E. Hirano Jinja
    Hirano Jinja is a historic Shinto shrine in Kyoto, Japan, renowned for its cherry blossoms and imperial patronage.
  • 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_69d807629d6c8190998f1b9bb12d2ed0 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbaf4c66008190b287e0551889d7c8 completed April 12, 2026, 2:42 p.m.
NED1 Entity disambiguation (via context triple) batch_6a02163209608190aa36abc63bc2b4e3 completed May 11, 2026, 5:47 p.m.
Created at: April 9, 2026, 9:43 p.m.