Triple
T36409330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haddonfield, Illinois |
E896833
|
entity |
| Predicate | hasFictionalHolidayEvent |
P87547
|
FINISHED |
| Object | Halloween night murders |
—
|
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: Halloween night murders | Statement: [Haddonfield, Illinois, hasFictionalHolidayEvent, Halloween night murders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalHolidayEvent Context triple: [Haddonfield, Illinois, hasFictionalHolidayEvent, Halloween night murders]
-
A.
hasFictionalEventType
chosen
Indicates that something is associated with, characterized by, or classified under a particular type or category of fictional event.
-
B.
fictionalHolidayCreator
Indicates that an entity is the originator or inventor of a fictional or imaginary holiday.
-
C.
fictionalEventMarked
Indicates that an event is identified or designated as fictional rather than real.
-
D.
hasFeastOrCommemoration
Indicates that a particular day, event, or context includes an associated religious feast, liturgical celebration, or commemorative observance.
-
E.
isCelebrated
Indicates that a person, event, or occasion is honored, commemorated, or festively observed by others.
- 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_69f76e54ce408190849acc3f7758937c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a00144238708190acbec3f791cc873e |
completed | May 10, 2026, 5:14 a.m. |
| PD | Predicate disambiguation | batch_6a00120244a4819090ef39070aba9d99 |
completed | May 10, 2026, 5:05 a.m. |
Created at: May 3, 2026, 4:10 p.m.