Triple
T33421351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cracker (TV series) |
E855852
|
entity |
| Predicate | hasRevivalSpecial |
—
|
GENERATED |
| Object | Cracker (2006 special) |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
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 (1 batch)
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. |
Created at: May 1, 2026, 1:36 a.m.