Triple
T8861503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ishiyama-dera |
E210897
|
entity |
| Predicate | deityCategory |
P85058
|
FINISHED |
| Object | Kannon temple |
—
|
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: Kannon temple | Statement: [Ishiyama-dera, deityCategory, Kannon temple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deityCategory Context triple: [Ishiyama-dera, deityCategory, Kannon temple]
-
A.
typeOfDeity
Indicates that one entity is classified as a specific kind or category of deity in relation to another.
-
B.
discussesDeity
Indicates that one entity talks or writes about, analyzes, or otherwise engages in discourse concerning a deity or divine being.
-
C.
otherDeity
Indicates that one deity is distinct from and not identical to another deity within a given context or system.
-
D.
deityDomain
Indicates that a deity has authority, influence, or primary association over a particular domain, aspect, or sphere of existence.
-
E.
mainDeity
Indicates that one entity serves as the primary or chief deity worshiped, revered, or associated with another entity (such as a religion, temple, or culture).
- F. None of above. chosen
Provenance (4 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_69ca838bbddc8190ab546d737e5d350f |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60e860888190a8a8702377db949e |
completed | April 1, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69cc5c279ea481908c71756f694b66bf |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cffe8ec819084c12770fe0578f2 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:50 p.m.