Triple
T15628391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Never Let Me Go (screenplay) |
E375743
|
entity |
| Predicate | screenplayFormat |
P30807
|
FINISHED |
| Object | feature-length |
—
|
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: feature-length | Statement: [Never Let Me Go (screenplay), screenplayFormat, feature-length]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: screenplayFormat Context triple: [Never Let Me Go (screenplay), screenplayFormat, feature-length]
-
A.
screenplayType
chosen
Indicates the specific category or format of a screenplay associated with a work or production.
-
B.
screenplayRecord
Indicates that there exists a record or documentation associated with a particular screenplay, capturing information about its creation, version, or related details.
-
C.
screenplayForDirector
Indicates that a screenplay is written or created specifically for a particular director to direct.
-
D.
screenplayBy
Indicates that a film, television show, or similar work was written or scripted by a particular person or group.
-
E.
screenplayDevelopedBy
Indicates that a screenplay was created, written, or otherwise developed by a particular person or organization.
- 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_69d85cd035a48190b73d5579ab73969a |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04eb4301881908c7157227fdf79b6 |
completed | April 16, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69deda868d4481908f4bce1c64d2902a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:14 a.m.