Triple
T3419133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Google I/O 2014 |
E72076
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Google event |
C1824
|
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: Google event Context triple: [Google I/O 2014, instanceOf, Google event]
-
A.
Google service
A Google service is any software application or platform provided by Google that delivers specific online functionality—such as search, email, storage, or productivity tools—over the internet to users.
-
B.
event
chosen
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.
-
C.
Google office
A Google office is a modern, collaborative workspace designed by Google that combines advanced technology, flexible work areas, and employee-focused amenities to foster innovation and productivity.
-
D.
virtual event management platform
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.
-
E.
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.
- 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_69ad85ad38e48190b7660c5118a35289 |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:15 p.m.