Triple
T12613989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kamo Wake-ikazuchi no Kami |
E301203
|
entity |
| Predicate | worshipPlaceType |
P34373
|
FINISHED |
| Object | Shinto shrine |
—
|
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: Shinto shrine | Statement: [Kamo Wake-ikazuchi no Kami, worshipPlaceType, Shinto shrine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worshipPlaceType Context triple: [Kamo Wake-ikazuchi no Kami, worshipPlaceType, Shinto shrine]
-
A.
religiousBuildingInstanceOf
Indicates that a specific religious building is an instance of a particular class or type of religious building.
-
B.
hasPlaceOfWorship
Indicates that an entity possesses, contains, or is associated with a designated location used for religious or spiritual worship.
-
C.
isPlaceOfWorshipFor
Indicates that a location serves as a site where members of a particular religion or belief system perform worship or religious practices.
-
D.
religiousSiteType
chosen
Indicates the specific kind or category of religious site associated with an entity (e.g., church, mosque, temple).
-
E.
religiousServiceType
Indicates the specific kind or category of religious service associated with an event or context.
- 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_69d7bdeaf49c8190b13800111fa77ea3 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9617b07ec8190b714f04ae6654060 |
completed | April 10, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69d960b195108190ac25bd95e644ace4 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:12 p.m.