Triple
T17910257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lapis Lazuli |
E447801
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | character from Steven Universe |
C40050
|
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: character from Steven Universe Context triple: [Lapis Lazuli, instanceOf, character from Steven Universe]
-
A.
anime character
An anime character is a stylized, often exaggerated fictional persona originating from Japanese animation, defined by distinctive visual design, expressive emotions, and participation in narrative-driven stories.
-
B.
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.
-
C.
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.
-
D.
Arrowverse character
An Arrowverse character is a fictional individual who exists within the shared television universe based on DC Comics properties, appearing in one or more interconnected Arrowverse series and contributing to its overarching narrative.
-
E.
Big Hero 6 character
A Big Hero 6 character is an individual—human, robot, or otherwise—who inhabits the futuristic city of San Fransokyo and contributes to the story’s blend of superhero action, emotional growth, and technological innovation.
- 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_69d8b9f6d394819082a6d69fd1e23d2f |
completed | April 10, 2026, 8:51 a.m. |
Created at: April 10, 2026, 10:19 a.m.