Triple
T26342591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harihar Ray |
E662685
|
entity |
| Predicate | relatedWorkDirector |
P107822
|
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: [Harihar Ray, relatedWorkDirector, Satyajit Ray]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedWorkDirector Context triple: [Harihar Ray, relatedWorkDirector, Satyajit Ray]
-
A.
hasDirectorOfWork
Indicates that an entity has a specific person or organization serving as the director responsible for overseeing its work or project.
-
B.
workOfDirector
chosen
Indicates that a creative work (such as a film, play, or show) is directed by a particular director.
-
C.
workOfDirectorKnownFor
Indicates that a work (such as a film or show) is directed by a person for whom this work is one of their notable or best-known creations.
-
D.
associatedWithDirectors
Indicates a direct relationship or connection between an entity and one or more film or project directors.
-
E.
appearsInWorkDirector
Indicates that an entity appears in a creative work in which the associated director is responsible for directing that 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_69ee81304194819092e20e0fae3aee07 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69fe38be079c8190a240191ac0e73e3a |
completed | May 8, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69fe350344508190930de2218156ca02 |
completed | May 8, 2026, 7:09 p.m. |
Created at: April 26, 2026, 10:40 p.m.