Triple
T36937388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kino der Toten |
E913654
|
entity |
| Predicate | remasterEngine |
P141161
|
FINISHED |
| Object | Black Ops III engine |
—
|
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: Black Ops III engine | Statement: [Kino der Toten, remasterEngine, Black Ops III engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: remasterEngine Context triple: [Kino der Toten, remasterEngine, Black Ops III engine]
-
A.
remastersGame
Indicates that one entity creates a new, updated version of an existing game, typically improving its graphics, audio, or performance while preserving the original gameplay.
-
B.
remasterPublisher
Indicates that an entity serves as the publisher responsible for releasing a remastered version of another entity (such as a work, product, or recording).
-
C.
reEnginedWith
chosen
Indicates that an existing vehicle, machine, or system has had its original engine replaced with a different specified engine.
-
D.
remasteredBy
Indicates that an existing work has been reprocessed or enhanced by a particular agent to improve or update its quality.
-
E.
hasRemastering
Indicates that one version of a work is a remastered form derived from another version of the same work.
- 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_69f76e8a6a5c81909c1febf32bf3fe23 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:13 p.m.