Triple
T30608249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Worzel Gummidge |
E779103
|
entity |
| Predicate | rebootStars |
P169610
|
FINISHED |
| Object | Mackenzie Crook |
—
|
NE NERFINISHED |
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: Mackenzie Crook | Statement: [Worzel Gummidge, rebootStars, Mackenzie Crook]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rebootStars Context triple: [Worzel Gummidge, rebootStars, Mackenzie Crook]
-
A.
rebootOf
Indicates that one work is a new version that restarts or reimagines the story, continuity, or franchise of another earlier work.
-
B.
rebootSeason
Indicates that a media series has been restarted or reimagined in a new season, typically resetting or significantly altering its prior continuity.
-
C.
rebootAired
Indicates that a rebooted version of a show, series, or franchise has been broadcast or released.
-
D.
rebootAnnounced
Indicates that an official announcement has been made that a system, service, or process will be rebooted.
-
E.
rebootPlatform
Indicates restarting a computing platform or system, typically causing all running processes and services on it to stop and then start again.
- 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_69f224a21fc08190abd9d8dd9eb6bb4c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f689b7bc6c8190b46762f5c16df91a |
completed | May 2, 2026, 11:33 p.m. |
| PD | Predicate disambiguation | batch_69f67e448a9c8190b591374d98799fe3 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f67f0353c88190a05b2db449abe0f4 |
completed | May 2, 2026, 10:47 p.m. |
Created at: April 29, 2026, 8:26 p.m.