Triple
T15319694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federlegno Arredo Eventi |
E366255
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | trade fair and events organization 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: trade fair and events organization company Context triple: [Federlegno Arredo Eventi, instanceOf, trade fair and events organization 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.
trade fair
A trade fair is a large, organized event where businesses and professionals from specific industries exhibit, demonstrate, and promote their products or services to potential buyers, partners, and the public.
-
C.
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.
-
D.
world’s fair organizing body
An organization responsible for planning, coordinating, and overseeing all aspects of a world’s fair, including theme development, participant engagement, logistics, funding, and compliance with international exposition standards.
-
E.
festival organization
Festival organization is the coordinated planning, management, and execution of all logistical, financial, promotional, and experiential aspects required to design and deliver a successful festival event.
- 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_69d85a121520819093dcce999fdefe1a |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:16 a.m.