Triple
T30345290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ALfheim Online |
E771853
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional video game |
C56762
|
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: fictional video game Context triple: [ALfheim Online, instanceOf, fictional video game]
-
A.
video game
A video game is an interactive digital entertainment experience in which players engage with visual and audio content through input devices to achieve goals, overcome challenges, or explore virtual worlds.
-
B.
video game fictional entity
A video game fictional entity is any imagined character, creature, object, or construct that exists within the narrative or interactive world of a video game, defined by its designed attributes, behaviors, and role in gameplay or story.
-
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.
fictional computer
A fictional computer is an imagined computing device, often with advanced or impossible capabilities, that exists only within stories, games, or speculative scenarios.
-
E.
science fiction game
A science fiction game is an interactive experience set in speculative futures or alternate realities that explores advanced technology, space travel, alien life, or other sci-fi concepts through gameplay, narrative, and world-building.
- F. None of above. chosen
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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:55 p.m.