Triple
T1271182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Hitchhiker's Guide to the Galaxy (computer game) |
E15712
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | interactive fiction video game |
C6698
|
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: interactive fiction video game Context triple: [The Hitchhiker's Guide to the Galaxy (computer game), instanceOf, interactive fiction video game]
-
A.
role‑playing game
A role-playing game is an interactive experience in which players assume fictional characters and collaboratively create or influence a narrative by making choices that affect the game world and its outcomes.
-
B.
interactive ride
An interactive ride is an amusement attraction where riders actively participate—through controls, choices, or physical actions—to influence the experience, outcome, or narrative of the ride.
-
C.
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.
-
D.
interpreter
An interpreter is a program or component that directly executes instructions written in a programming or scripting language by reading and performing them line by line without first compiling them into machine code.
-
E.
dynamic game
A dynamic game is a strategic interaction among multiple decision-makers that unfolds over time, where players’ choices at each stage can depend on past actions and information, influencing future payoffs and outcomes.
- 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_69a4935a94308190bb92555b79032824 |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:50 p.m.