Triple
T36347324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Lawton incident |
E895099
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | MonsterVerse event |
C64232
|
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: MonsterVerse event Context triple: [USS Lawton incident, instanceOf, MonsterVerse event]
-
A.
MonsterVerse tie-in comic
A MonsterVerse tie-in comic is a narrative graphic work that expands the shared cinematic universe of giant monsters like Godzilla and King Kong by exploring side stories, character backstories, and events connected to the films.
-
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.
organization in the MonsterVerse
An organization in the MonsterVerse is a structured group of humans or entities, such as Monarch or Apex, that operates with specific goals related to the study, control, exploitation, or defense against Titans and other colossal creatures within the shared cinematic universe.
-
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.
Wrestle Kingdom event
A Wrestle Kingdom event is New Japan Pro-Wrestling’s annual flagship professional wrestling supercard, typically held each January at the Tokyo Dome and featuring marquee matches, title bouts, and international talent.
- 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_69f76e4f437c8190a1af3ea2564f41f5 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:09 p.m.