Triple
T9995872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luke Hobbs |
E197199
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Fast & Furious character |
C27559
|
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: Fast & Furious character Context triple: [Luke Hobbs, instanceOf, Fast & Furious character]
-
A.
G.I. Joe character
A G.I. Joe character is a fictional military-themed action hero or villain, each with a distinct code name, specialty, personality, and backstory within the G.I. Joe universe.
-
B.
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.
-
C.
MonsterVerse character
A MonsterVerse character is a fictional being—often a giant monster, titan, or associated human figure—originating from the shared cinematic universe that includes Godzilla, Kong, and related creatures, defined by its role within that interconnected storyline.
-
D.
member of the Guardians of the Galaxy
A member of the Guardians of the Galaxy is an individual who belongs to a loosely organized team of interstellar adventurers dedicated to protecting the universe from cosmic threats.
-
E.
member of the Chrysler family
A member of the Chrysler family is an individual who is biologically or legally related to the Chrysler lineage, historically associated with the founders and successors of the Chrysler automotive enterprise.
- 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_69ca82f3b61c81908ecc2c1c96dbc2e4 |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 8:50 p.m.