Triple

T31665644
Position Surface form Disambiguated ID Type / Status
Subject Yoshida Shrine E808116 entity
Predicate associatedWithFamily P566 FINISHED
Object Yoshida family
The Yoshida family is a historically significant Japanese clan closely linked to Shinto ritual authority and the traditions centered around Kyoto’s Yoshida Shrine.
E1984447 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: Yoshida family | Statement: [Yoshida Shrine, associatedWithFamily, Yoshida family]
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: Yoshida family
Triple: [Yoshida Shrine, associatedWithFamily, Yoshida family]
Generated description
The Yoshida family is a historically significant Japanese clan closely linked to Shinto ritual authority and the traditions centered around Kyoto’s Yoshida Shrine.

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_69f348dbeef4819080b446a7feb6340b completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6aa29247881909fd865399696c58a completed May 3, 2026, 1:51 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2e8a1925788190b93fd88116391842 completed June 14, 2026, 11:01 a.m.
NEDg Description generation batch_6a2e8aba8d9481908df3439168b0f62f completed June 14, 2026, 11:04 a.m.
NED2 Entity disambiguation (via description) batch_6a2e8b6f6f2c819098e1787c61964edd completed June 14, 2026, 11:07 a.m.
Created at: April 30, 2026, 10:59 p.m.