Triple
T33516137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TrekFest |
E858371
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Star Trek 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: Star Trek fan event Context triple: [TrekFest, instanceOf, Star Trek fan event]
-
A.
event in Star Trek canon
An event in Star Trek canon is a significant occurrence or incident within the Star Trek universe—such as battles, discoveries, political changes, or personal milestones—that shapes characters, timelines, or interstellar relations and is recognized as part of the official storyline.
-
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.
science fiction convention
A science fiction convention is a organized gathering of fans, creators, and industry professionals celebrating science fiction and related genres through panels, screenings, cosplay, merchandise, and community activities.
-
D.
science fiction event
A science fiction event is a gathering, occurrence, or phenomenon—real or fictional—centered on speculative futures, advanced technologies, or imaginative worlds that explore the impact of science and innovation on individuals and societies.
-
E.
Star Trek location
A Star Trek location is any distinct place within the Star Trek universe—such as planets, starships, space stations, or regions of space—where narrative events, exploration, and interactions occur.
- 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_69f3497721848190978fbee5e0a526f8 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:39 a.m.