Triple
T29395070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vandiyur Mariamman Temple |
E745471
|
entity |
| Predicate | primaryFestivalsSeason |
P29256
|
FINISHED |
| Object | summer months |
—
|
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: summer months | Statement: [Vandiyur Mariamman Temple, primaryFestivalsSeason, summer months]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryFestivalsSeason Context triple: [Vandiyur Mariamman Temple, primaryFestivalsSeason, summer months]
-
A.
festivalSeason
chosen
Indicates that a time period is designated or recognized as the season during which a particular festival or set of festivals takes place.
-
B.
famousSeasonalEvent
Indicates a recurring event that is widely recognized or celebrated during a particular season.
-
C.
hasSeasonalEvents
Indicates that an entity organizes or experiences events that occur only during specific seasons or times of the year.
-
D.
popularSeason
Indicates that a particular season is widely liked, favored, or frequently chosen by many people.
-
E.
seasonsFeatured
Indicates that certain seasons of a series or competition are highlighted, showcased, or given special prominence in relation to an 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_6a0123d1162c81908182d01ba3ddd236 |
completed | May 11, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_6a01236713d88190b12a567c0dfb2d49 |
completed | May 11, 2026, 12:31 a.m. |
Created at: April 28, 2026, 2:45 p.m.