Triple
T33421351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cracker (TV series) |
E855852
|
entity |
| Predicate | hasRevivalSpecial |
P176579
|
FINISHED |
| Object | Cracker (2006 special) |
E855852
|
NE 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: Cracker (2006 special) | Statement: [Cracker (TV series), hasRevivalSpecial, Cracker (2006 special)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRevivalSpecial Context triple: [Cracker (TV series), hasRevivalSpecial, Cracker (2006 special)]
-
A.
hasRevivalsIn
Indicates that something has been brought back, renewed, or reintroduced in specific times, places, or contexts.
-
B.
revivalSpecialAired
chosen
Indicates that a special episode associated with a revival of a series or show has been broadcast.
-
C.
hasRevivalProgram
Indicates that an entity has an associated program or initiative aimed at restoring, renewing, or revitalizing something (such as a practice, resource, or condition).
-
D.
hasRevivalVarieties
Indicates that an entity has associated revival or renewed versions/varieties of itself.
-
E.
revivedAfter
Indicates that one entity comes back to life or is restored to a living or active state after a period of being dead, inactive, or nonfunctional, following another event or time point.
- F. None of above.
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_69f3496fdf0081908c1aa30870ce518b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a357705178881908d6dbc113d86be79 |
completed | June 19, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:36 a.m.