Triple
T17685721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viras |
E440882
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Gamera character |
C38475
|
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: Gamera character Context triple: [Viras, instanceOf, Gamera character]
-
A.
kaiju-related character
chosen
A kaiju-related character is an individual, creature, or entity whose identity, role, or narrative significance is directly tied to giant monsters—whether as a kaiju themselves, an ally or enemy of kaiju, or a person deeply involved in kaiju-related events, organizations, or technologies.
-
B.
Toho character
A Toho character is a fictional entity originating from Toho-produced media, such as kaiju films or related works, defined by its unique traits, abilities, and narrative role within the Toho universe.
-
C.
MonsterVerse creature
A MonsterVerse creature is a colossal, often ancient and otherworldly titan whose existence shapes global ecosystems, myths, and human history through its immense power and presence.
-
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.
giant humanoid mecha
A giant humanoid mecha is a towering, human-shaped robotic vehicle typically piloted by one or more operators, designed for large-scale combat, defense, or heavy-duty tasks.
- 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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
Created at: April 10, 2026, 10:02 a.m.