Triple
T37764479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mandleshwar |
E941375
|
entity |
| Predicate | hasReligiousFestivalType |
P38636
|
FINISHED |
| Object | Hindu festivals |
—
|
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: Hindu festivals | Statement: [Mandleshwar, hasReligiousFestivalType, Hindu festivals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligiousFestivalType Context triple: [Mandleshwar, hasReligiousFestivalType, Hindu festivals]
-
A.
hasPilgrimageOrFeast
Indicates that there is a religious pilgrimage or feast associated with, dedicated to, or occurring in relation to the referenced entity.
-
B.
hasFestivityType
Indicates that an event or celebration is classified as belonging to a particular type of festivity.
-
C.
religiousHolidayCelebrated
Indicates that a particular religious holiday is observed or celebrated by an entity.
-
D.
festivalObserved
chosen
Indicates that a particular festival is celebrated, observed, or commemorated by an entity (such as a person, group, or community).
-
E.
hasPublicHolidayOrFestival
Indicates that there exists a public holiday or festival associated with, occurring in, or relevant to the given entity.
- 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_69f76ee3251881909bb4451aad50752b |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:19 p.m.