Triple

T35911625
Position Surface form Disambiguated ID Type / Status
Subject Matsunoo Taisha E1038629 entity
Predicate dedicatedTo P500 FINISHED
Object Nakatsu-shima-hime-no-mikoto
Nakatsu-shima-hime-no-mikoto is a Shinto kami associated with water and maritime safety, venerated at shrines such as Matsunoo Taisha in Japan.
E2164208 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: Nakatsu-shima-hime-no-mikoto | Statement: [Matsunoo Taisha, dedicatedTo, Nakatsu-shima-hime-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: Nakatsu-shima-hime-no-mikoto
Triple: [Matsunoo Taisha, dedicatedTo, Nakatsu-shima-hime-no-mikoto]
Generated description
Nakatsu-shima-hime-no-mikoto is a Shinto kami associated with water and maritime safety, venerated at shrines such as Matsunoo Taisha in Japan.

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_69f76e2259608190bf6788a132e0d139 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7aaa2525081909a333b254f7059c6 completed May 3, 2026, 8:05 p.m.
NED1 Entity disambiguation (via context triple) batch_6a38b6f3b9348190937c431261b62113 completed June 22, 2026, 4:15 a.m.
NEDg Description generation batch_6a38b99bb6208190a405edbbb167fc18 completed June 22, 2026, 4:27 a.m.
NED2 Entity disambiguation (via description) batch_6a38ba4fb2208190916ce3c32af96635 completed June 22, 2026, 4:30 a.m.
Created at: May 3, 2026, 4:07 p.m.