Triple
T29211754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Margazhi |
E740562
|
entity |
| Predicate | linkedFestivalSeason |
P123104
|
FINISHED |
| Object | music and dance season in Chennai |
—
|
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: music and dance season in Chennai | Statement: [Margazhi, linkedFestivalSeason, music and dance season in Chennai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedFestivalSeason Context triple: [Margazhi, linkedFestivalSeason, music and dance season in Chennai]
-
A.
linkedFestival
Indicates that two entities are associated through a common festival, event, or celebration.
-
B.
linksFestivalTo
chosen
Indicates that one entity is associated with, connected to, or participates in a particular festival.
-
C.
linkedFestivalStatus
Indicates that one entity’s festival status is directly connected to or dependent on another entity’s festival status.
-
D.
relatedFestivalType
Indicates that one festival is associated with another through a shared or corresponding festival type or category.
-
E.
relatedFestivalDate
Indicates that there is a specific calendar date associated with a particular festival or celebration.
- 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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: April 28, 2026, 12:11 p.m.