Triple
T35042441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ripley 8 |
E1011103
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | human–Xenomorph hybrid |
C32115
|
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: human–Xenomorph hybrid Context triple: [Ripley 8, instanceOf, human–Xenomorph hybrid]
-
A.
Xenomorph-human hybrid
chosen
A Xenomorph-human hybrid is a bioengineered organism that combines the predatory physiology, acid blood, and hive-driven instincts of a Xenomorph with the intelligence, adaptability, and emotional complexity of a human.
-
B.
human-alien hybrid
A human-alien hybrid is a being that combines genetic, physiological, and often cultural traits from both humans and an extraterrestrial species, resulting in unique abilities, appearances, and perspectives distinct from either parent species.
-
C.
Klingon–human hybrid
A Klingon–human hybrid is an individual of mixed Klingon and human ancestry who embodies a blend of their distinct physiologies, cultures, and psychological traits.
-
D.
Vulcan-human hybrid
A Vulcan-human hybrid is an individual born of both Vulcan and human parentage, embodying a blend of Vulcan logic, physiology, and telepathic potential with human emotion, adaptability, and cultural traits.
-
E.
human-Kaiju hybrid
A human-Kaiju hybrid is a colossal, part-human, part-monster being that combines human intelligence and emotions with the immense size, strength, and destructive capabilities of a Kaiju.
- 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_69f76dcfdda48190b1ebae5da8b54f12 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.