Triple

T27004708
Position Surface form Disambiguated ID Type / Status
Subject Tenchi Kane no Kami E680209 entity
Predicate nameMeaning P453 FINISHED
Object “Tenchi” refers to heaven and earth
Tenchi Kane no Kami is a Shinto deity whose name evokes the unification and divine governance of heaven and earth.
E1749937 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: “Tenchi” refers to heaven and earth | Statement: [Tenchi Kane no Kami, nameMeaning, “Tenchi” refers to heaven and earth]
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: “Tenchi” refers to heaven and earth
Triple: [Tenchi Kane no Kami, nameMeaning, “Tenchi” refers to heaven and earth]
Generated description
Tenchi Kane no Kami is a Shinto deity whose name evokes the unification and divine governance of heaven and earth.

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_69eeeb52908c8190bd246244686aa455 completed April 27, 2026, 4:51 a.m.
NER Named-entity recognition batch_69f621d139f081909f9ca04e04095dba completed May 2, 2026, 4:09 p.m.
NED1 Entity disambiguation (via context triple) batch_6a1229c052708190901aab4506fdb248 completed May 23, 2026, 10:27 p.m.
NEDg Description generation batch_6a122a3a3b3c8190ab41feb5652546bb completed May 23, 2026, 10:29 p.m.
NED2 Entity disambiguation (via description) batch_6a122add10688190aa06ce1d690c1867 completed May 23, 2026, 10:31 p.m.
Created at: April 27, 2026, 7 a.m.