Triple
T28010552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Izumo Shinto |
E707404
|
entity |
| Predicate | emphasizesWorshipOf |
P2291
|
FINISHED |
| Object | Ōkuninushi |
—
|
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: Ōkuninushi | Statement: [Izumo Shinto, emphasizesWorshipOf, Ōkuninushi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emphasizesWorshipOf Context triple: [Izumo Shinto, emphasizesWorshipOf, Ōkuninushi]
-
A.
emphasizesAspectOfDeity
Indicates that one entity highlights, stresses, or draws special attention to a particular attribute, role, or dimension of a deity.
-
B.
worship
Indicates a relationship where one entity shows reverence, adoration, or religious devotion toward another entity, often recognizing it as sacred or divine.
-
C.
worshipedAs
Indicates that one entity regards and treats another as a deity or sacred figure, offering reverence, devotion, or religious honor.
-
D.
worshippedIn
chosen
Indicates that a particular deity, figure, or object of reverence is the focus of religious or spiritual worship within a specified place or context.
-
E.
worshipFocus
Indicates that one entity directs religious reverence, devotion, or adoration toward another as the primary object of worship.
- 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_69ef96ba350c81908230d0b501b974c4 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63bd9f5108190a8266bea76ef9513 |
completed | May 2, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 8:03 p.m.