Triple
T10194742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chris Bradley |
E238132
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | X-Men character |
C4314
|
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: X-Men character Context triple: [Chris Bradley, instanceOf, X-Men character]
-
A.
Marvel Comics character
A Marvel Comics character is a fictional individual within the Marvel Universe, possessing distinct abilities, personalities, and story arcs that interact with other characters and events across various comic book series and related media.
-
B.
comic book character
chosen
A comic book character is a fictional persona, often possessing distinctive abilities, traits, or backstory, that appears in sequential art narratives and drives the plot through their actions and development.
-
C.
Transformers character
A Transformers character is a sentient robotic being from the Transformers universe, typically capable of transforming between a humanoid robot form and an alternate mode such as a vehicle, weapon, or creature, with distinct allegiance, personality, and abilities.
-
D.
member of the Guardians of the Galaxy
A member of the Guardians of the Galaxy is an individual who belongs to a loosely organized team of interstellar adventurers dedicated to protecting the universe from cosmic threats.
-
E.
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.
- 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_69ca84de1b208190bf17bb305b002605 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 9:13 p.m.