Triple
T18440449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Numbuh 4 |
E450512
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of Kids Next Door |
C40038
|
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: member of Kids Next Door Context triple: [Numbuh 4, instanceOf, member of Kids Next Door]
-
A.
Codename: Kids Next Door character
chosen
A "Codename: Kids Next Door character" is an individual, often a child operative or antagonist, within the animated series' universe who participates in or opposes the Kids Next Door organization, each defined by a unique codename, personality, and role in the show's missions and storylines.
-
B.
Despicable Me character
A Despicable Me character is a whimsical, often exaggerated individual from the Despicable Me universe whose personality, appearance, and actions contribute to the franchise’s blend of comedy, heart, and mischief.
-
C.
Minion
A Minion is a small, subordinate creature or character that serves a more powerful entity, often performing simple, repetitive, or menial tasks, sometimes with comedic or blindly loyal behavior.
-
D.
Smurf
A Smurf is a small, blue, humanoid creature living in a communal forest village, characterized by distinct personalities, white clothing, and a strong sense of cooperation and adventure.
-
E.
character from The Powerpuff Girls
A character from The Powerpuff Girls is an individual—human, creature, or entity—who inhabits the show's vibrant, often chaotic world of Townsville and interacts with the superpowered trio through alliances, conflicts, or everyday life.
- 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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:30 a.m.