Triple

T33920940
Position Surface form Disambiguated ID Type / Status
Subject Noto Peninsula E869604 entity
Predicate hasLandmark P105 FINISHED
Object Soji-ji Temple
Soji-ji Temple is one of the two main head temples of the Sōtō school of Zen Buddhism in Japan, renowned for its historic architecture and serene monastic atmosphere.
E2285503 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: Soji-ji Temple | Statement: [Noto Peninsula, hasLandmark, Soji-ji Temple]
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: Soji-ji Temple
Triple: [Noto Peninsula, hasLandmark, Soji-ji Temple]
Generated description
Soji-ji Temple is one of the two main head temples of the Sōtō school of Zen Buddhism in Japan, renowned for its historic architecture and serene monastic atmosphere.

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_69f349992c508190aa4afa24a086cc8c completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f701eba5d48190854e10c68a6b4da7 completed May 3, 2026, 8:06 a.m.
NED1 Entity disambiguation (via context triple) batch_6a45f1e5484c819080b4fa4809cc17b2 completed July 2, 2026, 5:06 a.m.
NEDg Description generation batch_6a45f62ded008190a5ac436d6af1a661 completed July 2, 2026, 5:25 a.m.
NED2 Entity disambiguation (via description) batch_6a45f73fb2d48190b50aac074636e7a4 completed July 2, 2026, 5:29 a.m.
Created at: May 1, 2026, 1:49 a.m.