Triple
T12999856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NeXT Introduction event 1988 |
E322139
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | computer industry event |
C25769
|
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: computer industry event Context triple: [NeXT Introduction event 1988, instanceOf, computer industry event]
-
A.
technology conference
A technology conference is a structured event where professionals, enthusiasts, and organizations gather to share knowledge, showcase innovations, and discuss trends and developments in technology.
-
B.
music industry event
A music industry event is a planned gathering where artists, professionals, and stakeholders in the music business come together for performances, networking, promotion, and industry-related activities.
-
C.
IBM event
An IBM event is a scheduled gathering, either physical or virtual, organized or sponsored by IBM to share knowledge, showcase technologies, foster collaboration, and engage with customers, partners, or the broader tech 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.
Apple-related event
chosen
An Apple-related event is a scheduled occurrence organized or driven by Apple Inc. (or its ecosystem) to announce, showcase, or discuss Apple products, services, technologies, or company initiatives.
- 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_69d8076479b8819090afce3591939cdf |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 8:46 p.m.