Triple
T30096759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Severed Head |
E764886
|
entity |
| Predicate | screenwriterForFilmAdaptation |
P48034
|
FINISHED |
| Object | Iris Murdoch |
—
|
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: Iris Murdoch | Statement: [A Severed Head, screenwriterForFilmAdaptation, Iris Murdoch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: screenwriterForFilmAdaptation Context triple: [A Severed Head, screenwriterForFilmAdaptation, Iris Murdoch]
-
A.
screenwriters
chosen
Indicates that one or more entities are the writers who authored the screenplay or script for a film, show, or similar work.
-
B.
screenwriterForStudio
Indicates that a person serves as a screenwriter employed by or writing for a particular studio.
-
C.
screenwriterInstanceOf
Indicates that a screenwriter belongs to or is classified as a specific type, category, or class of entity.
-
D.
screenwriterInvolved
Indicates that a screenwriter participated in the creation or development of a particular work or project.
-
E.
screenwriterOfWorkAppearingIn
Indicates that a person is the screenwriter of a work in which a specified entity (such as a character, actor, or role) appears.
- 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_69f22474e4288190b5f895fe3974aa92 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6a0ea04888190ac3a813b603bcb5c |
completed | May 3, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 7:07 p.m.