Triple
T16330288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Humphrey Bogart as Dixon Steele |
E396532
|
entity |
| Predicate | screenwritingTheme |
P44895
|
FINISHED |
| Object | creativeFrustration |
—
|
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: creativeFrustration | Statement: [Humphrey Bogart as Dixon Steele, screenwritingTheme, creativeFrustration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: screenwritingTheme Context triple: [Humphrey Bogart as Dixon Steele, screenwritingTheme, creativeFrustration]
-
A.
coScreenwriter
Indicates that two or more individuals collaborated in writing the screenplay for the same work.
-
B.
screenwritersContext
Indicates the contextual or collaborative relationship between screenwriters, such as shared projects, influences, or professional associations.
-
C.
screenplayFocus
chosen
Indicates that a screenplay primarily centers on, highlights, or is chiefly concerned with a particular subject, character, or theme.
-
D.
screenwriters
Indicates that one or more entities are the writers who authored the screenplay or script for a film, show, or similar work.
-
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_69d87f255b788190a400eba031dd85d8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2c4debef08190a64f13214bfa098f |
completed | April 17, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69e226eba9b48190af6e80d3d1c2aed3 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:07 a.m.