Triple
T29670188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miles Dyson |
E750645
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | character in the Terminator franchise |
C43723
|
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: character in the Terminator franchise Context triple: [Miles Dyson, instanceOf, character in the Terminator franchise]
-
A.
Terminator character
A Terminator character is a relentless, human-like cyborg assassin from the future, typically sent back in time with a specific mission that often pits advanced machine intelligence against human survival.
-
B.
Terminator franchise element
chosen
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.
-
C.
Avatar franchise character
An Avatar franchise character is an individual, creature, or spirit from the Avatar universe whose identity, abilities, and relationships are shaped by the world’s elemental bending, cultures, and ongoing conflicts.
-
D.
fictional organization in the Terminator franchise
A fictional organization in the Terminator franchise is a structured group—such as Skynet, Resistance cells, or corporate and military entities—whose members, goals, and resources drive the conflict between humans and machines across different timelines.
-
E.
Terminator model
A Terminator model is a highly advanced, human-like robotic assassin designed for infiltration, combat, and execution of specific targets, often featuring adaptive AI and durable endoskeletal construction.
- 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_69f0d62418a08190a401b127adf9f8a6 |
completed | April 28, 2026, 3:45 p.m. |
Created at: April 28, 2026, 7:04 p.m.