Triple
T35065780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David (android) |
E1011726
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Alien franchise character |
C62418
|
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: Alien franchise character Context triple: [David (android), instanceOf, Alien franchise character]
-
A.
Alien franchise installment
An Alien franchise installment is a narrative work—such as a film, game, or comic—set in the Alien universe that explores encounters with xenomorphs and related entities, expanding the overarching mythos through new characters, settings, and conflicts.
-
B.
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.
-
C.
location in the Alien franchise
A location in the Alien franchise is any distinct setting—such as a spaceship, space station, planetary body, colony, or facility—where narrative events involving characters, xenomorphs, or related entities take place.
-
D.
character in the Planet of the Apes franchise
A character in the Planet of the Apes franchise is any individual—human, ape, or other sentient being—who exists within the series’ narrative universe and participates in its stories, conflicts, and themes.
-
E.
Blade Runner character
A Blade Runner character is an individual—human, replicant, or ambiguous—whose identity, morality, and purpose are explored within the dystopian, neo-noir world of the Blade Runner universe.
- 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_69f76dd193108190af2528186f25b72a |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.