Triple
T23641770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aaja Nachle (title track) |
E583917
|
entity |
| Predicate | featuresChoreographyFor |
P29261
|
FINISHED |
| Object | Madhuri Dixit |
—
|
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: Madhuri Dixit | Statement: [Aaja Nachle (title track), featuresChoreographyFor, Madhuri Dixit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresChoreographyFor Context triple: [Aaja Nachle (title track), featuresChoreographyFor, Madhuri Dixit]
-
A.
hasChoreographyBasedOn
Indicates that one choreography is derived from, inspired by, or structured according to another existing work or source.
-
B.
danceFeature
Indicates that one entity serves as a notable characteristic, element, or attribute of a dance or dancing-related activity.
-
C.
choreographedTo
Indicates that one action, movement, or sequence has been deliberately designed or arranged to align in timing, pattern, or structure with another.
-
D.
hasDanceChoreography
chosen
Indicates that an entity is associated with or characterized by a specific dance choreography.
-
E.
choreographyStyle
Indicates the specific style or form of choreography associated with a performance, routine, or choreographic work.
- 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_69e248fefafc81909656921192f30e80 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b28152108190972ac680cba986d7 |
completed | April 29, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:48 p.m.