Triple
T37204348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Plutonia Experiment |
E922126
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | first-person shooter campaign |
C30160
|
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: first-person shooter campaign Context triple: [The Plutonia Experiment, instanceOf, first-person shooter campaign]
-
A.
first-person shooter game
chosen
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.
-
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.
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.
-
D.
tactical shooter series
A tactical shooter series is a collection of games focused on realistic, team-based combat that emphasizes strategy, planning, and careful execution over fast-paced run-and-gun action.
-
E.
air assault campaign
An air assault campaign is a coordinated series of military operations that use rotary- and tilt-rotor aircraft to rapidly insert, support, and extract ground forces in contested or hostile areas to achieve specific tactical or operational objectives.
- 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_69f76ea4849481909b4a3073efb0114c |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:15 p.m.