Triple
T33409842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SOCOM U.S. Navy SEALs |
E855548
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | third-person shooter game series |
C29430
|
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: third-person shooter game series Context triple: [SOCOM U.S. Navy SEALs, instanceOf, third-person shooter game series]
-
A.
third-person shooter series
chosen
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.
-
B.
third-person shooter video game
A third-person shooter video game is an action game where players control a character visible on-screen from a camera positioned behind or around them, focusing on ranged combat with firearms or similar weapons.
-
C.
first-person shooter game
A first-person shooter game is a video game genre where players experience the action through the eyes of the protagonist, primarily engaging in combat using ranged weapons in real-time, often within immersive 3D environments.
-
D.
run and gun game series
A run and gun game series is a collection of fast-paced action games focused on continuous forward movement and shooting, often featuring challenging levels, numerous enemies, and arcade-style gameplay.
-
E.
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.
- 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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:36 a.m.