Triple
T20461343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raccoon City |
E501930
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | location in Resident Evil franchise |
C43562
|
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 Resident Evil franchise Context triple: [Raccoon City, instanceOf, location in Resident Evil franchise]
-
A.
Resident Evil character
A Resident Evil character is an individual within the franchise’s universe who navigates bioterror outbreaks, confronts mutated creatures, and advances the overarching narrative of survival horror.
-
B.
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.
-
C.
location in Marvel Comics
A "location in Marvel Comics" is any fictional place, setting, or environment within the Marvel universe where characters act and stories unfold, ranging from specific cities and planets to dimensions and hidden realms.
-
D.
location in the Marvel Universe
A "location in the Marvel Universe" is any distinct place—such as a city, planet, dimension, or specific site—within Marvel's fictional multiverse where characters, events, and stories occur.
-
E.
location in the Jurassic Park franchise
A "location in the Jurassic Park franchise" represents any distinct geographic or constructed setting—such as islands, facilities, enclosures, or visitor areas—where narrative events involving dinosaurs and human characters take place.
- 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_69e0b4ad4940819098cf2ff6413574e5 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:33 a.m.