Triple
T29614548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Why This Kolaveri Di |
E754824
|
entity |
| Predicate | directorOfPromoVideo |
P4911
|
FINISHED |
| Object | Aishwarya R. Dhanush |
—
|
NE NERFINISHED |
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: Aishwarya R. Dhanush | Statement: [Why This Kolaveri Di, directorOfPromoVideo, Aishwarya R. Dhanush]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directorOfPromoVideo Context triple: [Why This Kolaveri Di, directorOfPromoVideo, Aishwarya R. Dhanush]
-
A.
musicVideoProtagonist
Indicates that an entity serves as the main featured character or performer in a particular music video.
-
B.
musicVideoDirector
chosen
Indicates that one entity is the director responsible for creating or overseeing the production of the other entity, which is a music video.
-
C.
musicVideoCoDirector
Indicates a relationship where two or more individuals share responsibility for directing the same music video.
-
D.
promotionalRole
Indicates that an entity serves in a capacity focused on promoting, advertising, or publicizing another entity, product, or activity.
-
E.
videoIn
Indicates that one entity is a video that is contained within, embedded in, or associated as input to another 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_69f0ef85f62081909842b59fdf8717e1 |
completed | April 28, 2026, 5:33 p.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, 6:30 p.m.