Triple
T19453859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hawkins National Laboratory |
E486685
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | location in Stranger Things |
C41784
|
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 Stranger Things Context triple: [Hawkins National Laboratory, instanceOf, location in Stranger Things]
-
A.
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.
-
B.
Star Trek location
A Star Trek location is any distinct place within the Star Trek universe—such as planets, starships, space stations, or regions of space—where narrative events, exploration, and interactions occur.
-
C.
location in the Doctor Who universe
A "location in the Doctor Who universe" is any distinct place—planet, spaceship, dimension, time period, or specific site—where events, characters, or stories from Doctor Who occur or are referenced.
-
D.
location in the Torchwood universe
A "location in the Torchwood universe" is any distinct place—on Earth, in space, or across time—where events, organizations, or characters from Torchwood exist or act, such as cities, alien worlds, hidden bases, or temporal anomalies.
-
E.
location in the Marvel Cinematic Universe
A location in the Marvel Cinematic Universe is any distinct place—real or fictional—where events, characters, or organizations appear or operate within the interconnected MCU narrative.
- 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_69d8e8d86d608190bd199a98d0297f27 |
completed | April 10, 2026, 12:11 p.m. |
Created at: April 10, 2026, 1:38 p.m.