Triple
T33499238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tezaab |
E857944
|
entity |
| Predicate | songChoreographer |
P11856
|
FINISHED |
| Object | Saroj Khan |
—
|
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: Saroj Khan | Statement: [Tezaab, songChoreographer, Saroj Khan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: songChoreographer Context triple: [Tezaab, songChoreographer, Saroj Khan]
-
A.
choreographer
chosen
Indicates that one entity is the person who designs and arranges the dance or movement sequences performed by another entity.
-
B.
choreographedTo
Indicates that one action, movement, or sequence has been deliberately designed or arranged to align in timing, pattern, or structure with another.
-
C.
musicVideoChoreographer
Indicates that the subject served as the choreographer responsible for creating or directing the dance or movement in the specified music video.
-
D.
hasDanceChoreography
Indicates that an entity is associated with or characterized by a specific dance choreography.
-
E.
choreographedIn
Indicates that an entity (typically a choreographer or group) created or arranged the choreography for a performance, work, or event in a specified context or production.
- 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_69f3497660508190a541826a81f7e9ab |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e56e373481909502b961265cd68d |
completed | May 3, 2026, 6:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3db74c081909a991309d835d477 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:38 a.m.