Triple
T4028838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Megadodo Publications |
E83657
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional publishing 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 publishing company Context triple: [Megadodo Publications, instanceOf, fictional publishing 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.
science fiction publisher
A science fiction publisher is a company or imprint that acquires, edits, produces, markets, and distributes speculative fiction works focused on futuristic, technological, or imaginative themes.
-
C.
fantasy publisher
A fantasy publisher is a company or imprint that specializes in acquiring, editing, producing, and marketing books and other media set in imaginative, often magical worlds.
-
D.
publishing company imprint
A publishing company imprint is a trade name or brand under which a publisher releases specific categories or lines of books, often to target particular markets or audiences while remaining part of the larger parent company.
-
E.
publishing organization
A publishing organization is an entity that selects, produces, and distributes content such as books, journals, or digital media to reach and inform a target audience.
- 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_69aed92e29ac819080f7a98b594fec05 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:36 p.m.