Triple
T38218936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Facehugger |
E1010756
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | creature in the Alien franchise |
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: creature in the Alien franchise Context triple: [Facehugger, instanceOf, creature in the Alien franchise]
-
A.
Alien franchise character
chosen
An Alien franchise character is an entity—human, xenomorph, android, or other being—appearing within the Alien universe, defined by its role in the series’ narratives of survival, horror, and interspecies conflict.
-
B.
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.
-
C.
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.
-
D.
alien
An alien is a hypothetical or fictional being originating from a world or dimension other than Earth, often depicted with unfamiliar biology, culture, and technology.
-
E.
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.
- 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_69f76dcdc7708190a5f1751d53f40ffe |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:30 p.m.