Triple
T15600331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halloween II |
E375012
|
entity |
| Predicate | storyTime |
P119399
|
FINISHED |
| Object | same night as the events of Halloween (1978) |
—
|
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: same night as the events of Halloween (1978) | Statement: [Halloween II, storyTime, same night as the events of Halloween (1978)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storyTime Context triple: [Halloween II, storyTime, same night as the events of Halloween (1978)]
-
A.
storyBy
Indicates that one entity is the creator or author of the story associated with another entity.
-
B.
storyFunction
Indicates that one entity serves a particular narrative role or function within the story structure of another entity.
-
C.
storyTitle
Indicates that one entity is the title assigned to a story associated with another entity.
-
D.
storyWorld
Indicates the fictional universe or narrative setting within which a story, event, or character exists or takes place.
-
E.
storyElement
Indicates that one entity functions as a narrative component or part within the structure of another entity’s story.
- 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_69d85cce25008190b13b52745fbd719b |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e621fc4819097e8e85e7ddfdc6c |
completed | April 16, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69deda844af081909e658ebc9d9b403d |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f05f708190850f1d8782e132b0 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:12 a.m.