Triple
T37131163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Bad Wolf’s shop |
E919519
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | location in the Shrek franchise |
C65967
|
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 the Shrek franchise Context triple: [Big Bad Wolf’s shop, instanceOf, location in the Shrek franchise]
-
A.
character in the Shrek franchise
A character in the Shrek franchise is any fictional being—human, animal, or fantastical creature—who inhabits the fairy-tale-inspired world of Shrek and contributes to its narrative through distinct personalities, roles, and relationships.
-
B.
realm in the Land of Ooo
A realm in the Land of Ooo is a distinct, often magical territory or domain with its own geography, inhabitants, and rules that together form part of the larger Adventure Time world.
-
C.
Disney media franchise setting
A Disney media franchise setting is a cohesive fictional world or universe, originating from Disney properties, that provides the shared backdrop, rules, and locations for interconnected stories, characters, and media products.
-
D.
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.
-
E.
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.
- 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_69f76e9d13e48190a108f7fbf80ff375 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:15 p.m.