Triple
T22763785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paizo Publishing |
E563064
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | tabletop role-playing game publisher |
C42869
|
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: tabletop role-playing game publisher Context triple: [Paizo Publishing, instanceOf, tabletop role-playing game publisher]
-
A.
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.
-
B.
tabletop game
A tabletop game is a structured form of play conducted on a flat surface using physical components such as boards, cards, dice, or miniatures, governed by explicit rules and typically involving two or more players.
-
C.
game publishing company
chosen
A game publishing company is an organization that finances, markets, distributes, and often oversees the development of video or tabletop games created by internal teams or external developers.
-
D.
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.
-
E.
interactive fiction publisher
An interactive fiction publisher is an entity that selects, develops, and distributes narrative-driven, choice-based digital or print works, often supporting authors with editorial, technical, and marketing resources tailored to interactive storytelling.
- 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_69e24552e11c81909c2d61578a558bd7 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 17, 2026, 3:26 p.m.