Triple
T21224785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MGCP |
E523061
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | VoIP protocol |
C18457
|
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: VoIP protocol Context triple: [MGCP, instanceOf, VoIP protocol]
-
A.
VoIP client
A VoIP client is an application or device that enables users to make and receive voice (and often video) calls over IP networks instead of traditional telephone lines.
-
B.
media gateway control protocol
chosen
A media gateway control protocol is a signaling protocol that enables a media gateway controller to manage media gateways for the setup, modification, and teardown of multimedia sessions across packet and circuit-switched networks.
-
C.
audio-over-IP interoperability standard
An audio-over-IP interoperability standard defines common protocols, formats, and control mechanisms that enable different networked audio devices and systems to exchange high-quality audio streams seamlessly over IP-based networks.
-
D.
Audio Video Bridging protocol
Audio Video Bridging protocol is a set of IEEE Ethernet standards that provide time-synchronized, low-latency, and reliable transport of audio and video streams over local area networks.
-
E.
telecommunications software project
A telecommunications software project is an organized effort to design, develop, integrate, and deploy software systems that enable, manage, or optimize electronic communication over networks such as telephone, mobile, and internet infrastructures.
- 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_69e0b512ad94819087942b2ed925185f |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 3:44 p.m.