Triple
T18589096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transformers: Beast Wars |
E454311
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Transformers series |
C40934
|
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: Transformers series Context triple: [Transformers: Beast Wars, instanceOf, Transformers series]
-
A.
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.
-
B.
Marvel Cinematic Universe organization
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.
-
C.
Disney film series
A Disney film series is a collection of related movies produced or distributed by The Walt Disney Company that share common characters, settings, or narrative continuity.
-
D.
Avengers branch
An Avengers branch is a regional or specialized subdivision of the Avengers organization, formed to address localized threats and missions while operating under the broader Avengers framework.
-
E.
Spider-Man film
A Spider-Man film is a motion picture centered on the Marvel Comics superhero Spider-Man, typically exploring his dual life as Peter Parker and a masked crime-fighter who battles villains while navigating personal challenges.
- F. None of above. chosen
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_69d8d38ae7e081908a98df1251842402 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:44 a.m.