Triple
T17885553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wise Son |
E447190
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Milestone Media character |
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: Milestone Media character Context triple: [Wise Son, instanceOf, Milestone Media character]
-
A.
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.
-
B.
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.
-
C.
television film character
A television film character is a fictional persona created for and portrayed within a made-for-television movie, contributing to its narrative, themes, and emotional impact.
-
D.
Big Hero 6 character
A Big Hero 6 character is an individual—human, robot, or otherwise—who inhabits the futuristic city of San Fransokyo and contributes to the story’s blend of superhero action, emotional growth, and technological innovation.
-
E.
character from Megamind
A character from Megamind is an individual, often exaggerated and comedic, who inhabits the film’s superhero-satire world and contributes to its narrative through distinct personality traits, visual design, and relationships with other characters.
- 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_69d8b9f59bd48190a6fc925a855b8bac |
completed | April 10, 2026, 8:51 a.m. |
Created at: April 10, 2026, 10:18 a.m.