Triple

T25213501
Position Surface form Disambiguated ID Type / Status
Subject Atsuta Jingū E631758 entity
Predicate enshrines P2950 FINISHED
Object Take Inadane no Mikoto
Take Inadane no Mikoto is a Shinto deity venerated at Atsuta Jingū, traditionally regarded as an ancestral or protective kami associated with the shrine’s sacred lineage.
E1667317 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: Take Inadane no Mikoto | Statement: [Atsuta Jingū, enshrines, Take Inadane no Mikoto]
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: Take Inadane no Mikoto
Triple: [Atsuta Jingū, enshrines, Take Inadane no Mikoto]
Generated description
Take Inadane no Mikoto is a Shinto deity venerated at Atsuta Jingū, traditionally regarded as an ancestral or protective kami associated with the shrine’s sacred lineage.

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_69e75a8d1aa48190a4320acd3654762c completed April 21, 2026, 11:07 a.m.
NER Named-entity recognition batch_69f47b8b12ac8190bc77d9d11a29131b completed May 1, 2026, 10:08 a.m.
NED1 Entity disambiguation (via context triple) batch_6a105d34bcf0819083ebd5a10110886d completed May 22, 2026, 1:42 p.m.
NEDg Description generation batch_6a105e32237c8190ba397b04b9692e7b completed May 22, 2026, 1:46 p.m.
NED2 Entity disambiguation (via description) batch_6a105f4ef2648190a3b26415b711b171 completed May 22, 2026, 1:51 p.m.
Created at: April 21, 2026, 12:58 p.m.