Triple

T20986546
Position Surface form Disambiguated ID Type / Status
Subject Yamanashi Prefecture E516903 entity
Predicate touristAttraction P530 FINISHED
Object Erin-ji Temple
Erin-ji Temple is a historic Zen Buddhist temple in Yamanashi Prefecture, Japan, known for its traditional architecture, serene gardens, and cultural heritage.
E1648267 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: Erin-ji Temple | Statement: [Yamanashi Prefecture, touristAttraction, Erin-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: Erin-ji Temple
Triple: [Yamanashi Prefecture, touristAttraction, Erin-ji Temple]
Generated description
Erin-ji Temple is a historic Zen Buddhist temple in Yamanashi Prefecture, Japan, known for its traditional architecture, serene gardens, and cultural heritage.

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_69e0b4ffac148190bbade9f0eceb660b completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6fbe31cec8190a1007414148b8abe completed April 21, 2026, 4:24 a.m.
NED1 Entity disambiguation (via context triple) batch_6a100fc486c48190b42494cf2a047264 completed May 22, 2026, 8:11 a.m.
NEDg Description generation batch_6a10136871588190b4e4b4618ab7a400 completed May 22, 2026, 8:27 a.m.
NED2 Entity disambiguation (via description) batch_6a10140b2fec8190aa6d805f54926b56 completed May 22, 2026, 8:30 a.m.
Created at: April 16, 2026, 1:49 p.m.