Triple
T38495915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serious Sam: The Second Encounter |
E919691
|
entity |
| Predicate | hasRemakeOrHDVersion |
P21944
|
FINISHED |
| Object | Serious Sam HD: The Second Encounter |
E919691
|
NE 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: Serious Sam HD: The Second Encounter | Statement: [Serious Sam: The Second Encounter, hasRemakeOrHDVersion, Serious Sam HD: The Second Encounter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRemakeOrHDVersion Context triple: [Serious Sam: The Second Encounter, hasRemakeOrHDVersion, Serious Sam HD: The Second Encounter]
-
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.
hasRemakePlannedIn
Indicates that an existing work is planned to be remade in a specified time period or context.
-
E.
hasFilmVersionStatus
Indicates whether and how a work has been adapted into a film, specifying the status of that film version.
- F. None of above.
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_69f76e9ddd4481908f8c04439d848f9d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a45f963259c8190978fecff7351ea59 |
completed | July 2, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:31 p.m.