Triple
T37466897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dr. Neo Cortex (various facilities) |
E931054
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Crash Bandicoot location |
C62933
|
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: Crash Bandicoot location Context triple: [Dr. Neo Cortex (various facilities), instanceOf, Crash Bandicoot location]
-
A.
Crash Bandicoot game
A Crash Bandicoot game is a fast-paced, character-driven 3D platformer where players guide the titular marsupial through linear levels filled with obstacles, enemies, and collectibles to thwart a villain’s plans.
-
B.
Sonic the Hedgehog location
A Sonic the Hedgehog location is any distinct place within the Sonic universe—such as zones, cities, or landmarks—characterized by unique geography, hazards, and interactive elements that influence gameplay and story events.
-
C.
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.
-
D.
Super Mario location
A Super Mario location is any distinct, navigable area or environment within the Super Mario universe where gameplay, exploration, and interactions with characters and obstacles occur.
-
E.
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.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.