Triple
T23604230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ek Do Teen |
E582846
|
entity |
| Predicate | featuresOnScreenPerformer |
P152890
|
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: [Ek Do Teen, featuresOnScreenPerformer, Madhuri Dixit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresOnScreenPerformer Context triple: [Ek Do Teen, featuresOnScreenPerformer, Madhuri Dixit]
-
A.
featuresPerformerCameo
Indicates that the subject includes a brief, special appearance by a performer who is not part of the main cast or lineup.
-
B.
performedOnScreenBy
Indicates that an action, role, or performance is carried out by one entity in an on-screen context involving another entity.
-
C.
featuresSoloPerformancesBy
Indicates that the subject includes or showcases solo performances carried out by the specified performer or performers.
-
D.
featuresPerformerAsSelfTypeRole
Indicates that a work includes a performer appearing as themselves in a specific type of role.
-
E.
featuresPerformerType
Indicates that something includes or highlights a performer of a specified type (e.g., musician, actor, or other performance role).
- F. None of above. chosen
Provenance (4 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_69e248faa2788190abb1581742daa6aa |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b0ee6ce881909f556404cc235418 |
completed | April 29, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69f118c96a0081908a8ac98ef7e7e60c |
completed | April 28, 2026, 8:30 p.m. |
| PDg | Predicate description generation | batch_69f121cc494081908c987adfcde89b0e |
completed | April 28, 2026, 9:08 p.m. |
Created at: April 17, 2026, 6:44 p.m.