Triple
T28010556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Izumo Shinto |
E707404
|
entity |
| Predicate | centeredOnShrineTraditionsOf |
P27875
|
FINISHED |
| Object | Izumo Taisha |
—
|
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: Izumo Taisha | Statement: [Izumo Shinto, centeredOnShrineTraditionsOf, Izumo Taisha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centeredOnShrineTraditionsOf Context triple: [Izumo Shinto, centeredOnShrineTraditionsOf, Izumo Taisha]
-
A.
ritualCentersOn
Indicates that a ritual is primarily focused on, organized around, or thematically centered on a particular entity, object, or concept.
-
B.
shrineSignificance
Indicates the cultural, religious, or historical importance attributed to a particular shrine within its context.
-
C.
enshrines
Indicates that one entity formally preserves, protects, or honors another by giving it a permanent, often sacred or legally recognized, status.
-
D.
associatedShrine
chosen
Indicates that there is a specific shrine linked or connected to the given entity, typically as its dedicated or related place of worship or reverence.
-
E.
typicalShrineFeature
Indicates that something is a characteristic or commonly found element of a shrine.
- 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_69f65876c52c8190bc889c7a67bd07f3 |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 27, 2026, 8:03 p.m.