Triple
T37179179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resident Evil 7: Biohazard |
E921145
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Resident Evil game |
C43688
|
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: Resident Evil game Context triple: [Resident Evil 7: Biohazard, instanceOf, Resident Evil game]
-
A.
Resident Evil character
A Resident Evil character is an individual within the franchise’s universe who navigates bioterror outbreaks, confronts mutated creatures, and advances the overarching narrative of survival horror.
-
B.
survival horror franchise
A survival horror franchise is a series of related games, films, or media that focus on vulnerable protagonists facing terrifying threats with limited resources, emphasizing tension, fear, and strategic survival over direct combat.
-
C.
location in Resident Evil franchise
A "location in the Resident Evil franchise" represents any distinct place or environment—such as cities, buildings, facilities, or outdoor areas—where narrative events, exploration, and encounters with enemies occur within the Resident Evil universe.
-
D.
Half-Life series game
A Half-Life series game is a first-person action-adventure video game set in a science fiction universe that combines narrative-driven exploration, environmental puzzles, and combat against both alien and human enemies.
-
E.
Capcom game
chosen
A Capcom game is a video game developed or published by Capcom, typically characterized by action-oriented gameplay, distinctive characters, and often belonging to franchises like Street Fighter, Resident Evil, or Monster Hunter.
- 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_69f76ea250bc819083f28d81de25cd0c |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:15 p.m.