Triple
T30932769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scranton branch |
E788040
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional office branch |
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 office branch Context triple: [Scranton branch, instanceOf, fictional office branch]
-
A.
fictional government ministry
A fictional government ministry is an imagined official department within a government, created in stories or worldbuilding to oversee specific policy areas, functions, or societal needs.
-
B.
fictional corporate office
chosen
A fictional corporate office is an imagined workplace setting that represents the structure, culture, and daily operations of a business organization, often used as a backdrop for storytelling, satire, or exploration of professional dynamics.
-
C.
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.
-
D.
fictional political institution
A fictional political institution is an imagined organization or governing body within a narrative world that creates, interprets, or enforces rules, policies, or power structures for story purposes.
-
E.
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.
- F. None of above.
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_69f224c0b7fc819090cb89df60d23653 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:52 p.m.