Triple
T7147946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meetup.com |
E166616
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | online event platform |
C8625
|
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: online event platform Context triple: [Meetup.com, instanceOf, online event platform]
-
A.
virtual event management platform
chosen
A virtual event management platform is a digital system that enables organizations to plan, host, manage, and analyze online events such as conferences, webinars, and trade shows through integrated tools for registration, content delivery, engagement, and reporting.
-
B.
virtual event management platform
A virtual event management platform is a software system that enables organizations to plan, host, manage, and analyze online events by integrating registration, content delivery, engagement tools, and post-event analytics in a unified digital environment.
-
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.
convening platform
A convening platform is a structured environment—physical, digital, or hybrid—that brings diverse stakeholders together to connect, collaborate, and coordinate around shared goals or issues.
-
E.
event
An event is a distinct occurrence or happening, often bounded in time and space, that involves one or more participants and may trigger changes in state or behavior within a system.
- 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_69c68886779c8190a8e3fbabffe68253 |
completed | March 27, 2026, 1:39 p.m. |
Created at: March 27, 2026, 2:46 p.m.