Triple
T20573479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hitman (selected titles) |
E505156
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | stealth video game series |
C29442
|
CONCEPT FINISHED |
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: stealth video game series Context triple: [Hitman (selected titles), instanceOf, stealth video game series]
-
A.
stealth video game franchise
chosen
A stealth video game franchise is a series of games centered on avoiding detection through careful movement, strategy, and use of the environment to complete objectives covertly.
-
B.
third-person shooter series
A third-person shooter series is a collection of related video games in which players control a character viewed from a perspective outside and behind the avatar, focusing on ranged combat and action-oriented gameplay across multiple installments.
-
C.
science fiction video game series
A science fiction video game series is a collection of related games set in futuristic or speculative worlds that explore advanced technology, space travel, alien life, or other science-based imaginative concepts through interactive storytelling and gameplay.
-
D.
action-adventure game series
An action-adventure game series is a collection of related video games that blend real-time combat, exploration, and puzzle-solving within a continuous narrative universe or recurring thematic framework.
-
E.
puzzle video game series
A puzzle video game series is a collection of related games that challenge players to solve logic, pattern, or spatial problems through progressively complex and often thematically connected gameplay.
- 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_69e0b4b721588190993ac7b0a9be2736 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:39 a.m.