Triple
T7658531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lady Jaye |
E173445
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | G.I. Joe character |
C22365
|
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: G.I. Joe character Context triple: [Lady Jaye, instanceOf, G.I. Joe 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.
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.
-
C.
Jurassic Park character
A Jurassic Park character is an individual—human or dinosaur—whose actions, traits, and relationships drive the narrative of survival, science, and chaos within the dinosaur-filled Jurassic Park universe.
-
D.
Family Guy character
A Family Guy character is a fictional person or anthropomorphic being from the animated television series "Family Guy," defined by exaggerated traits, comedic behavior, and relationships within the show's satirical depiction of American family and society.
-
E.
Toho character
A Toho character is a fictional entity originating from Toho-produced media, such as kaiju films or related works, defined by its unique traits, abilities, and narrative role within the Toho universe.
- 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_69c69955517c819085bc715b96d304d2 |
completed | March 27, 2026, 2:51 p.m. |
Created at: March 27, 2026, 3:59 p.m.