Triple
T30943547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BB-28 |
E788324
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | game character |
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: game character Context triple: [BB-28, instanceOf, game character]
-
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.
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.
-
C.
anime character
An anime character is a stylized, often exaggerated fictional persona originating from Japanese animation, defined by distinctive visual design, expressive emotions, and participation in narrative-driven stories.
-
D.
Nintendo character
A Nintendo character is a fictional persona created or licensed by Nintendo that appears in its video games, media, and related merchandise, often embodying distinctive abilities, personalities, and roles within their respective game worlds.
-
E.
animated character
An animated character is a fictional persona brought to life through drawn, computer-generated, or stop-motion imagery, exhibiting movement, expression, and personality within animated media.
- 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_69f224c180f88190ad177372ee02b7e2 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:53 p.m.