Triple
T35911626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matsunoo Taisha |
E1038629
|
entity |
| Predicate | hasKami |
P84166
|
FINISHED |
| Object | Ōyamakui-no-kami |
—
|
NE NERFINISHED |
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: Ōyamakui-no-kami | Statement: [Matsunoo Taisha, hasKami, Ōyamakui-no-kami]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKami Context triple: [Matsunoo Taisha, hasKami, Ōyamakui-no-kami]
-
A.
hasKamiType
Indicates that an entity is associated with or classified under a specific type or category of kami.
-
B.
hasPrimaryKami
chosen
Indicates that an entity is associated with or devoted to a specific main kami (deity) as its primary spiritual focus or guardian.
-
C.
hasKata
Indicates that an entity possesses, practices, or is associated with a specific kata (a formalized sequence of movements or techniques).
-
D.
hasOmamori
Indicates that one entity possesses or is associated with an omamori (a protective charm or amulet).
-
E.
createdKami
Indicates that one entity brought a kami (a divine or spiritual being) into existence or was responsible for its creation.
- F. None of above.
Provenance (3 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. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:07 p.m.