Triple
T35843561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Zod |
E1036150
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | DC Comics fictional organization |
C40866
|
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: DC Comics fictional organization Context triple: [House of Zod, instanceOf, DC Comics fictional organization]
-
A.
DC Comics fictional family
chosen
A DC Comics fictional family is a group of related characters within the DC universe, connected by blood, marriage, or legacy, whose shared relationships and histories shape their individual stories and collective impact on the narrative.
-
B.
DC Comics superhero
A DC Comics superhero is a fictional character, often possessing extraordinary abilities or advanced technology, who fights evil and protects the innocent within the shared DC Universe.
-
C.
DC Comics superhero franchise
A DC Comics superhero franchise is a multimedia entertainment property centered on one or more DC superheroes, spanning comic books, films, television, games, and related merchandise within a shared fictional universe.
-
D.
Marvel Comics superhero team
A Marvel Comics superhero team is a group of super-powered individuals who unite to confront threats too great for any single hero, often balancing world-saving missions with complex interpersonal dynamics and moral dilemmas.
-
E.
Marvel Comics organization
A Marvel Comics organization is a fictional group, agency, or collective within the Marvel Universe that unites characters around a common purpose, ideology, or function, often influencing major storylines and events.
- 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_69f76e1a29e8819088280f26096aeb55 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.