Triple
T21419043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halloween 4: The Return of Michael Myers |
E528381
|
entity |
| Predicate | screenplayWrittenIn |
P143894
|
FINISHED |
| Object | 11 days |
—
|
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: 11 days | Statement: [Halloween 4: The Return of Michael Myers, screenplayWrittenIn, 11 days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: screenplayWrittenIn Context triple: [Halloween 4: The Return of Michael Myers, screenplayWrittenIn, 11 days]
-
A.
screenplayWrittenFor
Indicates that a screenplay was written specifically for a particular film, show, or production.
-
B.
screenplayBy
Indicates that a film, television show, or similar work was written or scripted by a particular person or group.
-
C.
screenplayDevelopedBy
Indicates that a screenplay was created, written, or otherwise developed by a particular person or organization.
-
D.
screenplayCoWrittenWith
Indicates that two or more individuals collaborated to write the same screenplay.
-
E.
screenwriterOfWork
Indicates that a person served as the screenwriter (wrote the screenplay) for a particular creative work.
- 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_69e0c454c248819093425d1099101c09 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b2ccddc08190b4f66fa6ccda41e2 |
completed | April 22, 2026, 11:36 a.m. |
| PD | Predicate disambiguation | batch_69e61633f8208190a2a849457c4e4198 |
completed | April 20, 2026, 12:04 p.m. |
| PDg | Predicate description generation | batch_69e6190163448190a2404b396215c686 |
completed | April 20, 2026, 12:16 p.m. |
Created at: April 16, 2026, 5:47 p.m.