Triple
T2377443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zoom Video Webinars |
E46229
|
entity |
| Predicate | supportsAudienceLocation |
P29891
|
FINISHED |
| Object | remote audiences |
—
|
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: remote audiences | Statement: [Zoom Video Webinars, supportsAudienceLocation, remote audiences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsAudienceLocation Context triple: [Zoom Video Webinars, supportsAudienceLocation, remote audiences]
-
A.
supportsLocation
chosen
Indicates that one entity provides the necessary structure, foundation, or capacity to hold, host, or accommodate another entity at a particular place or position.
-
B.
supportsRegionRestriction
Indicates that an entity enforces or accommodates limitations on availability or access based on geographic regions.
-
C.
supportsRegion
Indicates that one entity provides assistance, resources, or backing to a specific geographic or administrative region.
-
D.
teamLocationScope
Indicates the geographic or organizational area within which a team operates or is considered relevant.
-
E.
supportsCountry
Indicates that one entity provides assistance, endorsement, or backing to a specific country.
- 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_69a88a1554a48190a0180682bcf099be |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abca4d89248190be7d712d5fa8382b |
completed | March 7, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_69abc59d82f08190b7c36982d1ae783d |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:57 p.m.