Triple
T31107091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. military (MonsterVerse) |
E792823
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | organization in the MonsterVerse |
C59659
|
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: organization in the MonsterVerse Context triple: [U.S. military (MonsterVerse), instanceOf, organization in the MonsterVerse]
-
A.
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.
-
B.
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.
-
C.
Monsters
Monsters are fantastical or supernatural beings, often embodying fear, danger, or the unknown, that challenge heroes and societies within myths, stories, and games.
-
D.
Monster group
A Monster group is the largest sporadic simple group in group theory, an enormous and highly symmetric algebraic structure with intricate connections to number theory, geometry, and string theory.
-
E.
monster crossover film
A monster crossover film is a movie that brings together two or more established monster characters or franchises into a single shared narrative, often pitting them against each other or uniting them against a common threat.
- F. None of above. chosen
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_69f224cfd5d881908ec6447bc321cd58 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:03 p.m.