Triple
T7950572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halloween H20: 20 Years Later |
E184602
|
entity |
| Predicate | setYearsAfter |
P76474
|
FINISHED |
| Object | 20 years after 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: 20 years after the events of Halloween (1978) | Statement: [Halloween H20: 20 Years Later, setYearsAfter, 20 years after the events of Halloween (1978)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setYearsAfter Context triple: [Halloween H20: 20 Years Later, setYearsAfter, 20 years after the events of Halloween (1978)]
-
A.
settingStartYear
Indicates the year in which a particular setting, configuration, or condition first becomes effective or begins to apply.
-
B.
timeSettingEndYear
Indicates the year in which a specified time setting, period, or temporal condition comes to an end.
-
C.
endYear
Indicates the year in which an event, state, or relationship comes to an end.
-
D.
effectiveYear
Indicates the calendar year in which something (such as a rule, status, or agreement) becomes valid or takes effect.
-
E.
yearPassed
chosen
Indicates that a specified number of calendar years has elapsed between two time points or events.
- 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_69ca8292cba881908a64427b938dac47 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b5b7450819091e4e6f21e9d832d |
completed | March 31, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69cae9361bc48190886b7681e563d46b |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:10 p.m.