Triple
T37012804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jessamine Kaldwin |
E915993
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | character in a video game |
C4830
|
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: character in a video game Context triple: [Jessamine Kaldwin, instanceOf, character in a video game]
-
A.
video game character
chosen
A video game character is a fictional, interactive entity within a game world that the player controls or encounters, defined by its abilities, appearance, behavior, and role in the game's narrative or mechanics.
-
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.
board game character
A board game character is a distinct, often themed persona or token within a board game that represents a player’s role, abilities, and progression in the game’s world and mechanics.
-
D.
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.
-
E.
setting in a video game franchise
The setting in a video game franchise is the recurring fictional world or environment, including its locations, time period, and contextual lore, in which the games’ stories and gameplay take place.
- 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_69f76e90ed548190b187d2475f5c807d |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:14 p.m.