Triple
T28886695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lal Darja |
E732582
|
entity |
| Predicate | workOfDirectorKnownFor |
P166250
|
FINISHED |
| Object | poetic realism |
—
|
LITERAL FINISHED |
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: poetic realism | Statement: [Lal Darja, workOfDirectorKnownFor, poetic realism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workOfDirectorKnownFor Context triple: [Lal Darja, workOfDirectorKnownFor, poetic realism]
-
A.
workOfDirector
Indicates that a creative work (such as a film, play, or show) is directed by a particular director.
-
B.
directorOfWorkFeaturingSubject
Indicates that the subject is the director of a creative work in which another specified entity appears or is featured.
-
C.
directorOfWorkHeAppearsIn
Indicates that a person serves as the director of a work (such as a film, show, or production) in which he himself appears.
-
D.
workedAsDirectorFor
Indicates that one entity held the role of director in relation to another entity, such as an organization, project, or production.
-
E.
filmDirectorWorkedWith
Indicates that a film director has collaborated professionally with another person on one or more film projects.
- 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_69f05b07bdec819080cadfe147aa1f25 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f66003a3f48190a2ba6da5aafbb5cb |
completed | May 2, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65f75ac608190a62cd6afce14f68e |
completed | May 2, 2026, 8:32 p.m. |
Created at: April 28, 2026, 7:51 a.m.