Triple
T17459344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shobijin |
E425112
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | kaiju franchise 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: kaiju franchise character Context triple: [Shobijin, instanceOf, kaiju franchise 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.
kaiju spokesperson
A kaiju spokesperson is a representative who communicates on behalf of giant monsters, translating their destructive actions and intentions into messages understandable to humans and other stakeholders.
-
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.
kaiju researcher
A kaiju researcher is a specialist who studies giant monsters, analyzing their biology, behavior, origins, and ecological impact to better understand and potentially mitigate the threats they pose.
-
E.
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.
- 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_69d889db0ba481908402409af3b37917 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:47 a.m.