Triple
T18689851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zed |
E456962
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Men in Black character |
C40635
|
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: Men in Black character Context triple: [Zed, instanceOf, Men in Black character]
-
A.
Austin Powers character
An Austin Powers character is a flamboyant, comedic persona from the spy-parody film series, defined by exaggerated 1960s-inspired style, over-the-top behavior, and satirical takes on espionage tropes.
-
B.
Mission: Impossible character
A Mission: Impossible character is an individual—often a highly skilled agent, ally, or adversary—whose actions, loyalties, and specialized abilities drive the intricate espionage missions and high-stakes conflicts of the Mission: Impossible universe.
-
C.
character from Megamind
A character from Megamind is an individual, often exaggerated and comedic, who inhabits the film’s superhero-satire world and contributes to its narrative through distinct personality traits, visual design, and relationships with other characters.
-
D.
Despicable Me character
A Despicable Me character is a whimsical, often exaggerated individual from the Despicable Me universe whose personality, appearance, and actions contribute to the franchise’s blend of comedy, heart, and mischief.
-
E.
character in Dirk Gently series
A character in the Dirk Gently series is any person, entity, or being—ordinary, eccentric, or supernatural—who participates in the interconnected, often absurd events surrounding the holistic detective Dirk Gently.
- 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_69d8d391eb488190ac2e9abf5bf255e4 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:49 a.m.