Triple
T38580754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inari worship |
E932236
|
entity |
| Predicate | hasSyncreticForm |
P20349
|
FINISHED |
| Object | Buddhist Inari cult |
—
|
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: Buddhist Inari cult | Statement: [Inari worship, hasSyncreticForm, Buddhist Inari cult]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSyncreticForm Context triple: [Inari worship, hasSyncreticForm, Buddhist Inari cult]
-
A.
isCombinedFormOf
Indicates that one entity is a composite or merged form that results from combining two or more other entities.
-
B.
laterSyncretizedWith
chosen
Indicates that one element was subsequently merged or conflated with another into a single, combined form or identity.
-
C.
hasLanguageFormOf
Indicates that one entity is a specific linguistic form, expression, or realization of the language used by another entity.
-
D.
hasSyncreticDeity
Indicates that one deity is a composite or fusion of multiple distinct deities, combining their attributes or identities into a single syncretic figure.
-
E.
hasMorphologicalForm
Indicates that one entity is a specific morphological form or inflected variant of another entity.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.