Triple
T28010565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Izumo Shinto |
E707404
|
entity |
| Predicate | emphasizesRitual |
P25858
|
FINISHED |
| Object | kami‑oroshi and kami‑mukae welcoming of deities |
—
|
LITERAL 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: kami‑oroshi and kami‑mukae welcoming of deities | Statement: [Izumo Shinto, emphasizesRitual, kami‑oroshi and kami‑mukae welcoming of deities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emphasizesRitual Context triple: [Izumo Shinto, emphasizesRitual, kami‑oroshi and kami‑mukae welcoming of deities]
-
A.
ritualsDirectedAt
Indicates that certain rituals are performed with a specific entity, object, or target as their intended focus or recipient.
-
B.
ritualSignificance
Indicates that something holds special importance or meaning within a ritual or ceremonial context.
-
C.
ritualAttitude
Indicates an entity’s characteristic stance, mindset, or emotional orientation toward a ritual or ritual practice.
-
D.
usesRitually
Indicates that an entity employs or performs something as part of a ritual or ceremonial practice.
-
E.
ritualCharacteristics
chosen
Indicates the defining features, practices, or attributes that characterize a particular ritual.
- 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_69f63fd79e4c8190af9263b679e5ff07 |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 8:03 p.m.