Triple
T30348723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Afterlife High School |
E771932
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | location in anime |
C56777
|
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: location in anime Context triple: [Afterlife High School, instanceOf, location in anime]
-
A.
location in the Sonic the Hedgehog series
A location in the Sonic the Hedgehog series represents any distinct place or environment within the Sonic universe, such as zones, cities, or landmarks, where gameplay, story events, or character interactions occur.
-
B.
location in comics
A location in comics is any specific place or setting—real or fictional—where comic book events occur and characters interact, helping to establish atmosphere, context, and narrative progression.
-
C.
location in the Avatar universe
A location in the Avatar universe is any distinct place—such as a city, region, landmark, or realm—within the world of Avatar: The Last Airbender and The Legend of Korra that has its own geographic, cultural, or narrative significance.
-
D.
location in the Mario series
A location in the Mario series is any distinct place or environment within the Mario universe—such as kingdoms, worlds, levels, or specific areas—where gameplay, story events, or character interactions occur.
-
E.
location in SpongeBob SquarePants
A location in SpongeBob SquarePants is any distinct place or setting within the show's underwater world where characters interact and events occur, such as buildings, natural environments, or specific areas in Bikini Bottom and beyond.
- 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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:56 p.m.