Triple
T16635871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vicious Christmas special |
E404201
|
entity |
| Predicate | isHolidaySpecialOf |
P123672
|
FINISHED |
| Object | Vicious |
—
|
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: Vicious | Statement: [Vicious Christmas special, isHolidaySpecialOf, Vicious]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHolidaySpecialOf Context triple: [Vicious Christmas special, isHolidaySpecialOf, Vicious]
-
A.
includesSpecialDay
Indicates that a time period, schedule, or collection contains or encompasses at least one designated special day or occasion.
-
B.
holidayType
Indicates the specific category or kind of holiday associated with an event or date (e.g., public, religious, national, or personal).
-
C.
primaryHoliday
Indicates that one holiday is the main or most significant holiday associated with a given entity, time, or context.
-
D.
hasHolidayCustom
Indicates that there is a specific traditional practice or custom associated with a particular holiday.
-
E.
hasStandUpSpecial
Indicates that an entity has created, performed, or released a stand-up comedy special.
- 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_69d8838a41f08190b0c3f79c47df5078 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e378e999d48190bff680040dbc883d |
completed | April 18, 2026, 12:28 p.m. |
| PD | Predicate disambiguation | batch_69e296ad3f148190af09223dc35b155c |
completed | April 17, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69e2d7fb02f481908885a226c2191231 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:17 a.m.