Triple
T29082865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avengers (temporary ally) |
E734024
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional superhero team affiliation role |
C10293
|
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: fictional superhero team affiliation role Context triple: [Avengers (temporary ally), instanceOf, fictional superhero team affiliation role]
-
A.
fictional superhero duo
A fictional superhero duo is a pair of complementary, often contrasting heroes whose combined abilities, personalities, and narratives drive collaborative crime-fighting and character development within a shared story world.
-
B.
Marvel Comics team
chosen
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.
-
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.
fictional superhero family
A fictional superhero family is a group of related characters, typically spanning multiple generations, who share extraordinary abilities and a common mission to protect others while navigating the dynamics and challenges of family life.
-
E.
Teen Titans character
A Teen Titans character is a young superhero or ally within the Teen Titans universe, defined by their unique powers, personality, and role in the team’s adventures and interpersonal dynamics.
- 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_69f05b0c0f28819086eae6e84f2ae472 |
completed | April 28, 2026, 7 a.m. |
Created at: April 28, 2026, 10:57 a.m.