Triple
T33853294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keith Gordon as Peter Miller |
E867692
|
entity |
| Predicate | workHasScreenwriter |
P121013
|
FINISHED |
| Object | Brian De Palma |
—
|
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: Brian De Palma | Statement: [Keith Gordon as Peter Miller, workHasScreenwriter, Brian De Palma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workHasScreenwriter Context triple: [Keith Gordon as Peter Miller, workHasScreenwriter, Brian De Palma]
-
A.
hasScreenwriter
Indicates that a creative work is associated with the person or entity who wrote its screenplay or script.
-
B.
workScreenwritersInclude
Indicates that a creative work’s credited screenwriters include the specified person or persons.
-
C.
hasScreenwriterCreator
Indicates that an entity has another entity serving as the screenwriter who created or originated its screenplay.
-
D.
screenwriterOfWorkAppearingIn
chosen
Indicates that a person is the screenwriter of a work in which a specified entity (such as a character, actor, or role) appears.
-
E.
screenwriterOfWork
Indicates that a person served as the screenwriter (wrote the screenplay) for a particular creative 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_69f349937b648190a34ada70f6a2b534 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:47 a.m.