Triple
T37399780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tōka Ebisu Festival |
E928960
|
entity |
| Predicate | deityRoleOfEbisu |
P118406
|
FINISHED |
| Object | god of prosperity |
—
|
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: god of prosperity | Statement: [Tōka Ebisu Festival, deityRoleOfEbisu, god of prosperity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deityRoleOfEbisu Context triple: [Tōka Ebisu Festival, deityRoleOfEbisu, god of prosperity]
-
A.
roleInShinto
Indicates that an entity holds a particular function, status, or significance within the context of Shinto beliefs, practices, or institutions.
-
B.
roleOfReferencedDeity
chosen
Indicates that one entity specifies the function, status, or position held by a deity that is referenced in relation to another entity or context.
-
C.
deityCategory
Indicates that one entity is classified as belonging to a particular category or type of deity in relation to another entity.
-
D.
roleInKojiki
Indicates the role or function an entity holds within the narrative or structure of the Kojiki.
-
E.
appliesToDeityIn
Indicates that something (such as a rule, attribute, or statement) is relevant or applicable to a deity within a specified context or domain.
- 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_69f76ebbf79c8190b85bbcf3a6be57e4 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:16 p.m.