Triple

T38085873
Position Surface form Disambiguated ID Type / Status
Subject Kasugayama Castle E950974 entity
Predicate near P350 FINISHED
Object Rinsen-ji Temple
Rinsen-ji Temple is a historic Buddhist temple in Japan known for its association with the warlord Uesugi Kenshin, who is said to have studied there in his youth.
E2288651 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: Rinsen-ji Temple | Statement: [Kasugayama Castle, near, Rinsen-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: Rinsen-ji Temple
Triple: [Kasugayama Castle, near, Rinsen-ji Temple]
Generated description
Rinsen-ji Temple is a historic Buddhist temple in Japan known for its association with the warlord Uesugi Kenshin, who is said to have studied there in his youth.

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_69f76f03a3608190a73fd6df87c792a8 completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fc456f33048190a303b87c366a64c8 completed May 7, 2026, 7:55 a.m.
NED1 Entity disambiguation (via context triple) batch_6a5aa643e2148190b99412d1291ec77e completed July 17, 2026, 10:01 p.m.
NEDg Description generation batch_6a5aa6d0ab94819092469a3a90ccd344 completed July 17, 2026, 10:04 p.m.
NED2 Entity disambiguation (via description) batch_6a5aabd4c84c8190854d635ec3c074fa completed July 17, 2026, 10:25 p.m.
Created at: May 3, 2026, 4:21 p.m.