Triple
T5940888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Owen Grady |
E132162
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Jurassic Park character |
C19610
|
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: Jurassic Park character Context triple: [Owen Grady, instanceOf, Jurassic Park character]
-
A.
Transformers character
A Transformers character is a sentient robotic being from the Transformers universe, typically capable of transforming between a humanoid robot form and an alternate mode such as a vehicle, weapon, or creature, with distinct allegiance, personality, and abilities.
-
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.
MonsterVerse creature
A MonsterVerse creature is a colossal, often ancient and otherworldly titan whose existence shapes global ecosystems, myths, and human history through its immense power and presence.
-
D.
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.
-
E.
Nintendo character
A Nintendo character is a fictional persona created or licensed by Nintendo that appears in its video games, media, and related merchandise, often embodying distinctive abilities, personalities, and roles within their respective game worlds.
- 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_69c0085c55dc8190aa90e242c956e2fa |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 4:01 p.m.