Triple
T26024496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashihara-no-Nakatsukuni |
E647252
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | location in Shinto cosmology |
C43717
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: location in Shinto cosmology Context triple: [Ashihara-no-Nakatsukuni, instanceOf, location in Shinto cosmology]
-
A.
Shinto shrine classification
Shinto shrine classification is the conceptual system for categorizing Shinto shrines based on factors such as their enshrined deities, historical rank, regional location, and ritual functions within Japanese religious practice.
-
B.
Shinto mythological event
A Shinto mythological event is a significant occurrence or episode in Japanese Shinto tradition involving kami (deities or spirits), sacred places, and ritual actions that explain the origins, order, or spiritual nature of the world.
-
C.
Shinto concept
chosen
A Shinto concept is an idea, belief, or principle rooted in Japan’s indigenous Shinto tradition, often relating to kami (spirits), ritual purity, harmony with nature, and the sacredness of everyday life.
-
D.
Shugendō sacred site
A Shugendō sacred site is a mountainous religious landscape—often including temples, pilgrimage routes, and natural features—used for ascetic practices that blend Shinto, Buddhism, and indigenous mountain worship.
-
E.
Shinto religious role
A Shinto religious role is a position or office within Shinto practice responsible for conducting rituals, maintaining shrines, and mediating between kami (spirits) and the community.
- F. None of above.
Provenance (1 batch)
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_69e77e8b60e88190a3b26c4f0032a2c2 |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 22, 2026, 9:05 a.m.