Triple

T24800834
Position Surface form Disambiguated ID Type / Status
Subject Kagutsuchi E620517 entity
Predicate otherName P39 FINISHED
Object Hinokagutsuchi-no-kami
Hinokagutsuchi-no-kami is a Japanese fire deity, revered in Shinto mythology as a powerful and often destructive kami associated with flames and volcanic phenomena.
E1691887 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: Hinokagutsuchi-no-kami | Statement: [Kagutsuchi, otherName, Hinokagutsuchi-no-kami]
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: Hinokagutsuchi-no-kami
Triple: [Kagutsuchi, otherName, Hinokagutsuchi-no-kami]
Generated description
Hinokagutsuchi-no-kami is a Japanese fire deity, revered in Shinto mythology as a powerful and often destructive kami associated with flames and volcanic phenomena.

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_69e2fabf26bc8190b191faac8f67065b completed April 18, 2026, 3:30 a.m.
NER Named-entity recognition batch_69f412a9b64881908ed86b9c9b044635 completed May 1, 2026, 2:40 a.m.
NED1 Entity disambiguation (via context triple) batch_6a10c10760a4819089c46eae89f764cd completed May 22, 2026, 8:48 p.m.
NEDg Description generation batch_6a10c25f38548190a7487c7cb829bce0 completed May 22, 2026, 8:53 p.m.
NED2 Entity disambiguation (via description) batch_6a10c4dc54f481909f2e06eaa2d15d43 completed May 22, 2026, 9:04 p.m.
Created at: April 18, 2026, 4:49 a.m.