Triple
T15732038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clone High |
E381367
|
entity |
| Predicate | rebootInstanceOf |
P22728
|
FINISHED |
| Object | revival series |
—
|
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: revival series | Statement: [Clone High, rebootInstanceOf, revival series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rebootInstanceOf Context triple: [Clone High, rebootInstanceOf, revival series]
-
A.
rebootOf
chosen
Indicates that one work is a new version that restarts or reimagines the story, continuity, or franchise of another earlier work.
-
B.
rebootHost
Indicates that a host machine is restarted, typically involving shutting it down and bringing it back up to restore normal operation.
-
C.
rebootOwner
Indicates that one entity is responsible for initiating or controlling the reboot of another entity.
-
D.
rebootPlatform
Indicates restarting a computing platform or system, typically causing all running processes and services on it to stop and then start again.
-
E.
rebootAnnounced
Indicates that an official announcement has been made that a system, service, or process will be rebooted.
- 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_69d86d9cdb648190bf3171be0bd7d872 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04fd3614481908b2694b1d3550058 |
completed | April 16, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69e00526759c819088b80d85138b8974 |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:46 a.m.