Triple
T21224740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Megaco |
E523060
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | H.248 |
—
|
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: H.248 | Statement: [Megaco, alsoKnownAs, H.248]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: H.248 Context triple: [Megaco, alsoKnownAs, H.248]
-
A.
H.248
chosen
H.248 is an ITU-T protocol, also known as Megaco, used for controlling media gateways in next-generation and IP multimedia networks.
-
B.
H.323
H.323 is an ITU-T standard that defines protocols for voice, video, and data communication over packet-based networks such as IP.
-
C.
MGCP
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.
-
D.
H.245
H.245 is an ITU-T control protocol used in multimedia communication systems to negotiate channel usage and capabilities between endpoints.
-
E.
H.324
H.324 is an ITU-T multimedia communication protocol designed for real-time audio, video, and data transmission over circuit-switched telephone networks.
- 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.