Triple

T21225283
Position Surface form Disambiguated ID Type / Status
Subject Media Gateway E523070 entity
Predicate supportsCodec P203 FINISHED
Object G.723.1 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: G.723.1 | Statement: [Media Gateway, supportsCodec, G.723.1]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: G.723.1
Context triple: [Media Gateway, supportsCodec, G.723.1]
  • A. G.723.1 chosen
    G.723.1 is an ITU-T audio codec standard designed for low-bit-rate voice compression, commonly used in VoIP and multimedia communication systems.
  • B. G.723
    G.723 is an ITU-T speech coding standard designed for low-bit-rate voice compression, commonly used in early VoIP and multimedia communication systems.
  • C. G.721
    G.721 is an ITU-T (formerly CCITT) audio coding standard that defines 32 kbit/s ADPCM compression for digital telephony.
  • D. 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.
  • E. G.726
    G.726 is an ITU-T audio codec standard that specifies adaptive differential pulse-code modulation (ADPCM) for compressing voice signals at multiple bit rates, commonly used in telephony.
  • 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.