Triple
T34614983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MCH (Messecenter Herning) group |
E888837
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | events and exhibition company |
C31775
|
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: events and exhibition company Context triple: [MCH (Messecenter Herning) group, instanceOf, events and exhibition company]
-
A.
trade fair and exhibition company
chosen
A trade fair and exhibition company plans, organizes, and manages events where businesses showcase products and services, network, and engage with potential clients and partners.
-
B.
exhibition design firm
An exhibition design firm is a company that plans, designs, and produces immersive, visually engaging environments for museums, trade shows, galleries, and branded experiences to communicate stories, information, and identities.
-
C.
exhibition society
An exhibition society is an organized group or institution dedicated to planning, curating, and presenting public displays of art, artifacts, or thematic collections for cultural, educational, or promotional purposes.
-
D.
hybrid event management platform
A hybrid event management platform is a unified system that enables planning, hosting, and analyzing events that combine in-person and virtual experiences, including registration, engagement tools, content delivery, and post-event analytics.
-
E.
event management app
An event management app is a software application that helps users plan, organize, promote, and track events by managing tasks such as scheduling, registrations, ticketing, communication, and attendee engagement.
- 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_69f349d584e08190b40b9f6281ad50c4 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:03 a.m.