Triple
T29427267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orm Marius |
E746329
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Aquaman character |
C38137
|
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: Aquaman character Context triple: [Orm Marius, instanceOf, Aquaman character]
-
A.
Superman character
A Superman character is a fictional superhero archetype possessing extraordinary powers, a strong moral code, and a dual identity used to protect others and fight injustice.
-
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.
kaiju-related character
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.
-
D.
Arrowverse character
chosen
An Arrowverse character is a fictional individual who exists within the shared television universe based on DC Comics properties, appearing in one or more interconnected Arrowverse series and contributing to its overarching narrative.
-
E.
Lensman character
A Lensman character is an elite, telepathically empowered agent of the Galactic Patrol, entrusted with a powerful Lens that symbolizes their incorruptible authority and duty to protect civilization.
- 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_69f0a7a06e0081908add494075912eb4 |
completed | April 28, 2026, 12:27 p.m. |
Created at: April 28, 2026, 3:10 p.m.