Triple
T7016283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dakshineswar Kali Temple |
E162706
|
entity |
| Predicate | primaryFestival |
P41325
|
FINISHED |
| Object | Kali Puja |
—
|
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: Kali Puja | Statement: [Dakshineswar Kali Temple, primaryFestival, Kali Puja]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryFestival Context triple: [Dakshineswar Kali Temple, primaryFestival, Kali Puja]
-
A.
mainFestival
chosen
Indicates that an event is the primary or central festival associated with a particular context, place, or entity.
-
B.
festivalFocus
Indicates that a festival is centered around, dedicated to, or thematically focused on a particular subject, activity, or feature.
-
C.
primaryHoliday
Indicates that one holiday is the main or most significant holiday associated with a given entity, time, or context.
-
D.
festivalSeason
Indicates that a time period is designated or recognized as the season during which a particular festival or set of festivals takes place.
-
E.
festivalObserved
Indicates that a particular festival is celebrated, observed, or commemorated by an entity (such as a person, group, or community).
- 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_69c6885a127c8190867b059bdccf13ff |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e5ecd4488190bf19e42de55da98b |
completed | March 27, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69c6e1b8118481909d76eb6616160e80 |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:34 p.m.