Triple
T36697292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moonstone |
E906126
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Marvel Comics antihero |
C2832
|
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: Marvel Comics antihero Context triple: [Moonstone, instanceOf, Marvel Comics antihero]
-
A.
Marvel Comics character
chosen
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.
Marvel Comics person
A Marvel Comics person is an individual character—human, superhuman, alien, or otherwise—who exists within the Marvel universe and participates in its stories, events, and relationships.
-
C.
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.
-
D.
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.
-
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_69f76e7195c48190b5580c9cfb01e95f |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:12 p.m.