Triple
T359503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zoom Video Communications |
E7816
|
entity |
| Predicate | coreOffering |
P9404
|
FINISHED |
| Object | cloud-based video conferencing platform |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: cloud-based video conferencing platform | Statement: [Zoom Video Communications, coreOffering, cloud-based video conferencing platform]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreOffering Context triple: [Zoom Video Communications, coreOffering, cloud-based video conferencing platform]
-
A.
offersServiceTo
Indicates that one entity provides or makes a service available for the benefit or use of another entity.
-
B.
offersFeature
chosen
Indicates that one entity provides or makes available a particular feature or capability to another entity.
-
C.
offeredIn
Indicates that something is made available or provided within a particular context, setting, or medium.
-
D.
offersViewOf
Indicates that one entity provides a vantage point from which another entity can be seen or visually appreciated.
-
E.
offersProgram
Indicates that an entity provides or makes available a specific program (such as a course, curriculum, or initiative).
- F. None of above.
Provenance (3 batches)
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_69a2e7e880008190a6ad7e06e5d03007 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebb248608190b060553219616043 |
completed | Feb. 28, 2026, 1:20 p.m. |
| PD | Predicate disambiguation | batch_69a2e95aeed48190b5e48865cc964938 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.