Triple

T4402442
Position Surface form Disambiguated ID Type / Status
Subject G.711 E93646 entity
Predicate comparedTo P278 FINISHED
Object G.729 E95665 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: G.729 | Statement: [G.711, comparedTo, G.729]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: G.729
Context triple: [G.711, comparedTo, G.729]
  • A. G.729 chosen
    G.729 is a widely used ITU-T audio codec standard that compresses voice for bandwidth-efficient transmission in VoIP and other telephony applications.
  • B. 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.
  • C. G.711
    G.711 is a widely used ITU-T audio codec standard for pulse code modulation (PCM) of voice in traditional telephony and VoIP systems.
  • D. Speex
    Speex is an open-source, patent-free audio compression codec designed primarily for efficient, high-quality speech encoding.
  • E. 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.
  • 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_69b345158c748190a2c040fce2da9980 completed March 12, 2026, 10:58 p.m.
NER Named-entity recognition batch_69b352d08a0c8190ac6c125df40eca75 completed March 12, 2026, 11:57 p.m.
NED1 Entity disambiguation (via context triple) batch_69b6135ecdc08190b2a7458614cf4c54 completed March 15, 2026, 2:03 a.m.
Created at: March 12, 2026, 11:28 p.m.