Triple
T35727858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Final Fantasy VII Remake |
E1032665
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | episodic game |
C14740
|
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: episodic game Context triple: [Final Fantasy VII Remake, instanceOf, episodic game]
-
A.
recurring game
A recurring game is a game or match that takes place repeatedly over time, often on a regular schedule or as part of an ongoing series or season.
-
B.
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.
-
C.
narrative-driven game
chosen
A narrative-driven game is an interactive experience where storytelling, character development, and plot progression are the primary focus, guiding gameplay and player choices.
-
D.
fragmentary play
A fragmentary play is a dramatic work composed of incomplete, disjointed, or non-linear scenes that rely on gaps, omissions, and abrupt transitions to convey meaning and emotional impact.
-
E.
event in a video game
An event in a video game is a discrete occurrence or trigger—often time-based, player-driven, or system-generated—that changes the game state, prompts responses, or advances gameplay or narrative.
- 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_69f76e102b5881909e5d63a30a5cecbe |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:05 p.m.