Triple
T25654067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R. D. Bansal and Company |
E643181
|
entity |
| Predicate | distributedFilmByDirector |
P160266
|
FINISHED |
| Object | Satyajit Ray |
—
|
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: Satyajit Ray | Statement: [R. D. Bansal and Company, distributedFilmByDirector, Satyajit Ray]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distributedFilmByDirector Context triple: [R. D. Bansal and Company, distributedFilmByDirector, Satyajit Ray]
-
A.
backedFilmByDirector
Indicates that a director provided support, endorsement, or resources for the production of a particular film.
-
B.
workOfDirector
Indicates that a creative work (such as a film, play, or show) is directed by a particular director.
-
C.
filmDirectorOfAssociatedWork
Indicates that a person serves as the director of the specified creative work (such as a film or related audiovisual production).
-
D.
isDirectedBy
Indicates that one entity serves as the director or guiding authority responsible for the creation, management, or execution of another entity (such as a film, project, or organization).
-
E.
directorsOfFilm
Indicates the person or people who directed a given film.
- 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_69e77e7d8a848190a98d0162325fd780 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f601f106a08190ad7b4537223dbd8c |
completed | May 2, 2026, 1:53 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fba5248190945acf1561280799 |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f600be0de88190989611e952b03117 |
completed | May 2, 2026, 1:48 p.m. |
Created at: April 21, 2026, 6:31 p.m.