Triple
T30356647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | By a Waterfall |
E772160
|
entity |
| Predicate | directorOfParentWork |
P190675
|
FINISHED |
| Object | Lloyd Bacon |
—
|
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: Lloyd Bacon | Statement: [By a Waterfall, directorOfParentWork, Lloyd Bacon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directorOfParentWork Context triple: [By a Waterfall, directorOfParentWork, Lloyd Bacon]
-
A.
authorOfParentWork
Indicates that one entity is the author of a work that serves as the parent or source for another related work.
-
B.
hasDirectorOfWork
Indicates that an entity has a specific person or organization serving as the director responsible for overseeing its work or project.
-
C.
directorOfWorkAboutSubject
Indicates that a person is the director of a creative work whose content or focus is about a specified subject.
-
D.
directorFullName
Indicates that the predicate specifies the complete name of the person who serves as the director in the described relationship or context.
-
E.
authorOfWorkAppearingIn
Indicates that one entity is the creator or writer of a work that appears within another work or publication.
- 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fcce2cf9188190b3f65b362203a6a3 |
completed | May 7, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
| PDg | Predicate description generation | batch_69fccdd2d84481909a7ce22407def9c7 |
completed | May 7, 2026, 5:37 p.m. |
Created at: April 29, 2026, 7:57 p.m.