Triple
T29091092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revengers |
E734854
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Marvel Cinematic Universe team |
C30530
|
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 Cinematic Universe team Context triple: [Revengers, instanceOf, Marvel Cinematic Universe team]
-
A.
Marvel Cinematic Universe organization
chosen
A Marvel Cinematic Universe organization is a structured group or agency within the MCU, composed of characters united by a common purpose, hierarchy, and resources that influence the franchise’s overarching narrative and events.
-
B.
Marvel Cinematic Universe television season
A Marvel Cinematic Universe television season is a collection of episodic, live-action or animated stories produced for television or streaming that are set within and contribute to the shared continuity, characters, and overarching narrative of the MCU franchise.
-
C.
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.
-
D.
Marvel Cinematic Universe film
A Marvel Cinematic Universe film is a feature-length motion picture produced by Marvel Studios that takes place within a shared continuity of interconnected superhero stories, characters, and events based on Marvel Comics.
-
E.
Marvel Cinematic Universe television special
A Marvel Cinematic Universe television special is a standalone, short-form televised production set within the MCU continuity that expands its characters, stories, or events outside the main film and series releases.
- 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_69f05b0ed66481908f2e864fa550d2f1 |
completed | April 28, 2026, 7 a.m. |
Created at: April 28, 2026, 11:05 a.m.