Triple
T15673454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chief Executive Officer of Monsters, Inc. |
E377376
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional corporate office |
C35701
|
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: fictional corporate office Context triple: [Chief Executive Officer of Monsters, Inc., instanceOf, fictional corporate office]
-
A.
fictional company
A fictional company is an imagined business entity created for storytelling, simulation, or illustrative purposes, complete with its own brand, structure, and operations but without real-world legal or commercial existence.
-
B.
fictional skyscraper
A fictional skyscraper is an imagined, often architecturally distinctive high-rise building that serves as a central setting or symbolic structure within a narrative world.
-
C.
fictional hotel
A fictional hotel is an imagined lodging establishment, often richly detailed in setting, atmosphere, and services, that serves as a narrative backdrop or central location in stories, films, games, or other creative works.
-
D.
fictional research institution
A fictional research institution is an imagined organization dedicated to conducting systematic investigation and experimentation, often serving as a setting or driver for scientific, technological, or societal developments within a narrative.
-
E.
fictional house
A fictional house is an imagined dwelling, often richly detailed in literature, film, or other media, that serves as a setting reflecting the story’s themes, characters, and world.
- 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_69d85cd2e28481909d4e975bee20872f |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 4:16 a.m.