Triple
T33421352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cracker (TV series) |
E855852
|
entity |
| Predicate | revivalSpecialAired |
P176579
|
FINISHED |
| Object | 2006 |
—
|
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: 2006 | Statement: [Cracker (TV series), revivalSpecialAired, 2006]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revivalSpecialAired Context triple: [Cracker (TV series), revivalSpecialAired, 2006]
-
A.
revivalAiredOnChannel
Indicates that a revival of a show or series was broadcast on a specific television channel.
-
B.
revivalBroadcastIn
Indicates that a revival or rerun of a work is broadcast within a specified medium, channel, or platform.
-
C.
notableRevivalPremiereDate
Indicates the date on which a notable revival or re-staging of a work (such as a play, musical, or performance) was first premiered.
-
D.
revival
Indicates the act of bringing something back into use, popularity, or active existence after a period of decline, dormancy, or disuse.
-
E.
appearsInRevival
Indicates that an entity participates in, is featured in, or is otherwise present within a revival or revived version of another work, event, or production.
- 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_69f3496fdf0081908c1aa30870ce518b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e52a6d40819084472f6072c91e9f |
completed | May 3, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69f6e47c13348190a10528c84a401178 |
completed | May 3, 2026, 6 a.m. |
Created at: May 1, 2026, 1:36 a.m.