Triple
T37886850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | InterTabac |
E945017
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | tobacco industry event |
C63009
|
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: tobacco industry event Context triple: [InterTabac, instanceOf, tobacco industry event]
-
A.
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.
-
B.
hospitality industry event
A hospitality industry event is a planned gathering where professionals from hotels, restaurants, travel, and related services meet to network, showcase offerings, share industry insights, and explore business opportunities.
-
C.
foodservice industry event
A foodservice industry event is a planned gathering where professionals and stakeholders in the food and beverage sector meet to network, showcase products, share knowledge, and explore business opportunities.
-
D.
petroleum industry event
A petroleum industry event is a planned gathering where professionals, companies, and stakeholders in the oil and gas sector meet to share information, showcase technologies, discuss market trends, and build business relationships.
-
E.
video game industry event
A video game industry event is a planned gathering where developers, publishers, hardware makers, media, and fans come together to showcase, promote, and discuss video games, technologies, and related business opportunities.
- F. None of above. chosen
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_69f76ef02668819089e7940c4001af5e |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:19 p.m.