Triple
T5688122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dehu |
E125360
|
entity |
| Predicate | hasFestivalActivity |
P2955
|
FINISHED |
| Object | kirtan and bhajan programs |
—
|
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: kirtan and bhajan programs | Statement: [Dehu, hasFestivalActivity, kirtan and bhajan programs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFestivalActivity Context triple: [Dehu, hasFestivalActivity, kirtan and bhajan programs]
-
A.
hasFestival
Indicates that a location, community, or entity hosts or holds a festival or celebratory event.
-
B.
hasFestivalContext
Indicates that something is related to, occurs within, or is characterized by the setting, activities, or circumstances of a festival.
-
C.
hasCulturalEvent
chosen
Indicates that a cultural event (such as a festival, performance, or exhibition) takes place in, is associated with, or is hosted by a given entity.
-
D.
hasFestivalImportance
Indicates that something holds notable significance, relevance, or prominence within the context of a festival or festive event.
-
E.
determinesFestival
Indicates that one entity decides, defines, or selects which festival is applicable or will occur for another entity or context.
- 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_69c0082a884c8190a79001bae658941f |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0248751bc8190b12aaa42d1ef17e3 |
completed | March 22, 2026, 5:19 p.m. |
| PD | Predicate disambiguation | batch_69c021be59088190a81c880957f666ab |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:44 p.m.