Triple
T33518663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Rainmaker (1956 film) |
E858439
|
entity |
| Predicate | screenplayBasedOnWorkBy |
P44894
|
FINISHED |
| Object | N. Richard Nash |
—
|
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: N. Richard Nash | Statement: [The Rainmaker (1956 film), screenplayBasedOnWorkBy, N. Richard Nash]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: screenplayBasedOnWorkBy Context triple: [The Rainmaker (1956 film), screenplayBasedOnWorkBy, N. Richard Nash]
-
A.
screenplayDevelopedFrom
chosen
Indicates that a screenplay was created or adapted based on a prior work, such as a story, script, or other source material.
-
B.
screenplayWrittenFor
Indicates that a screenplay was written specifically for a particular film, show, or production.
-
C.
screenplayBy
Indicates that a film, television show, or similar work was written or scripted by a particular person or group.
-
D.
screenwriterOfWork
Indicates that a person served as the screenwriter (wrote the screenplay) for a particular creative work.
-
E.
screenwriterOfWorkAppearsIn
Indicates that a person is the screenwriter of a work in which they themselves also appear.
- 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_69f349781c6c819082c516b260efe7e2 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: May 1, 2026, 1:39 a.m.