Triple
T20372375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apeman Hop |
E497096
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | character in the Animal Boy universe |
C4314
|
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 the Animal Boy universe Context triple: [Apeman Hop, instanceOf, character in the Animal Boy universe]
-
A.
comic book character
chosen
A comic book character is a fictional persona, often possessing distinctive abilities, traits, or backstory, that appears in sequential art narratives and drives the plot through their actions and development.
-
B.
MonsterVerse character
A MonsterVerse character is a fictional being—often a giant monster, titan, or associated human figure—originating from the shared cinematic universe that includes Godzilla, Kong, and related creatures, defined by its role within that interconnected storyline.
-
C.
Arrowverse character
An Arrowverse character is a fictional individual who exists within the shared television universe based on DC Comics properties, appearing in one or more interconnected Arrowverse series and contributing to its overarching narrative.
-
D.
Steven Universe character
A Steven Universe character is an individual—human, Gem, or fusion—within the Steven Universe universe, defined by their unique gem-based abilities, personality, relationships, and role in the overarching narrative.
-
E.
Dakotaverse character
A Dakotaverse character is an individual—often a superpowered hero, villain, or supporting figure—who exists within the shared Milestone Media/DC Comics Dakotaverse continuity, shaped by its distinct urban, social, and cultural themes.
- 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_69e0b4a4f9b081908a5a021919c21ccb |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:26 a.m.