Triple
T37468972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amplitude |
E931103
|
entity |
| Predicate | hasRemakeOrReboot |
—
|
GENERATED |
| Object | Amplitude (2016 video game) |
—
|
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: hasRemakeOrReboot Context triple: [Amplitude, hasRemakeOrReboot, Amplitude (2016 video game)]
-
A.
hasRemake
chosen
Indicates that one work is a new version or recreation of an earlier existing work.
-
B.
hasRemakeBy
Indicates that an original work has been remade or re-created by a specified agent (such as a person, studio, or organization).
-
C.
hasRemakeOrRetroVersion
Indicates that one work has been remade or re-released in a retro-style version of the original.
-
D.
remakeAppearsIn
Indicates that a remake of a work is featured, shown, or included within a particular context, such as a collection, series, or medium.
-
E.
hasRemakePlannedIn
Indicates that an existing work is planned to be remade in a specified time period or context.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.