Triple

T7428185
Position Surface form Disambiguated ID Type / Status
Subject MCU (multipoint control unit) E171419 entity
Predicate supports P516 FINISHED
Object H.323 E171421 NE 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: H.323 | Statement: [MCU (multipoint control unit), supports, H.323]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: H.323
Context triple: [MCU (multipoint control unit), supports, H.323]
  • A. H.323 chosen
    H.323 is an ITU-T standard that defines protocols for voice, video, and data communication over packet-based networks such as IP.
  • B. 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.
  • C. SIP
    SIP is a Unicode supplementary plane that contains additional CJK ideographs beyond those in the Basic Multilingual Plane.
  • D. SIP
    SIP is the IATA airport code for Simferopol International Airport, the main air gateway to the Crimean Peninsula.
  • E. G.722
    G.722 is a wideband audio codec standard that provides higher-quality voice transmission than traditional narrowband codecs, commonly used in VoIP and teleconferencing applications.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69c68a63491881909281f73d4d5643bf completed March 27, 2026, 1:47 p.m.
NER Named-entity recognition batch_69c6f306bfe481909f99f6792de95ffc completed March 27, 2026, 9:13 p.m.
NED1 Entity disambiguation (via context triple) batch_69c81f0e28e88190805108dff740dda3 completed March 28, 2026, 6:33 p.m.
Created at: March 27, 2026, 3:12 p.m.