Triple
T18370705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vorta |
E446173
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | genetically engineered species |
C40421
|
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: genetically engineered species Context triple: [Vorta, instanceOf, genetically engineered species]
-
A.
genetically engineered hybrid
A genetically engineered hybrid is an organism created by deliberately combining genetic material from different species or strains to express selected traits that do not occur together in nature.
-
B.
genetically engineered lynx
A genetically engineered lynx is a bioengineered wild feline whose DNA has been deliberately modified to enhance or alter traits such as size, intelligence, resilience, or specific biological functions beyond those found in natural lynx populations.
-
C.
genetically engineered superhuman
A genetically engineered superhuman is an individual whose DNA has been deliberately modified to enhance physical, mental, or other abilities far beyond typical human limits.
-
D.
genetic engineer
A genetic engineer is a professional who manipulates and modifies the genetic material of organisms using biotechnological tools to study gene function or develop new traits and applications.
-
E.
community of human-animal hybrids
A community of human-animal hybrids is a socially organized group of individuals who possess both human and animal traits, sharing a common culture, environment, and set of norms shaped by their dual natures.
- 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_69d8b9f370b88190b1e5081c2c238e7f |
completed | April 10, 2026, 8:50 a.m. |
Created at: April 10, 2026, 10:44 a.m.