Triple
T28567003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zangen Pharmaceuticals |
E722706
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional pharmaceutical company |
C7523
|
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 pharmaceutical company Context triple: [Zangen Pharmaceuticals, instanceOf, fictional pharmaceutical company]
-
A.
fictional company
chosen
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 pharmacy
A fictional pharmacy is an imagined or narrative-based establishment that provides medicinal products, health services, and related interactions within a story or conceptual setting.
-
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 factory
A fictional factory is an imagined industrial facility, often depicted in stories or media, where goods, ideas, or fantastical items are produced under unique or extraordinary conditions.
-
E.
fictional corporate office
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.
- 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_69f01a5f69d08190ad5c0d2167078dec |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 28, 2026, 4:07 a.m.