Triple
T29050927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Korg |
E735259
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Thor supporting character |
C54579
|
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: Thor supporting character Context triple: [Korg, instanceOf, Thor supporting character]
-
A.
superhero sidekick
chosen
A superhero sidekick is a usually younger or less-experienced partner who supports a primary superhero in their crime-fighting efforts, often providing complementary skills, emotional grounding, and narrative contrast.
-
B.
Avatar franchise character
An Avatar franchise character is an individual, creature, or spirit from the Avatar universe whose identity, abilities, and relationships are shaped by the world’s elemental bending, cultures, and ongoing conflicts.
-
C.
Tron character
A Tron character is a stylized, neon-lit digital persona existing within a computer-generated world, embodying programs, users, or security forces that interact through high-tech combat and light-based vehicles.
-
D.
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.
-
E.
stock character
A stock character is a stereotypical fictional persona, easily recognized by audiences, that embodies a set of familiar traits, behaviors, and roles used repeatedly across stories and genres.
- 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_69f077e64b88819094d37bdbca8191b3 |
completed | April 28, 2026, 9:03 a.m. |
Created at: April 28, 2026, 10:08 a.m.