Triple
T32850937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nebuchadnezzar |
E840248
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | vehicle in The Matrix franchise |
C58542
|
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: vehicle in The Matrix franchise Context triple: [Nebuchadnezzar, instanceOf, vehicle in The Matrix franchise]
-
A.
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.
-
B.
Batman vehicle
A Batman vehicle is a specialized, high-tech mode of transportation designed for Batman, equipped with advanced weaponry, stealth capabilities, and crime-fighting tools to support his vigilantism.
-
C.
Star Wars vehicle
A Star Wars vehicle is any mode of transportation within the Star Wars universe, ranging from small personal speeders to massive capital ships, used for travel, combat, or cargo across land, air, space, or hyperspace.
-
D.
Terminator franchise element
A Terminator franchise element is any character, machine, event, technology, or narrative construct that originates from or is fundamentally tied to the Terminator universe’s depiction of time-traveling warfare between humans and sentient machines.
-
E.
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.
- 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_69f349412c78819084459850e11d29f7 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:17 a.m.