Triple
T32125028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaff |
E820475
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Blade Runner character |
C58866
|
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: Blade Runner character Context triple: [Gaff, instanceOf, Blade Runner character]
-
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.
Starship Troopers character
A Starship Troopers character is an individual—human or alien—who exists within the militaristic, satirical sci-fi universe of Starship Troopers, defined by their role in interstellar warfare, political ideology, and interactions with the series’ themes of duty, citizenship, and propaganda.
-
C.
Dune character
A Dune character is an individual entity within the Dune universe, defined by distinct traits, roles, and relationships that drive the saga’s political, ecological, and spiritual narratives.
-
D.
Tron character
A Tron character is a stylized, neon-lit digital persona existing within a computer-generated world, embodying programs, users, or security forces that interact through high-tech combat and light-based vehicles.
-
E.
Lensman character
A Lensman character is an elite, telepathically empowered agent of the Galactic Patrol, entrusted with a powerful Lens that symbolizes their incorruptible authority and duty to protect civilization.
- 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_69f34902d42c819083a8e6bba9a8bb9a |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:29 a.m.