Triple
T26096653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vicki Baum |
E658286
|
entity |
| Predicate | wroteScreenplaysFor |
P159937
|
FINISHED |
| Object | Hollywood studios |
—
|
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: Hollywood studios | Statement: [Vicki Baum, wroteScreenplaysFor, Hollywood studios]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wroteScreenplaysFor Context triple: [Vicki Baum, wroteScreenplaysFor, Hollywood studios]
-
A.
screenplayWrittenFor
Indicates that a screenplay was written specifically for a particular film, show, or production.
-
B.
screenwriterOfWork
Indicates that a person served as the screenwriter (wrote the screenplay) for a particular creative work.
-
C.
screenwriterOfWorkAppearingIn
Indicates that a person is the screenwriter of a work in which a specified entity (such as a character, actor, or role) appears.
-
D.
screenwriterOfWorkAppearsIn
Indicates that a person is the screenwriter of a work in which they themselves also appear.
-
E.
screenwriterOfWorkFeaturing
Indicates that one entity is the screenwriter responsible for creating the screenplay for a work in which the other entity appears or is featured.
- 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_69ee5bbfc4d08190a1b206d0ac3a1e8d |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6073720748190aecfc9af3ba039fd |
completed | May 2, 2026, 2:16 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 26, 2026, 7:51 p.m.