Triple
T37217806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baneshwar Mahadev Temple |
E922787
|
entity |
| Predicate | hasPrimaryFestivals |
P3113
|
FINISHED |
| Object | Maha Shivaratri |
E138493
|
NE 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: Maha Shivaratri | Statement: [Baneshwar Mahadev Temple, hasPrimaryFestivals, Maha Shivaratri]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryFestivals Context triple: [Baneshwar Mahadev Temple, hasPrimaryFestivals, Maha Shivaratri]
-
A.
hasFestival
chosen
Indicates that a location, community, or entity hosts or holds a festival or celebratory event.
-
B.
hasFestivalImportance
Indicates that something holds notable significance, relevance, or prominence within the context of a festival or festive event.
-
C.
hasFestivalFrequency
Indicates how often a festival or recurring celebratory event takes place within a given time period.
-
D.
hasFestivalDepicted
Indicates that a work or representation includes a depiction or portrayal of a festival.
-
E.
hasFestivalConnection
Indicates a relationship in which two entities are connected through a festival, such as by participation, organization, sponsorship, or association with that event.
- F. None of above.
Provenance (4 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_69f76ea6f5288190b8d9988f613811c0 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40362908ec819095a1568f312658b7 |
completed | June 27, 2026, 8:44 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:15 p.m.