Triple
T33296731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mick Travis (O Lucky Man!) |
E852467
|
entity |
| Predicate | screenwriterOfWorkContext |
P25235
|
FINISHED |
| Object | David Sherwin |
—
|
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: David Sherwin | Statement: [Mick Travis (O Lucky Man!), screenwriterOfWorkContext, David Sherwin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: screenwriterOfWorkContext Context triple: [Mick Travis (O Lucky Man!), screenwriterOfWorkContext, David Sherwin]
-
A.
screenwritersContext
Indicates the contextual or collaborative relationship between screenwriters, such as shared projects, influences, or professional associations.
-
B.
screenwriterOfWork
chosen
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.
screenwriterOfWorkCreator
Indicates that one entity is the screenwriter who created or wrote the screenplay for a particular 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_69f34966ed4c81908dc9dda82d8c7fe3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: May 1, 2026, 1:33 a.m.