Triple
T17887668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Canary |
E447237
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | DC Comics superheroine |
C23891
|
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: DC Comics superheroine Context triple: [Black Canary, instanceOf, DC Comics superheroine]
-
A.
DC Comics superhero
chosen
A DC Comics superhero is a fictional character, often possessing extraordinary abilities or advanced technology, who fights evil and protects the innocent within the shared DC Universe.
-
B.
Marvel Comics character
A Marvel Comics character is a fictional individual within the Marvel Universe, possessing distinct abilities, personalities, and story arcs that interact with other characters and events across various comic book series and related media.
-
C.
DC Comics superhero franchise
A DC Comics superhero franchise is a multimedia entertainment property centered on one or more DC superheroes, spanning comic books, films, television, games, and related merchandise within a shared fictional universe.
-
D.
Marvel Comics superhero team
A Marvel Comics superhero team is a group of super-powered individuals who unite to confront threats too great for any single hero, often balancing world-saving missions with complex interpersonal dynamics and moral dilemmas.
-
E.
comic book character
A comic book character is a fictional persona, often possessing distinctive abilities, traits, or backstory, that appears in sequential art narratives and drives the plot through their actions and development.
- 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_69d8b9f59bd48190a6fc925a855b8bac |
completed | April 10, 2026, 8:51 a.m. |
Created at: April 10, 2026, 10:18 a.m.