Triple
T34006484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Los Bandoleros |
E871979
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Fast & Furious franchise work |
C59245
|
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: Fast & Furious franchise work Context triple: [Los Bandoleros, instanceOf, Fast & Furious franchise work]
-
A.
Fast & Furious character
A Fast & Furious character is a high-octane persona defined by exceptional driving skills, deep loyalty to their chosen “family,” and a willingness to bend or break the law in pursuit of adrenaline, justice, or redemption.
-
B.
Frozen franchise work
A Frozen franchise work is any creative production—such as a film, short, book, game, or related media—set in the Frozen universe and featuring its characters, themes, or settings as established by Disney’s Frozen series.
-
C.
Transformers series
The Transformers series is a multimedia franchise centered on sentient robots that can transform into vehicles, weapons, and other objects, exploring their conflicts and alliances across comics, cartoons, films, and toys.
-
D.
location in the Cars franchise
A "location in the Cars franchise" is any distinct place or setting—such as towns, racetracks, landmarks, or regions—depicted within the Cars universe where characters live, travel, or events occur.
-
E.
vehicle in the Marvel Cinematic Universe
A vehicle in the Marvel Cinematic Universe is any mode of transportation—terrestrial, aerial, aquatic, or spacefaring—used by characters to travel, fight, or support missions within the MCU’s narrative.
- 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_69f349a08848819084b348d64c1879c3 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:50 a.m.