Triple
T21224825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MGCP |
E523061
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | RFC 2705 MGCP |
—
|
NE NERFINISHED |
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: RFC 2705 MGCP | Statement: [MGCP, alsoKnownAs, RFC 2705 MGCP]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2705 MGCP Context triple: [MGCP, alsoKnownAs, RFC 2705 MGCP]
-
A.
MGCP
chosen
MGCP (Media Gateway Control Protocol) is a signaling and call control protocol used in VoIP systems to manage media gateways under the control of call agents or media gateway controllers.
-
B.
RFC 2732
RFC 2732 is an Internet standards document that specified the use of bracketed IPv6 addresses in URLs before being superseded by RFC 3986.
-
C.
RFC 5766
RFC 5766 is an IETF specification that defines the Traversal Using Relays around NAT (TURN) protocol for relaying network traffic to help clients communicate across NATs and firewalls.
-
D.
H.248
H.248 is an ITU-T protocol, also known as Megaco, used for controlling media gateways in next-generation and IP multimedia networks.
-
E.
G.722.1 Annex C
G.722.1 Annex C is an extension of the ITU-T G.722.1 wideband audio codec that provides higher bit-rate modes for improved audio quality in applications like conferencing and VoIP.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b512ad94819087942b2ed925185f |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e734aa82c4819086cef6364619b4e9 |
completed | April 21, 2026, 8:26 a.m. |
Created at: April 16, 2026, 3:44 p.m.