Triple

T20920359
Position Surface form Disambiguated ID Type / Status
Subject Bungo Province E515189 entity
Predicate containsShrine P114896 FINISHED
Object Yusuhara Hachiman-gū
Yusuhara Hachiman-gū is a historic Shinto shrine dedicated to the war god Hachiman, located in the former Bungo Province on Japan’s Kyushu island.
E1623763 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: Yusuhara Hachiman-gū | Statement: [Bungo Province, containsShrine, Yusuhara Hachiman-gū]
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: Yusuhara Hachiman-gū
Triple: [Bungo Province, containsShrine, Yusuhara Hachiman-gū]
Generated description
Yusuhara Hachiman-gū is a historic Shinto shrine dedicated to the war god Hachiman, located in the former Bungo Province on Japan’s Kyushu island.

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_69e0b4f9d5ec8190bb2bd27350ed341c completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6ec677338819081410cbaa2846260 completed April 21, 2026, 3:17 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0fbcd6237c8190815702e274a30c44 completed May 22, 2026, 2:17 a.m.
NEDg Description generation batch_6a0fbddd0ccc81908036002270cbf4f5 completed May 22, 2026, 2:22 a.m.
NED2 Entity disambiguation (via description) batch_6a0fbf3f6c4481908f8dcd0168ee16a2 completed May 22, 2026, 2:28 a.m.
Created at: April 16, 2026, 12:48 p.m.