Triple
T30596799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vishanti |
E778809
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Marvel Comics character team |
C10295
|
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 character team Context triple: [Vishanti, instanceOf, Marvel Comics character team]
-
A.
Marvel Comics team
A Marvel Comics team is a group of superheroes or characters who regularly operate together within the Marvel Universe, united by a common purpose, affiliation, or mission.
-
B.
Marvel Comics superhero team
chosen
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.
-
C.
DC Comics team
A DC Comics team is a group of superheroes and/or supervillains within the DC Universe who unite under a common purpose, identity, or mission to confront threats or pursue shared goals.
-
D.
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.
-
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_69f224a1570c8190a85d3ac330479a79 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:24 p.m.