Triple
T19596648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shichifukujin |
E470364
|
entity |
| Predicate | festivalOrRitual |
P38636
|
FINISHED |
| Object | New Year customs in Japan |
—
|
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: New Year customs in Japan | Statement: [Shichifukujin, festivalOrRitual, New Year customs in Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: festivalOrRitual Context triple: [Shichifukujin, festivalOrRitual, New Year customs in Japan]
-
A.
ritualEvent
Indicates that an event is a ritual or ceremonial occurrence, typically involving prescribed actions, symbols, or practices performed according to tradition or custom.
-
B.
ritualActivities
Indicates that one entity engages in, performs, or is associated with ritualistic or ceremonial activities in relation to another entity or context.
-
C.
festivalObserved
chosen
Indicates that a particular festival is celebrated, observed, or commemorated by an entity (such as a person, group, or community).
-
D.
ritualCategory
Indicates the classification relationship that assigns a ritual to a specific ritual type or category.
-
E.
religiousEvent
Indicates that an event is related to religious practices, observances, or ceremonies.
- 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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e6407b997881909762c8f919c9cdad |
completed | April 20, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69e514e166dc8190a0f147e0b4c8bbe7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:43 p.m.