Triple
T37650638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dinosaurs on Isla Sorna |
E937162
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Group of genetically engineered dinosaurs |
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: Group of genetically engineered dinosaurs Context triple: [Dinosaurs on Isla Sorna, instanceOf, Group of genetically engineered dinosaurs]
-
A.
dinosaur cloning facility
A dinosaur cloning facility is a high-security scientific complex where preserved prehistoric DNA is extracted, sequenced, and used to bioengineer and incubate living dinosaurs for research, display, or commercial purposes.
-
B.
Dinosaur-like creature
A dinosaur-like creature is a large, prehistoric-inspired animal characterized by reptilian features such as scales or rough skin, powerful limbs, and often a massive tail, evoking the appearance and presence of ancient dinosaurs.
-
C.
Xenomorph-human hybrid
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.
-
D.
genetically engineered species
chosen
A genetically engineered species is a group of organisms whose genetic material has been deliberately modified using biotechnology to express desired traits not typically found in the original population.
-
E.
Tyrannosaurus rex specimen
A Tyrannosaurus rex specimen is a specific individual fossil or preserved example of the species Tyrannosaurus rex, used to study its anatomy, behavior, and evolutionary relationships.
- 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_69f76ed4fe908190b8061c5c135e0971 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:18 p.m.