Triple
T4423052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Withnail & I |
E95145
|
entity |
| Predicate | screenplayOrigin |
P30807
|
FINISHED |
| Object | original screenplay |
—
|
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: original screenplay | Statement: [Withnail & I, screenplayOrigin, original screenplay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: screenplayOrigin Context triple: [Withnail & I, screenplayOrigin, original screenplay]
-
A.
screenplayDevelopedFrom
Indicates that a screenplay was created or adapted based on a prior work, such as a story, script, or other source material.
-
B.
scriptOfOrigin
Indicates that one entity is the original writing system or script from which another script is derived or historically originates.
-
C.
screenplayRecord
Indicates that there exists a record or documentation associated with a particular screenplay, capturing information about its creation, version, or related details.
-
D.
screenplayType
chosen
Indicates the specific category or format of a screenplay associated with a work or production.
-
E.
screenplayBy
Indicates that a film, television show, or similar work was written or scripted by a particular person or group.
- 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_69b3453a36908190b95a79a297ca083c |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3554b36a48190a475ac5474bed132 |
completed | March 13, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69b34f5eabe88190a12b244ea71e46d6 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:30 p.m.