Triple
T7608194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hiromine Shrine |
E180161
|
entity |
| Predicate | hasWorshipType |
P11149
|
FINISHED |
| Object | kami worship |
—
|
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 worship | Statement: [Hiromine Shrine, hasWorshipType, kami worship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorshipType Context triple: [Hiromine Shrine, hasWorshipType, kami worship]
-
A.
worshipType
chosen
Indicates the manner or form in which worship is practiced or expressed in a religious or spiritual context.
-
B.
worshipperType
Indicates the specific category or kind of worshipper involved in a religious or devotional relationship or action.
-
C.
hasWorshipSpaceFeature
Indicates that a worship space possesses or includes a particular feature, characteristic, or facility.
-
D.
hasReligiousInstitutionType
Indicates that an entity is associated with, or classified by, a specific type of religious institution.
-
E.
worshipsDeity
Indicates that one entity reveres, honors, or performs religious devotion toward another entity regarded as a deity.
- 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_69c69f3567008190ab01d2ca7b53584a |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6fa1de8a4819091f9e9347835ce16 |
completed | March 27, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e485f88190910b39da52a955fe |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:54 p.m.