Triple
T31107042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Titans (MonsterVerse) |
E792822
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | collective term for giant monsters |
C12142
|
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: collective term for giant monsters Context triple: [Titans (MonsterVerse), instanceOf, collective term for giant monsters]
-
A.
MonsterVerse creature
chosen
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.
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.
-
C.
multi‑headed monster
A multi-headed monster is a fearsome creature with multiple independently acting heads sharing a single body, often embodying chaos, resilience, and overwhelming power.
-
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.
Monsters
Monsters are fantastical or supernatural beings, often embodying fear, danger, or the unknown, that challenge heroes and societies within myths, stories, and games.
- 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_69f224cfd5d881908ec6447bc321cd58 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:03 p.m.