Triple
T24783955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Discworld conventions |
E620069
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | literary fan event |
C2657
|
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: literary fan event Context triple: [Discworld conventions, instanceOf, literary fan event]
-
A.
literary celebration
A literary celebration is an event or occasion dedicated to honoring, enjoying, and promoting literature, its creators, and its cultural impact through activities such as readings, discussions, and performances.
-
B.
fan convention
chosen
A fan convention is a large organized gathering where enthusiasts of specific media, genres, or hobbies come together to celebrate, meet creators and celebrities, attend panels and activities, and connect with fellow fans.
-
C.
literary salon
A literary salon is a regular gathering, often in a private home or intimate venue, where writers, intellectuals, and enthusiasts meet to discuss literature, exchange ideas, and foster artistic and intellectual community.
-
D.
publishing industry event
A publishing industry event is a planned gathering where professionals involved in creating, producing, and distributing written or digital content meet to network, share knowledge, showcase works, and discuss trends and opportunities in the publishing field.
-
E.
literary scene
A literary scene is a cohesive unit of storytelling in which characters interact within a specific time and place to advance the plot, reveal character, or develop theme through concrete action and detail.
- 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_69e2fabdbe8c8190adbb9434b8636cad |
completed | April 18, 2026, 3:30 a.m. |
Created at: April 18, 2026, 4:45 a.m.