Triple

T22453800
Position Surface form Disambiguated ID Type / Status
Subject Ako Gishi Festival E555059 entity
Predicate associatedWithPlace P2830 FINISHED
Object Oishi Shrine
Oishi Shrine is a Shinto shrine in Ako, Japan, best known for honoring Ōishi Kuranosuke and the Forty-seven Ronin, central figures in the Ako Gishi Festival.
E1894369 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: Oishi Shrine | Statement: [Ako Gishi Festival, associatedWithPlace, Oishi Shrine]
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: Oishi Shrine
Triple: [Ako Gishi Festival, associatedWithPlace, Oishi Shrine]
Generated description
Oishi Shrine is a Shinto shrine in Ako, Japan, best known for honoring Ōishi Kuranosuke and the Forty-seven Ronin, central figures in the Ako Gishi Festival.

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_69e11e5113208190ab58c6b595f9d1d0 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15b4d6368819082cafbbd83339fbf completed April 29, 2026, 1:13 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2721c7068c8190b5c7456557837b36 completed June 8, 2026, 8:10 p.m.
NEDg Description generation batch_6a272333f384819084456b384bc17a6c completed June 8, 2026, 8:16 p.m.
NED2 Entity disambiguation (via description) batch_6a2723e6c6648190801fec9c9fd7f557 completed June 8, 2026, 8:19 p.m.
Created at: April 16, 2026, 8:48 p.m.