Triple
T7674687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blockbusters |
E173831
|
entity |
| Predicate | spinOffOrRevival |
P9802
|
FINISHED |
| Object | Sky One revival |
—
|
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: Sky One revival | Statement: [Blockbusters, spinOffOrRevival, Sky One revival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spinOffOrRevival Context triple: [Blockbusters, spinOffOrRevival, Sky One revival]
-
A.
spinOff
Indicates that a new entity is created by separating or divesting part of an existing entity, forming an independent offshoot derived from the original.
-
B.
revivedBy
Indicates that an entity has been brought back to life, consciousness, or active state through the action or intervention of another entity.
-
C.
revival
chosen
Indicates the act of bringing something back into use, popularity, or active existence after a period of decline, dormancy, or disuse.
-
D.
revivedAs
Indicates that an entity, after having ceased to exist or function in its original form, comes back into existence or operation in a new or restored form.
-
E.
inspiredSpinOff
Indicates that one entity served as the creative or conceptual inspiration for another entity that was developed as a spin-off.
- 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_69c6995703e0819081de77361b602e78 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7048b0b448190889bd40e0a38e51a |
completed | March 27, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69c701618d3481908be84b76f36ac5a1 |
completed | March 27, 2026, 10:14 p.m. |
Created at: March 27, 2026, 4 p.m.