Triple
T28203148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Psychoville |
E716941
|
entity |
| Predicate | hasHalloweenSpecial |
P123672
|
FINISHED |
| Object | Psychoville Halloween Special |
—
|
NE NERFINISHED |
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: Psychoville Halloween Special | Statement: [Psychoville, hasHalloweenSpecial, Psychoville Halloween Special]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHalloweenSpecial Context triple: [Psychoville, hasHalloweenSpecial, Psychoville Halloween Special]
-
A.
isHolidaySpecialOf
chosen
Indicates that something is a special version, event, or offering specifically created for or associated with a particular holiday.
-
B.
hasSpecials
Indicates that an entity offers or is associated with special deals, promotions, or limited-time offers.
-
C.
hasStandUpSpecial
Indicates that an entity has created, performed, or released a stand-up comedy special.
-
D.
hasSpecial
Indicates that an entity possesses or is associated with a distinctive or exceptional attribute, status, or feature compared to others.
-
E.
hasTimeOfSpecialAttraction
Indicates a relationship where something is associated with a specific time period during which it has a heightened or special level of attraction.
- 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_69efd6b826908190857e6e7dad74ed93 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 27, 2026, 10:33 p.m.