Triple
T24288281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tōshō Daigongen |
E605734
|
entity |
| Predicate | relatedDeityType |
P102272
|
FINISHED |
| Object | gongen syncretic deity |
—
|
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: gongen syncretic deity | Statement: [Tōshō Daigongen, relatedDeityType, gongen syncretic deity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedDeityType Context triple: [Tōshō Daigongen, relatedDeityType, gongen syncretic deity]
-
A.
relatedNameOfGod
Indicates that one entity is a name, title, or designation that refers to or is associated with God.
-
B.
relatedDeityResidence
Indicates that a deity is associated with, dwells in, or is traditionally believed to reside in a particular place or realm.
-
C.
relationshipToDeities
Indicates how an entity is connected or related to one or more deities, such as through worship, lineage, role, or status.
-
D.
associatedDeityOrForce
chosen
Indicates that one entity is linked to, represented by, or under the influence of a particular deity or supernatural force.
-
E.
sharesDeitiesWith
Indicates that two entities have one or more deities in common within their respective religious or mythological systems.
- 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_69e295480d0c8190846fc3c2e2da1d4c |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28f57a9a08190b183879ff76071d0 |
completed | April 29, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:08 a.m.