Triple
T17363599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cosmos (Godzilla) |
E422131
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Godzilla franchise character |
C14771
|
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: Godzilla franchise character Context triple: [Cosmos (Godzilla), instanceOf, Godzilla franchise 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.
Toho character
chosen
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.
kaiju film series
A kaiju film series is a collection of movies centered around recurring giant monsters, typically featuring their battles with humanity, other creatures, or each other across multiple interconnected stories.
-
D.
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.
-
E.
entity in the Pacific Rim universe
A Pacific Rim universe entity is any distinct being, machine, or organism—such as Jaegers, Kaiju, humans, or related constructs—that exists within and interacts with the narrative world defined by interdimensional monster invasions and giant robotic defenders.
- 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_69d889d520008190a26917a95bf1c2ea |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:44 a.m.