Triple

T30192246
Position Surface form Disambiguated ID Type / Status
Subject Ishite-ji E767521 entity
Predicate hasStructure P35 FINISHED
Object Main hall (Hondō)
The Main Hall (Hondō) of Ishite-ji is the temple’s principal worship hall, housing its most sacred Buddhist images and serving as the central focus of religious ceremonies.
E1902984 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: Main hall (Hondō) | Statement: [Ishite-ji, hasStructure, Main hall (Hondō)]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Main hall (Hondō)
Triple: [Ishite-ji, hasStructure, Main hall (Hondō)]
Generated description
The Main Hall (Hondō) of Ishite-ji is the temple’s principal worship hall, housing its most sacred Buddhist images and serving as the central focus of religious ceremonies.

Provenance (5 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_69f2247db1108190835c0727c97637c3 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f67f84b03c8190a2574fde91d86e8c completed May 2, 2026, 10:49 p.m.
NED1 Entity disambiguation (via context triple) batch_6a27587433788190b0d9d67b9bd6a21c completed June 9, 2026, 12:04 a.m.
NEDg Description generation batch_6a275a7e7e78819088b7aef8057de369 completed June 9, 2026, 12:12 a.m.
NED2 Entity disambiguation (via description) batch_6a275b67290c8190bb71f367c87d8e09 completed June 9, 2026, 12:16 a.m.
Created at: April 29, 2026, 7:29 p.m.